Who decides the cut-over date?

You do. We propose a date once a rehearsal migration has run cleanly and the reconciliation report shows no open differences, and a written rollback step stays in place until the old system is retired.

Depth 20.1 · Cloud, data and modernisation · Level 3

Migration

Migration is moving an application, its data and its configuration from one environment to another, such as from an owned server to a cloud account or between cloud providers. Some systems move largely as they are, others need changes to run well in the new place. The decision is made system by system.

Specification

Input: Access to the current environment, the target cloud account, and the owners of each system in scope.
Method: We inventory dependencies, choose for each system whether to move it as is or adapt it, rehearse the move in a copy of production, then cut over with a rollback path ready.
Deliverable: Each system running in the target environment, defined as code, with a cutover record and a tested rollback step.
Measured by: Reconciliation reports for data, matched behaviour on agreed test cases, and incidents during and after cutover.

Most often bought inB2B software, Logistics and supply chain

The artefact, before and after

Each system running in the target environment, defined as code, with a cutover record and a tested rollback step.

Before: a blank migration record with a row for each of dependency inventory, move as is or adapt, decided per system, rehearsal in a production copy, cutover with rollback ready, infrastructure as code in your accounts, and no entries. After: every row carries a finding and a checked status, which is the state the work hands over.

Inside it

01Dependency inventory
02Move as is or adapt, decided per system
03Rehearsal in a production copy
04Cutover with rollback ready
05Infrastructure as code in your accounts

Typical first engagement

The usual order of a first piece of work. Timing and price are set at scoping, once we have seen the stack.

01InventoryYou get: Services, data stores, dependencies and traffic for everything in scope.
02PlanYou get: An order of moves with a rollback for each step.
03RehearsalYou get: A full copy and reconciliation run before the real switch.
04Switch and parallel runYou get: Traffic moved, both systems compared, then the source retired.

Cloud, data and modernisation

Next in this line

A question people ask about this

Who decides the cut-over date?: You do. We propose a date once a rehearsal migration has run cleanly and the reconciliation report shows no open differences, and a written rollback step stays in place until the old system is retired.

Ask about this part of the stack

Write one question about migration in your own systems. We answer it in writing and name what we would need to see to answer it properly.

Send one question

A written reply, no call needed.