Legacy modernisation without a risky big-bang switch
The old system retired module by module, with the business running the whole time.
Use case · A logistics company on an old desktop system
Retiring the system only one person understood
A composite of the projects we take on: the problem, what we built, and what changed. Pick an act to jump the film to it.
Who it is for
Is this you?
- Companies running on a desktop system that is hard to change
- Teams where only one or two people understand the code
- Products stuck on an old PHP, .NET or Uniface version
What you get
- Audit of the old system, its screens and business rules
- Migration plan, module by module
- New web app and API
- Data migration with reconciliation reports
- Old and new running side by side
- Documentation and handover
Built with
- Uniface
- .NET
- React
- Node.js
- PHP
- Laravel
- SQL Server
- PostgreSQL
What we cover
Legacy modernisation, in detail
Pick one part or the whole set. We scope only what your problem needs.
Migrations
- Uniface to .NET and React
- PHP to Node.js
- Desktop apps to the web
- Monolith to services, where it helps
Data
- Schema redesign
- Migration scripts with checks
- Reconciliation reports
- Archiving old records
Cloud moves
- On-premise servers to AWS, Azure or Google Cloud
- Containers for old workloads
- Backups and recovery plans
- Cost review after the move
Keep it running
- Support for the old system during the move
- Framework and dependency upgrades
- Security patches
- Knowledge capture from your experts
How it runs
From first call to legacy modernisation in production
You see working software early and can change direction while it is still cheap.
- 01
Map the old system
We sit with the people who use and maintain it, and write down every screen, rule and report. - 02
Plan the order
We pick the module order that removes the most risk first and agree how each switch is checked. - 03
Rebuild side by side
Each module is rebuilt and run beside the old one on real data until the results match. - 04
Switch off
Users move over, the last data is migrated and checked, and the old system is retired.
Questions
Legacy modernisation: what people ask
Do we have to stop using the old system?
No. The old system keeps running until each new module has proved itself on real data. Users move over module by module.
What if there is no documentation?
That is common. We learn the rules from the code, the database and the people who use the system, and write them down as we go.
Can you upgrade instead of rewriting?
Sometimes that is the better choice. We look at both in the audit and recommend the cheaper, safer route for your case.
Planning legacy modernisation work?
Tell us where things get stuck today. We will reply with a plan, not a pitch.