Custom software · web and desktop systems, databases, integrations
Legacy software modernization. Keep, wrap, rewrite
or retire
Legacy software modernization means choosing a route for each old system: keep it, wrap it with an interface so new tools can use it, rewrite it in parts, or retire it. Amazing Soft, based in Bucharest since 2016, handles wrapping and rewriting in parts. The first step is always a data export. One example from our portfolio: “Retail store software for an international retailer, moved to Linux”. If a system works and nobody needs to change it, keep it.
The problem. Nobody dares change the working system
The old system still runs the company: orders, inventory, invoices and the price list. Someone who has since left wrote it years ago, in a language nobody on the team writes anymore. There is no documentation or test suite. The server cannot be updated because an update would break the application. Every new requirement hits the same barrier, whether it is an online store, a warehouse mobile app or an accountant’s report. The data is there, but the only way to get it out is by hand. The company has stopped asking for changes because each one means a week of worrying about what might break.
Software modernization services. Four routes for your existing system
Modernization is often sold as a single service. In practice, there are four routes, and most companies need two at once. You might keep one part, wrap another and rewrite a third.
| Route | What it means | This fits | It does not fit |
|---|---|---|---|
| Keep | Leave the system as it is, document it, back it up and isolate the server. | When it works, its data is exportable, nobody needs new features and the people who run it are staying. | When you depend on it daily but the server or language is out of support. |
| Wrap | Put an interface, or API, in front of the old system or database so new tools can read and write through it. | When the core logic is right, you need a web or mobile interface or an integration, and a rewrite would take too long. | When the data model is wrong, or the system is so slow or fragile that calls through the API fail. |
| Rewrite in parts | Rebuild one module at a time using the same data, with old and new parts running side by side. | When the system changes often, the team needs to maintain it and you can allow months for the transition. | When everything must be replaced in one day, or the budget covers only the first part and nobody has planned the rest. |
| Retire | Move the function into a product you buy and export the history. | Standard functions such as accounting, email or HR when a product handles them better than software you would build. | When the function sets your company apart, or the product cannot import your history. |
Four questions determine the route for each part: Does it still need to change? Can you export the data? Who will maintain it next year? What would a day of downtime cost?
Say you run old PHP software. How gradual replacement would work
Say you run your company on an old PHP and MySQL application for customers, products, orders and invoices, with no export beyond printing. An API around its database would let a new online store read products and inventory and send orders back. Your team would keep using the old screens while replacement screens were built one at a time around the same data. If the online store and warehouse app met your needs, the rebuild would stop there.
Why not rewrite everything at once. Four reasons
The old system is the only specification
Nobody remembers every rule it enforces. A full rewrite rediscovers those rules one bug at a time, in production.
Nothing is delivered until everything is
A year of work can pass without a new screen in anyone’s hands or a way to stop halfway.
The team has to keep working
A side-by-side transition lets people use new screens as they arrive and keep using the old ones until then.
The data determines the pace
A legacy system migration is mostly a data migration. Once the data is exported and understood, the rewrite order becomes clear. The rewrite can sometimes be shorter than planned.
What happens to the data. The first step, always
Before we choose a route, we make a complete data export in a format you own. We verify it against the screens your team uses. We then clean it where needed, addressing duplicates, unused records and fields nobody fills in. We document it table by table.
During wrapping, the old database remains the source of truth, and the API reads and writes to it. During a rewrite in parts, new modules use the same data until the last old screen is retired. We then move the data once, after a trial migration and with a rollback plan in place. Nothing is deleted until the new system has completed a full month-end using it.
Before a rewrite, a written technical review: Technical due diligence →
Who this suits. Teams relying on older business software
Companies in the UK and the US that rely on software written five to twenty years ago in PHP, classic ASP, .NET Framework, Java, Delphi, Access or FoxPro. The server is one nobody wants to touch, and the data needed for the next step is locked inside. The service covers systems used by a dozen people through to several hundred.
If your old system is a mobile app in the stores, see app maintenance and upgrades. The approach is similar, but the tools differ.
Proof. Store software moved to Linux
Retail store software for an international retailer, moved to Linux
We moved the software the stores run on onto new equipment and onto Linux, in phases, and added self-scan for shoppers. See this work →
The assessment comes before the proposal, and the export comes before any change. We build in versions you can see and test. We write code in languages your team can maintain, and document what we find and build.
Our custom software development services cover web applications, customer portals, system integrations and desktop apps, with details of what we deliver and how.
When not to modernize. Four cases
It works and needs no changes
If the data is exportable and the server is supported, keep it, document it and back it up.
A product does the job better
If the system handles standard accounting, email or HR, move that work into a product and export the history.
Nobody on your side owns it
Modernization needs one person who knows the business rules and makes decisions. Without that person, start with the assessment and stop there.
You want a complete switch on a fixed day
We do not do that. Your business would bear the risk, while the old system remains the only specification.
Questions. Short answers
What is legacy software modernization?
It means updating or replacing old software so your company can keep using its data and make changes to the system again. Each part follows one of four routes: keep it, wrap it with an API, rewrite it in parts or retire it into a product. The right answer is usually a mix, chosen after an assessment and a data export.
Is application modernization the same as legacy software modernization?
Yes. Application modernization is another name for the same work: updating or replacing old software so your company can keep using its data and make changes to the system again. On this page, it covers web and desktop systems and the databases behind them.
How much do legacy software modernization services cost?
We do not publish prices because two systems of the same size can differ several times over in cost. The price depends on the condition of the code and data, how many parts need wrapping or rewriting, and connections to other systems. The assessment comes first. You then receive the written proposal with a fixed price for each stage.
How long does a legacy system migration take?
Months rather than weeks, in stages, with the old and new systems running side by side. The assessment and data export come first and are short. The remaining work depends on how many parts need rewriting. The proposal sets out the stages and their order. We do not promise a date before the assessment.
Can we keep working in the old system during the modernization?
Yes. That is the purpose of wrapping and rewriting in parts. Your team keeps using the old screens while new ones replace them one at a time. The data stays in one place until the last old screen is switched off.
What if nobody has the source code?
It happens. With access to the database and running application, we can still export the data, document what the system does from its screens, and wrap it. A rewrite then starts from the data and how your team uses the system, rather than from the code.
Do you also modernize mobile apps?
Yes. Our maintenance and app rescue service covers apps in the App Store and Google Play that nobody maintains anymore. This page covers web and desktop systems and the databases behind them.
Who we are. Your development team in Bucharest
Amazing Soft SRL is a software company in Bucharest, Romania, founded in 2016. We work remotely with companies in the UK, the US and Canada, in English. Our data processing agreement is published on our legal page. Our time zone is EET, which overlaps most of the UK working day and the morning on the North American East Coast. The price is set after the free 30-minute consultation, in the written proposal with a fixed price.
Describe what your old system does. You receive an assessment plan
We reply on the channel you wrote on to arrange the free 30-minute consultation. The assessment comes before the written proposal with a fixed price for each stage. If the proposal suits you, we sign the contract and start work.
- Home
- Legacy software modernization