From a legacy system to a current platform — with no standstill in the core business.
An established B2B wholesaler for diesel and gas engine parts and remanufacturing logistics. Grown over decades, with a specialised legacy system whose logic was unique — and no longer fit for the future.
A specialised legacy system, specialised subjects.
An ALPHAPLAN-based ERP, extended over decades with adaptations for the specifics of the trade — core charges, remanufacturing deposit logic, technical classification by engine type, a compatibility database. Functionally mature, but embedded in a technical environment that was no longer current.
Management faced the question: migrate, or stay put? Moving to a current platform would put the core business at risk — the special functions were not easy to represent in any standard ERP.
- ALPHAPLAN as a decades-old specialised ERP
- Core charges and remanufacturing logic not representable in any standard system
- The e-invoicing obligation and new digital requirements looming
Evaluation, design, implementation.
A vendor-neutral analysis: which standard ERP can represent the specialised subjects? Which have to be added as custom modules? A make-or-buy decision together with management and the tax advisers.
Detailed architecture for core charges as a custom module, remanufacturing deposit workflows, migration of the compatibility database, DATEV integration with all its special cases. An e-invoicing roadmap in parallel.
Migration in planned phases, with no standstill. The uncritical areas first, then the specialised subjects. We accompany the implementation actively and act as sparring partner on the detailed decisions.
What we actually used.
Migration on plan, with no operational outages.
The project is running. The first migration phases have been completed successfully — master data and standard processes work on the new platform. The specialised subjects are defined as custom modules and are in the implementation phase.
What management feared most beforehand — a standstill in day-to-day business — did not happen. Migrating in phases, with close support, kept the platform change from becoming a bottleneck.
- Phased migration on schedule
- No operational outages during the changeover
- Specialised subjects cleanly represented in custom modules
(Client quote to follow — we are waiting for the migration to complete.)
Other clients, other sectors, other stories.
See all cases →Does this sound like your platform?
If you recognise a situation like this — a platform that grew as it went, data kept in step by hand, the pains of growth — we are glad to talk with you about whether a similar route would suit you.