Services
One niche, done properly: getting business-critical applications off dead or dying platforms without losing the rules encoded in them. Every engagement starts with a fixed-price assessment — never with a blank-check rewrite.
Visual FoxPro to .NET
FoxPro 2.x and Visual FoxPro applications rebuilt on .NET + SQL, with the business rules intact.
Clipper / xBase
DOS-era Clipper and xBase systems — contained with Harbour first, then migrated calmly.
dBase / DBF data
DBF tables moved to SQL with codepages, memo files and deleted rows handled correctly.
Microsoft Access
Access front-ends and Jet/ACE databases upsized to SQL Server and rebuilt for the web.
Lotus Notes / Domino
NSF documents, forms and reader-field security reproduced faithfully outside Domino.
Advantage Database (ADS)
Post-EOL strategy for SAP Advantage: freeze, replace the server, or migrate off DBF.
How every engagement is structured
-
Legacy Assessment (fixed price, 1–2 weeks)
Inventory of code, data, indexes, reports, integrations and users. Risk map and a written migration roadmap with effort estimates. Yours to keep, whoever executes it.
-
Parity harness before new code
We capture the current system's real behavior — reports, totals, edge cases — as an automated test suite. That suite, not opinions, later decides when the migration is done.
-
Incremental migration
Data first, read-only mirrors early, modules moved in slices. The legacy system stays in charge until each slice passes parity.
-
Cutover with a way back
Go-live with a rollback plan and a frozen, archived copy of the old world — so the decision is reversible until it no longer needs to be.
Start with a fixed-price Legacy Assessment
One to two weeks. You get a full inventory of the application and its data, a risk map (what breaks first, what is undocumented, what nobody can rebuild), a data-quality report and a migration roadmap with honest effort estimates — a document you can execute with us or with any other team. Fixed price, agreed before we start.