Cutover, fallback plan and go-live

On cutover weekend, preparation becomes reality. Calm does not come from optimism, but from a process that everyone involved knows and whose branches are decided in advance.

The truth is in the mapping

The cutover combines data freeze, final export, import, technical inspection, technical acceptance and release. A fallback plan not only describes “installing a backup”, but also the timing, decision and handling of changes that have occurred in the meantime.

From raw stock to controlled import

1. Freeze scope, source version, expiration, contacts and go/no-go criteria.
2. Stop write access in the legacy system or capture a clearly defined delta.
3. Create final backups and verify their readability.
4. Run import and automated controls by runbook.
5. Have designated specialists check core processes.
6. Decide go/no-go before the relapse threshold and communicate clearly.
7. Once launched, closely monitor bugs, performance and support patterns.

Evidence instead of gut feeling

• Each step has a time, person responsible and expected result.
• Delta between test and production is complete.
• Relapse has been rehearsed and is achievable in a timely manner.
• Post-launch support and escalation are staffed.

The typical breaking points

• During the import, both systems remain writable in an uncontrolled manner.
• Go/No-Go is postponed without a named decision-making role.
• Fallback ignores new productive data after startup.

This is what you take with you

The move to X-ERP becomes a guided, decisionable event – not a night of surprises.

Further information / source

Related topics

1. For migration specialists – transfer and optimize data from third-party systems › Test migration, checksums and acceptance
2. For migration specialists – transferring and optimizing data from third-party systems › Basics

Frequently asked questions