A friend owns a legacy application written in AlphaBASIC that runs on an Alpha Micro system. Although it is old, the software is still used commercially and generates revenue. It mainly handles data entry, validation, and submitting tax-related records to a government agency.
He would like to move it to a web-based application. The system does not seem unusually complex, but accuracy is critical because even a small validation or calculation error could cause real-world tax problems. The original developer is retired but still available as a contractor, and there is a detailed manual describing the workflows, fields, business rules, validation, reports, and migration process, along with the source code and screenshots.
What would be the best migration strategy? Should the existing application be integrated with a new web front end first, or should the business logic and database be rebuilt from scratch? Has anyone handled a similar AlphaBASIC modernization?
2 Answers
Because this handles tax submissions, I would avoid replacing the calculation and validation engine all at once. If possible, build a web interface that sends data to the existing program and receives its results. That lets you modernize the user experience while keeping the proven business logic in place during the first phase.
If the old system cannot be integrated, then recreate the rules carefully and compare the new and old systems with large sets of real or anonymized cases. Regression testing, edge cases, audit trails, and a period of running both systems in parallel are more important than the choice of framework.
I would treat this as a new web application rather than trying to translate the old screens line by line. Use the existing source, manual, screenshots, and interviews with users to document the workflows, entities, validations, calculations, reports, and government submission process. The manual sounds especially valuable because it explains why each step exists, not just what each screen looks like.
A sensible target could be a REST API with a modern front end, such as React, Angular, or Blazor, with the domain model and database designed around the actual business processes. Generate documentation and automated tests as you go so future developers know what the system is supposed to do.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically