Assessment and proof
We inventory source availability, OCX/COM and native dependencies, databases, serial or hardware interfaces, printing and installer constraints. A proof of concept targets the highest-risk boundary and produces evidence for preservation, staged modernization or replacement.
- Recover critical workflows and acceptance cases.
- Separate urgent compatibility work from architectural change.
- Plan phased delivery with production rollback.
- Compare migrated outputs against representative data and devices.
Useful starting material
Provide source and project files, deployed binaries, installers, database samples, error evidence, device documentation, a working-machine inventory and the workflows that cannot be interrupted. Exact outcomes depend on what survives; assessment precedes commitment to a rewrite.
Compare application modernization, .NET migration, Windows migration and the VB6 pillar.