Replatforming
A new platform, the same proven process
We move running systems to a modern architecture. In stages, with data and permissions migrated, so the company is never left without its tool, not even for a day.
What replatforming is
Changing the foundation without tearing the house down
Replatforming means moving a system to a different technology platform while keeping its business logic. The company does not give up a process it has refined for years. It changes the technology that process runs on.
The reason is rarely purely technical. The old system usually still does what it was built for. The problem appears around it: it cannot be connected to the new ERP, it does not work on a phone, people who can develop it are hard to find, and every change takes longer and costs more.
Signs that it is time to decide
- Knowledge of the system is in the hands of one or two people.
- Integration with new systems needs workarounds instead of standard interfaces.
- A security audit flags the platform as a risk.
- Users keep their own spreadsheets because the system cannot keep up with change.
- Licence and maintenance costs rise while the number of users falls.
An old system is rarely bad. What is bad is the moment when nobody can change it safely any more.
Where we begin every conversation about modernisationFive routes
Replatforming is not always the right answer
For each application we consider five options. An honest assessment often concludes that some systems only need maintaining and some can be switched off.
| Route | What it involves | When it makes sense | What to watch |
|---|---|---|---|
| Maintain | The system stays on its current platform; errors and threats are removed. | The application is stable, rarely changes and does not block other projects. | Technical debt grows and specialists become scarcer. |
| Modernise in place | A new interface, integrations and a version upgrade without changing platform. | The platform is still supported and the problem is usability or missing connections to other systems. | The platform’s limitations remain. |
| Replatform | Business logic and data move to a new platform, usually with a new interface. | The platform holds back development, integration or security, and the process is worth keeping. | Requires a sound inventory and careful data migration. |
| Replace with a product | The process moves to a ready system, such as an ERP or a specialised platform. | The application does what standard software does today. | The process has to be fitted to the tool. |
| Retire | The system is switched off and data archived in read-only mode. | Nobody works in the application any more, but the data must be kept. | Access to the archive must be ensured for the required period. |
How we work
Five stages of moving a system
The key rule: for a time the old and new systems run side by side. Functions move to the new platform one after another.
- 01 Inventory Applications, users, data, integrations
- 02 Decision per application Keep, modernise, move, replace or retire
- 03 Target architecture Data model, permissions, integrations
- 04 Migration in stages New modules beside the old system
- 05 Switch-off and archive Trial migrations, parallel run
A practitioner’s view
Where migrations most often go wrong
Code can be rewritten. What is harder is what the code does not show: unwritten rules, data of varying quality and connections everybody forgot.
Logic nobody wrote down
In long-lived systems business rules live in the code, in views and in users’ habits. We reconstruct them from the running application and from conversations with people, not from documentation that usually describes the state of years ago.
Data quality
Old systems contain incomplete records, differing identifier formats and historical data stored in ways that are hard to read automatically. So we repeat trial migrations several times and compare the result with the source each time.
Permissions
Who sees which document is often buried deep in the old platform. We move not only the data but also the rules of access to it, and test them on examples chosen by the process owners.
Integrations everyone forgot
A nightly export to another system, a report sent by e-mail, a file dropped on a disk. Such connections come to light only after switch-off unless they are inventoried earlier.
Where we migrate from
Environments we know from modernisation work
Each of these platforms served companies well for years. Trouble starts when it has to be connected to other systems or opened to more people.
HCL Notes / Domino
Analysis of databases, documents and attachments, export to XML or JSON, and moving data and business logic to a web application.
More on Notes / DominoMS Access
Forms and logic from a file on one computer move to a web application with a central database, roles and change history. Old reports are replaced by interactive tables with filters and export.
FoxPro
We analyse the running system, reconstruct rules nobody wrote down and move functions gradually, verifying that historical data is complete.
The scope and method of migration are agreed after analysing the specific system. We do not promise an automatic, push-button migration.
Questions
What clients ask most often
How does replatforming differ from writing a system from scratch?
In replatforming the starting point is a running system: its data, rules and the way users work. We keep what works and move it to a new platform. Writing from scratch starts with a blank page and usually means redesigning the process too. In practice projects combine both: some functions are moved unchanged and some are simplified along the way.
Does everything have to be moved at once?
No, and it is usually not worth it. We start with the application that blocks the company most or carries the greatest risk. The others can keep running, and some turn out after the inventory to be candidates for retirement.
What about historical data?
We agree that with the process owner. Data needed for current work goes to the new system. Older data can be moved in full or left in a read-only archive if regulations or company policy require it.
How long does such a project take?
It depends on the number of applications, data quality and integrations. That is why the first stage is an inventory with an assessment of each application. Only then do we give a scope and schedule instead of estimating blind.
Do you handle maintenance after migration?
Yes. After rollout we can move on to maintaining and developing the system under an agreed SLA. We also take over applications built by other vendors.
Do you have a system nobody wants to touch?
Let’s start with an inventory. After it you will know what to keep, what to move and in what order.