# ERP migration – editable cutover plan

SYNQ · 24 September 2026 · Version: [complete]

Planning aid, not a finished operational or recovery procedure. Adapt, test and approve it for your systems. It does not guarantee zero data loss or uninterrupted operation.

## 1. Scope and responsibility

- Source systems / versions / technical owners: [complete]
- Target system / version / technical owner: [complete]
- Data objects and volumes: [complete]
- Dependencies and connected systems: [complete]
- Project lead / deputy: [complete]
- Business acceptance owner / deputy: [complete]
- Go/no-go decision owner: [complete]

## 2. Migration, archive and exclusions

| Dataset | Migrate / archive / other handling | Reason | Owner | Evidence / access check |
|---|---|---|---|---|
| [complete] | | | | |

Retention, deletion, privacy and document-access review: [owner / decision reference]. Do not delete data solely on the basis of this template.

## 3. Mapping and test evidence

- Register: erp-migration-en.csv
- Approved mapping version: [complete]
- Export / test snapshot: [complete]
- Import order based on dependencies: [complete]
- Required values / error list / decision owner: [complete]
- Repeated import checked for unintended duplicates: [evidence]
- Count / total reconciliation with identical filters: [evidence]
- Business samples and permission checks: [evidence]

## 4. Prepare cutover

- Planned cut-off: [complete]
- Write freeze or capture of final changes: [rule]
- New / changed / deleted record handling: [rule]
- Authoritative system per process during transition: [complete]
- Backup and tested restoration: [reference]
- Rehearsal, outcome and open issues: [reference]
- Team / partner communication: [plan / owner]

| Step | Prerequisite | Operator / deputy | Planned window | Verification evidence | Approval |
|---|---|---|---|---|---|
| Control changes | [complete] | | | | |
| Produce final snapshot | [complete] | | | | |
| Import | [complete] | | | | |
| Reconcile and verify business use | [complete] | | | | |
| Decide launch or fallback | [complete] | | | | |
| Enable write access | [complete] | | | | |

## 5. Abort and fallback

- Concrete abort criteria: [complete]
- Last point for planned fallback: [complete]
- Trigger / decision owner: [complete]
- Restoration steps and tested evidence: [reference]
- Handling of transactions already created or changed in the target: [rule]
- If fallback is no longer possible: [escalation / correction plan]
- Communication and authorisation to resume the legacy system: [plan]

## 6. Post-launch checks and completion

- Initial live transactions / documents checked: [evidence]
- Interfaces and exports checked: [evidence]
- Remaining issues and owners: [list]
- Support route and monitoring: [complete]
- Archive / legacy access secured and checked: [evidence]
- Legacy retirement approved by business and technical owners: [date / owners]
- Migration acceptance: [version / date / owners]