Gate 1: establish the baseline and open decisions
| Check | Record to retain |
|---|---|
| Source inventory | Components, versions, configurations and responsible parties. |
| Dependencies | Feeds, execution routes, CRM connections, network rules and operational jobs. |
| Data plan | What is transferred, retained or reconciled and by which approved method. |
| Open decisions | Unknowns, restrictions and the party responsible for resolving them. |
Separate a move of infrastructure from a platform conversion or change in commercial arrangement. They can require different acceptance and data-treatment decisions.
Gate 2: validate the target and the cutover procedure
- Demonstrate the agreed account and operator workflows in the authorised target environment.
- Validate the relevant instrument, pricing and external-connection configuration.
- Record the configuration freeze or synchronisation process.
- Identify the people approving each production change and their communication route.
- Agree stop conditions, reconciliation duties and the decision to return to the previous arrangement.
Document limitations in the target test. An isolated demonstration can leave production routing or external approvals unproven.
Gate 3: reconcile after the switch
Keep a timestamped cutover log and verify the agreed client, operator and integration flows. Check the required data state using the approved reconciliation method. Record unresolved exceptions and their owners before declaring the change complete.
Do not assume rollback is a simple reversal once new activity has occurred. Follow the agreed data and decision process. Use the migration planning guide for the technical method and the migration coordination scope when several providers or teams must complete the gates together.