Our ERP implementation approach: five phases, five decisions.
Whether it is an ERP implementation or an SAP S/4HANA migration, each phase of our methodology ends with a documented result. Then you decide whether and how to proceed.
- Certified SAFe® 6.0 Practice Consultant (SPC)
- PRINCE2® Practitioner
- Overall project leadership reporting to the executive board
From legacy system to stable operations
Assessment and readiness
System landscape, custom code, data, processes, and interfaces.
Result: readiness report and recommendation for the transition path. Decision: path, budget range, and timeline.
Target processes and data strategy
Together with the business: target processes, migration objects, cleansing rules, and owners for each data area.
Result: agreed designs and object list. Decision: approval of the designs for implementation.
Test migrations
Full test migrations (mock migrations) with reconciliation of quantities and values, until the migration is reproducible.
Result: reconciliation reports and measured run times. Decision: dates for the dress rehearsal and cutover.
Cutover and go-live
Switchover according to the runbook: owners, time windows, checkpoints, abort criteria, and fallback plan.
Result: production system with reconciled data. Decision: go or no-go at the end of the weekend.
Hypercare and handover
The stabilization phase after go-live: support through the first weeks of operations, quick fixes, and an orderly handover to your team.
Result: stable operations and handover documentation. Decision: project closure.
What your executive team gets from us
The decisions are yours. We make sure each one is on the table in time, with options and consequences.
- One-page status reportStatus, risks, and open decisions, short enough for any steering committee.
- Decision papersOptions with their consequences for schedule, budget, and risk, plus a clear recommendation.
- Agreed leewayWe agree in advance how much schedule and budget variance the project absorbs on its own. Anything beyond that is your decision.
- Go/no-go criteriaThey are fixed before the cutover weekend begins. On Sunday, they are checked, not negotiated.
Agile where it helps. Plan-driven where it has to be.
An ERP project has parts that need to be managed differently. That is why we use hybrid project management.
| Project part | Approach | Why |
|---|---|---|
| Process design and concept | Iterative, in workshops with demos in the system | Business teams spot gaps faster in the system than in a document. |
| Extensions and custom software | Agile, with backlog, sprints, and prioritization by economic value | Requirements change, and the value should become visible early. |
| Data migration | Cyclical, with scheduled test migrations and reconciliation after each run | Quality comes from repetition. |
| Cutover | Plan-driven, following the runbook, with a go/no-go decision | On the cutover weekend, every hour counts. |
| Project governance | Management stages, tolerances, and a project board (steering committee), following PRINCE2® | The executive team decides at clear points. |
| Multiple teams | Joint planning at a fixed cadence, based on SAFe® | Dependencies between teams become visible before they become a problem. |
Phase 4: cutover and go-live
The cutover weekend is organized around the cutover runbook.
- T–6 wks Dress rehearsal The full runbook is run once, with real data volumes and measured run times.
- T–2 wks Master data freeze Material, supplier, and customer master records change only with approval.
- Friday Close legacy system Complete open transactions, post stock, lock the legacy system for postings.
- Saturday Migration Objects are migrated in a fixed sequence, from business partners to fixed assets.
- Sunday Reconciliation Check quantities and values against the legacy system; reconcile asset values with accounting.
- Sunday evening Go/no-go Decision based on criteria agreed in advance. The fallback plan is ready.
- Monday Go-live First working day in the new system, with hypercare and daily reconciliation.
We plan the dress rehearsal six to eight weeks before go-live; the other intervals follow from its measured run times.
- Every task with owner, start, duration, and dependencies
- Master data freeze and closing in the legacy system
- Sequence of migration objects with measured run times
- Checkpoints with reconciliation of quantities and values
- Go/no-go criteria fixed in advance
- Fallback plan if the criteria are not met
- Communication plan for business teams, customers, and suppliers
- Hypercare organization for the first weeks
Initial call: 30 minutes, free of charge.
Tell us about your system landscape and timeline. We will tell you where we see risks and whether we are the right fit.