PLATFORM MODERNISATION BRIEF
Migration map for a scope
A completed fictional example, then a 6-item grid to prepare a meeting between application owners, the data team, operations and the business. The map brings together the scope, the expected evidence, the sign-offs and the rollback conditions; it is not an executable migration plan.
2-page map: page 1, completed fictional example; page 2, 6 fields to fill in directly in the PDF. Typed text is kept when you save.
Completed example (fictional)
| Item | Fictional example: first cutover scope |
|---|---|
| Scope and uses | A dataset feeding an application, an invoicing process, a partner export and reporting; uses to preserve, exclusions and still-unknown uses flagged. |
| Dependencies and owners | Applications, flows, rules and owners connected; hand-reworked export and poorly documented legacy process to check; one named approver per use. |
| Reference and tests | Time reference, filters, units and special cases set before acceptance testing; checks on results, availability times, access rights and the behaviour of consuming applications. |
| Sequence and go-ahead | Order of operations and interruption points; person authorised to decide, criteria, sign-offs obtained and acceptable reservations; rehearsal in a suitable environment. |
| Stop, rollback and new writes | Triggers and owner; operations recorded after the cutover kept, reconciled or replayed without loss or duplicates; outputs already distributed; point beyond which a recovery or correction procedure becomes necessary. |
| Monitoring, evidence and date | Immediate post-cutover checks, observation period and alert recipients; expected evidence per check; review date (fictional example: no real date). |
Blank grid
| Item | Your scope |
|---|---|
| Scope and uses | |
| Dependencies and owners | |
| Reference and tests | |
| Sequence and go-ahead | |
| Stop, rollback and new writes | |
| Monitoring, evidence and date |