Last reviewed 10 November 2026
Coordinating a migration across the organisation
This route is for a migration lead who is coordinating many assets across the organisation.
Handbook practice: Each role supplies one input to the plan.
| Role | Input |
|---|---|
| Executive sponsor | The decision to proceed |
| Migration lead | The one-page plan |
| Asset owners | The system and its unknowns |
| Procurement | The supplier questions |
| Legal or risk | The confidentiality period and the applicable timeline |
| Operations | The change window and the rollback owner |
| Suppliers | The product, version, and the answer |
Read in this order for the handbook's six steps:
- Decide whether the handbook applies and name an owner.
- Find cryptographic dependencies and record unknowns.
- Assess confidentiality period, importance, and constraints.
- Prioritise and choose a source-backed path.
- Engage suppliers and migrate.
- Verify what changed and set the subsequent review.
Handbook practice, citing ASD's planning for post-quantum cryptography publication: name an owner is the handbook's step before LATICE; find dependencies is Locate; assess the confidentiality period and constraints is Assess; prioritise is Triage; engage suppliers and migrate is Implement; verify the change, communicate it, and set the subsequent review is Communicate and educate. The handbook's six-step list and LATICE do not have the same number of steps.
A large bespoke estate, critical national infrastructure, or a regulated system needs a specialist as well as this route.
Then read these pages in order:
The output is a one-page migration plan with an owner for each asset and a subsequent-review date.
Primary next page: Migration plan.
Sources
- ASD, Planning for post-quantum cryptography. Planning publication
- ETSI, TR 104 016, October 2024. TR 104 016