A core system from 2012, opened up again
Manufacturer in the Brainport region, 320 employees — an API layer next to the existing system, without production downtime.
- 6
- weeks until the first integration went live
Where it began
The planning system had been running since 2012 and did its job, but had no integration at all. Every new web shop or customer portal meant Excel exports and putting data back by hand.
Replacing it was too risky: all of production depended on it.
How we approached it
-
01
Read first, then write
We built an API layer that only read from the existing database, so nobody had to worry about production.
-
02
Writing through the same rules
Changes go through the business rules of the old system, not around them. That way there is one version of the truth.
-
03
Recording the migration path
Every part that now runs through the API can later be replaced on its own without touching the rest.
What it delivered
Six weeks after the start the first integration went live, without a minute of production downtime. The customer portal now takes delivery times straight from the planning.
Is this familiar?
Tell us which process takes the most manual work. Within half an hour you'll know whether it can be solved this way.