Articles
Field notes, not marketing. Everything here comes from systems we have actually migrated or still operate — anonymized, but real.
-
Rewrite vs convert vs wrap: choosing a legacy migration strategy honestly
The real strategies for a legacy application — parity-tested rewrite, automated conversion, wrapping — compared by cost, risk and what you own afterwards.
-
Lotus Notes/Domino to .NET: what actually breaks
Field notes from migrating a ~9,000-document Notes application to .NET: rich text, reader fields, role mapping — the six places every NSF migration bleeds.
-
SAP Advantage Database Server after EOL: your realistic options in 2026
Advantage Database Server is discontinued. The four realistic paths — freeze, replace the server, migrate the data, retire the app — with benchmark notes.
-
Migrating a Clipper/xBase app without losing 30 years of business rules
Parity testing for xBase migrations: freeze current behavior as executable tests — bugs included — and let the diff decide when the new system is ready.