About
MigrationParity is a deliberately narrow practice: legacy migration for the long-tail stacks, run by someone who still operates these systems in production — not someone who read about them.
My name is Vito Romanovsky (Vitaly Romanovsky). I have spent my career as a software engineer and database administrator inside manufacturing companies — the environment where "legacy" is not an abstraction but the thing that prints today's traveler cards and closes this month's books.
That career happens to be a tour of exactly the systems this practice migrates. I maintain and extend DBF-based production software daily: FoxPro-era data with DOS codepages (including the Hebrew cp862 flavor that breaks every generic tool), CDX indexes with business rules inside them, client/server xBase over Advantage Database Server. Recent projects, anonymized:
- Ported a production Clipper-family utility to Harbour — 32- and 64-bit native builds of a decades-old codebase, verified live against the original server-based DBF data. The "contain first, migrate calmly" pattern this site recommends is one I have executed, not just diagrammed.
- Migrated a ~9,000-document Lotus Notes workflow application to .NET 8 with a SQL backend — schema archaeology, rich-text conversion, reader-field security reproduced as row-level authorization, and a COM coexistence bridge for the transition. The scars became this article.
- Benchmarked post-EOL options for SAP Advantage Database Server on production-shaped workloads — including open-source server replacement and 32→64-bit client stacks — before recommending a path. Findings published here.
- Built verified DBF-to-SQL pipelines feeding modern reporting from live xBase systems — nightly, checksummed, with the legacy application undisturbed.
I work in English, Hebrew and Russian; I am based in Israel and work remotely with clients worldwide. The free DBF Analyzer on this site is the kind of tool I build for my own migrations, shared because watching it flag your files explains my work faster than any brochure.
How I engage
Every engagement starts with a fixed-price Legacy Assessment — one to two weeks, ending in a written roadmap you own outright. No open-ended discovery billing, no pressure toward the biggest project: if containment or even retirement is the right answer for your system, that is what the roadmap will say.
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.