System Selection gets the attention. Migration and go-live decide success.
Seven lessons from ERP and CRM transformations at PE-backed companies in the DACH region, for management and investors who need the new system to work in day-to-day business.
Free download
A 7-page read on sequencing, migration, fallbacks, stabilisation and ownership.
Done!
The whitepaper is on its way to your inbox. If it doesn’t arrive within a few minutes, please check your spam folder.
By submitting, you agree that we may send you the whitepaper by email. Unsubscribe anytime.
82%
customers migrated in a staged rollout
~50%
added value assumed in year one
~€3m
vs €1.6m estimate without hypercare
What you'll learn
What decides success after the contract is signed
-
A switchover order that protects operations
Why ERP, billing and operations rarely belong on one date, and how staged migration with checks between groups keeps orders and invoices flowing.
-
Fallbacks and data the business signs off
How tested fallbacks for critical interfaces and data checked by the business prevent problems that only surface in live operation.
-
Budget and ownership beyond go-live
Why stabilisation needs its own budget and exit criteria, how to plan parallel costs, and who must own the system afterwards.
The Problem
During selection, management and investors discuss ERP, CRM and implementation partners at length. Once the contract is signed, implementation is often left largely to the partner, while decisions on processes, data and responsibilities stay with the company.
Business teams take on project work on top of day-to-day business. If invoices cannot be issued or orders cannot ship, revenue and liquidity take the hit directly.
“Switching ERP, billing and operations on one date puts all the risk on a single day.”
The answer is to plan migration, go-live and stabilisation as thoroughly as the selection.
FAQs
Why do business software projects so often fail after the software has already been chosen?
Selection gets most of the attention, but migration, go-live and stabilisation decide whether the project works. Once the contract is signed, implementation is often left largely to the partner, while decisions on processes, data and responsibilities stay with the company. Business teams usually do project work on top of their day jobs, often without dedicated project management.
Should we switch to new business software all at once or in phases?
It depends on how your systems and processes depend on each other. A single cutover date puts all the risk on one day and needs very thorough testing and a robust cutover plan. Where dependencies allow, a step-by-step switchover is safer: start with less critical components, and migrate customers or entities in groups, checking each group before the next. A blanket rule such as "always migrate finance last" is too simplistic.
How do we make sure our data is ready before migrating to new business software?
Being told the data has been cleaned is not enough, because even formally valid records can be wrong in business terms. The business and technical teams should agree on validation criteria together. The technical team checks formats, completeness and duplicates, and the business confirms that the data reflects real customers, contracts and processes. This sign-off cannot be handed entirely to the implementation partner.
What happens if an interface fails after go-live?
If nobody knows how the affected process should continue, orders or invoices can stall. For every critical interface, check in advance whether a manual or technical fallback exists, such as an export and import tested with realistic volumes. Where there is no viable substitute, a working interface has to be a condition for go-live, and delivery dates and response times should be agreed with vendors early.
How much budget should we plan for support after a business software go-live?
There is no fixed mark-up, but intensive post-go-live support (hypercare) needs its own budget, an available team and clear exit criteria. It should end only once key processes run stably and operations can take over open issues, not just when a planned date arrives. In one project, the estimate was €1.6m without hypercare and closer to €3m including stabilisation, which shows why this budget should be ring-fenced.
When does new business software actually start paying off?
Rarely from day one. New licences and project costs usually arrive before legacy systems are switched off and improvements take full effect. The business case should show total costs over three to five years, including parallel operation, licences, stabilisation and internal effort, and schedule savings realistically. In one project, only about half of the expected added value was assumed for the first twelve months.
Who should own business software internally once the implementation partner is gone?
Even with an external support partner, the company needs someone who sets priorities, reviews performance and makes decisions, because a support contract does not replace that role. The owner should be named during implementation, for example a system owner or integration engineer depending on size and complexity. Knowledge has to be handed over while the project team is still available.
Get the whitepaper.
Free of charge.
Get the whitepaper now
A 7-page read on sequencing, migration, fallbacks, stabilisation and ownership.
Done!
The whitepaper is on its way to your inbox. If it doesn’t arrive within a few minutes, please check your spam folder.
By submitting, you agree that we may send you the whitepaper by email. Unsubscribe anytime.