Problems this service addresses
- You want to replace an old VB6, MFC, or WinForms app
- There is no specification document; the current app’s behavior is the spec
- The person in charge has left, and every change risks breaking something
- You want a full rewrite, but the risk of business downtime or rollback is too high
- You need to decide what to do with existing reports, data, device integrations, and COM assets
In a Windows app replacement, rather than rebuilding from scratch right away, it matters most to pick up the specifications embedded in current operations and decide the order of replacement.
Themes we handle well
- Migrating business apps built on VB6 / MFC / WinForms
- Taking inventory of screens, reports, data, settings, and external integrations
- Continuing to use existing COM / ActiveX / OCX, or separating them out in stages
- Plans that include parallel operation, rollback, and migration rehearsals
- Design, implementation, and migration support for the new Windows app
Typical way of working
- First, we review the current app’s screens, data, reports, external integrations, and operating procedures.
- Next, we split the app into what to keep, what to replace first, and what to defer, and build a migration plan ordered by risk.
- Implementation then proceeds on the new app’s design, development, and migration, with parallel operation and rollback in mind.
When this is a good fit
- Your old Windows app is reaching the limit of continued use
- You want to escape dependence on a vendor or a former employee
- You want to move to a new architecture in stages without breaking the existing specifications
- You want to start with just the investigation and the plan before committing to a replacement