Most legacy systems have been running for many years. They have grown with the business, and there is more in them than a feature list shows: pricing rules, approvals, exceptions that someone added at some point. Accordingly, people have a lot of respect for the switch.
We replace legacy systems with ElbDesk, our custom ERP, area by area rather than on a single cut-over date. The following sections answer the questions we are asked most often along the way.
How is the switch planned while the business keeps running?
First we look at what depends on the old system: which areas use which data? Which programs are connected? Where are there dependencies you only notice at second glance?
That gives us an order. A first area switches while the rest stays in the old system for now. The data needed flows back and forth through tested interfaces. For each stage we define tests, data migration, sign-off and, where needed, a period of parallel operation. Why this route is usually safer than a hard switch is described in Cut-over date or step by step.
What if the knowledge sits with a few people?
That is the rule rather than the exception. Often only two or three people know the rules the system really follows, and some of it is written down nowhere.
So we record these rules together with exactly those people, using real cases rather than abstract workshops. What comes out of it is documented. In the end the knowledge no longer depends on individuals, but lives in the new system and its documentation.
What happens to our legacy data?
Before implementation we clarify which data is migrated, in what form and how thoroughly it is cleaned up first. Not everything has to go into the new system: some records are only needed for looking things up.
For older data we define how it stays readable and easy to find. Where retention requirements matter, we involve your tax adviser. More on this in Moving old data to a new system.
What stays from the old system and what is new?
We decide that together. Systems that work well and that you want to keep are included in the transition plan and connected where possible. What gets replaced is what slows the business down.
With ElbDesk we do not start from scratch. The Core brings sign-in, permissions, collaboration and documents, and ERP modules such as purchasing, stock or accounting are added as needed. What gets developed is mainly what makes your business different.
Do you also support the introduction of other ERP systems?
Our replacement projects are built on ElbDesk. If you have decided on another ERP, that is also a route we support - just differently.
In that case you introduce the new ERP with its vendor, and we take care of what is needed around it: interfaces to your other programs and custom applications for workflows the standard does not cover. What that can look like is shown on our page on ERP integration and interfaces.
What happens after the rollout?
The project does not end with the switch. We agree who your contact is in daily operation and how disruptions are handled. New requirements and further areas are planned as separate stages.
Keeping knowledge in the team is part of it too: documentation and training are meant for your staff and for those who join later.
