Specialist · Pick / MultiValue migration
If your business runs on a Pick / MultiValue system — Rocket UniData, UniVerse, PickBasic, D3 or jBASE — you already know the problem: almost no one left can work on it. I can. I migrate the data and the business logic into a modern .NET, Angular and SQL platform — without losing what the old system knows.
Why it's urgent
MultiValue and PickBasic developers are retiring and aren't being replaced — the talent pool shrinks every year.
The whole system often rests on a single person who understands it. When they leave or retire, the business is exposed.
Connecting a MultiValue database to modern web, mobile, payments or reporting tools is painful and brittle.
Proprietary licensing and specialist support keep costing you, for a platform you're trying to move beyond.
Decades of business rules are buried in PickBasic, largely undocumented — the riskiest part of any migration.
Terminal / green-screen interfaces slow new staff down and hold the business back from where it wants to go.
Why me, specifically
Most migrations fail in the gap between two groups: the modern developers who've never seen a MultiValue database, and the few remaining Pick developers who don't build modern web platforms. I sit in both camps — years of hands-on PickBasic, UniData and UniVerse, plus current .NET, Angular and SQL.
That's why the business logic survives the move. I can read what the old system actually does — including the edge cases no one wrote down — and rebuild it correctly, rather than guessing and shipping something that quietly does the wrong thing.
From
To
Two ways in
Get your data out of the Pick / MultiValue system and into a modern SQL database — Microsoft SQL Server for enterprise needs, or PostgreSQL for lower cost — cleanly mapped from the multi-valued model, ready for reporting, integration, or as the first step toward a rebuild.
Rebuild the whole system as a modern, cloud-native web platform — the PickBasic business logic recovered and re-implemented, a proper web UI replacing the green screen, and everything you own and can hire for.
How a migration runs
Review the UniData/UniVerse schema and PickBasic logic; document the rules that matter.
Design the relational model and target architecture; plan the migration and cutover.
Move data and rebuild in safe stages, reconciled against the old system, running in parallel.
Switch off the legacy platform — and I stay on to support and enhance what replaced it.
Common questions
A free intro call to talk through your UniData / UniVerse / Pick system, or a paid Software Opportunity Review for a full migration plan with budgets and timelines.