Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Post-quantum migration planning is the programme of discovering where your organisation uses vulnerable cryptography, ranking it by risk, and replacing it before the published deadlines.

What Is Post-Quantum Migration Planning?
Replacing RSA and elliptic curve cryptography across a large organisation is not a patching exercise. It touches TLS termination, VPNs, internal PKI, code signing, device identity, payment hardware, database encryption, and every supplier product in between. The SHA-1 transition took the industry roughly a decade and affected only hashing. This one is bigger, and it has published deadlines.
Migration planning is the programme management around that work: finding the cryptography, deciding what moves first, securing budget and supplier commitments, and sequencing changes so that nothing breaks in the middle.
NCSC guidance issued in 2025 sets out three milestones for UK organisations:
NIST’s draft IR 8547 aligns with this, indicating deprecation of 112-bit classical public key cryptography around 2030 and disallowance by 2035. Regulated sectors are adding their own expectations, and the financial sector in particular is being asked by supervisors how post-quantum risk features in ICT risk management under DORA.
Discovery is the longest phase and the one organisations consistently underestimate. The output is a cryptographic bill of materials recording, for each system: which algorithms and key lengths are in use, where keys live, who owns them, which protocols and certificates are involved, whether the component can be upgraded, and how long the data it protects must remain confidential.
Draw from several sources, because no single one is complete:
Rank by two variables: how long the data must stay confidential, and how hard the system is to change. The first drives urgency, because of harvest now, decrypt later collection; the second drives lead time.
| Priority | Typical systems | Why |
|---|---|---|
| Highest | Long-lived confidential traffic: replication links, backup transfer, site-to-site VPNs, health and legal records in transit | Recorded today, readable later; few endpoints to change |
| High | Roots of trust: internal CA hierarchies, code signing, firmware verification keys | Long validity periods and hard to replace once deployed |
| Medium | External-facing TLS, API gateways, identity providers | Hybrid key exchange is available now, so change is cheap |
| Longest lead | Smart cards, TPMs, payment HSMs, OT and IoT devices | Algorithms in silicon; requires a hardware refresh cycle |
Start with the changes that are already available and low risk. Enabling hybrid key exchange on web servers, CDNs, and SSH is a configuration task today, and it immediately protects recorded traffic. Moving symmetric encryption to AES-256 is similarly cheap.
Then address the structural work. Build crypto agility into the systems you are touching anyway: version ciphertext, centralise cryptographic calls, separate key references from key material. Put algorithm requirements into procurement and renewal terms. Align hardware replacement with existing refresh cycles rather than funding a separate programme. And test through every intermediary, because larger handshakes and certificates break middleboxes in ways that unit tests will not reveal.
Give the programme a named owner, a board-level reporting line, and a budget separate from business-as-usual patching, because without those it will be deferred every quarter in favour of something with a nearer deadline.
Three mistakes recur. Treating 2035 as the start date, when discovery alone takes years in a large estate. Deploying non-standardised algorithms from earlier competition rounds, which creates a second migration. And assuming suppliers will handle it silently, when in reality their roadmaps are the long pole and only contractual pressure moves them. We scope and run discovery exercises as part of our cyber risk analysis services, which is usually what turns a stated intention into a dated plan.
With discovery, not with technology selection. Scan your endpoints, search your code, pull certificate and key inventories, and question suppliers. Until you know where vulnerable cryptography lives and what data it protects, any prioritisation is guesswork. Most organisations find the inventory itself takes longer than the first wave of changes.
A structured inventory of the cryptography in your estate: algorithms, key lengths, key locations and owners, protocols, certificates, the systems involved, and the confidentiality lifetime of the data concerned. It is the post-quantum equivalent of a software bill of materials, and it is the artefact auditors and regulators will increasingly ask to see.
The main standards settled in August 2024, so the waiting argument has largely expired. Hybrid key exchange is deployed by Chrome, OpenSSH, Apple, and the major CDNs. What remains unsettled is post-quantum certificates, which is a reason to sequence signatures later, not a reason to delay discovery or confidentiality work.
Ask now, in writing, what each product supports and when post-quantum algorithms will arrive, and add the requirement to contracts and renewals. For hardware with algorithms fixed in silicon, map the devices against your refresh cycle and bring replacements forward where the data warrants it. These are the longest lead times in the programme.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.