A Plain English Post-Quantum Migration Checklist for Companies
Do not panic, do plan
No one has publicly shown a quantum computer able to break RSA or elliptic curves today. But migrations take years, data stolen now can be read later (harvest now, decrypt later), and the tools to protect yourself are already shipping. The good news: much of the work is ordinary IT housekeeping, and a lot of it is free because browsers, operating systems and cloud providers are doing it by default. Here is a practical checklist.
Step 1: Make an inventory
List every place your company uses public key cryptography: websites, VPNs, SSH, internal services, email signing, code signing, device certificates, databases, backups, payment systems, third party APIs and anything your vendors run for you. Europol's January 21, 2026 report on financial services calls inventory of business use cases that rely on public key cryptography a critical first step. You cannot fix what you cannot find. Why this matters: RSA and elliptic curves are the algorithms at risk.
Step 2: Rank by risk
The Europol report, developed with the Quantum Safe Financial Forum and partners, scores each use case on three things: the shelf life of the protected data (how long it must stay secret), its exposure (how reachable it is for attackers) and the severity of a compromise. It then adds a migration time score, covering things like solution availability, cost and third party dependencies. A medical record or a state secret has a long shelf life and goes to the top. A one-day session token goes lower.
Step 3: Take the easy wins now
- Turn on hybrid key exchange where it exists. Many CDNs and browsers already use it (how it works). Check the hop between your CDN and your own servers, which Cloudflare's reporting suggests lags the browser side.
- Upgrade SSH. OpenSSH reports ML-KEM hybrid as default from version 10.0, and version 10.1 warns on non-post-quantum connections (details).
- Update libraries and operating systems so they include ML-KEM support, for example OpenSSL 3.5 or later, as listed in Cloudflare's documentation.
- Remove weak and outdated cryptography that adds technical debt. The Europol framework highlights avoiding cryptographic antipatterns as a way to speed later migration.
Step 4: Build crypto agility
Do not hard-code algorithms. Put cryptography behind configuration and libraries you can update, document where keys live, and automate certificate renewal. The goal is to swap algorithms like changing a lightbulb, not rewiring the building. Read crypto agility explained.
Step 5: Ask vendors the right questions
Ask every important supplier: Which NIST standards (FIPS 203, 204, 205) do you support? When? Do you offer hybrid modes? What is your plan for signatures and certificates? Put answers in contracts and renewals. Be wary of vague "quantum-safe" marketing; ask for the standard name. The status of the standards is in the standards status guide.
Step 6: Plan for signatures and PKI
Key exchange is easiest. Signatures and certificates are harder because of size and ecosystem coordination (PKI guide). Start with long-lived things: firmware signing keys, device identities, document signing archives and private root certificates. Pilot ML-DSA in test environments, and watch what Chrome and other browsers decide.
Step 7: Test, then roll out in stages
Larger handshakes can upset old firewalls and load balancers. Test in a lab, pilot with a small group, monitor errors and performance, then widen. Keep a classical fallback during the transition (hybrid is ideal).
Step 8: Track the deadlines
NIST says it plans to deprecate and ultimately remove quantum-vulnerable algorithms by 2035, with high-risk systems earlier. US federal directions are summarized in the deadlines guide. Cloudflare reported moving its own full post-quantum target to 2029, a useful benchmark for how fast a well-resourced company can move, though your timeline will differ.
What about banks?
Financial firms hold long-lived sensitive data and so are early movers. The Europol-led report gives them a risk-based method, and commentary links it to earlier work from the Bank for International Settlements (a July 2025 readiness roadmap, which I did not read directly). One project cited in coverage is QuSecure with Banco Sabadell and Accenture. If you are a small business, you do not need a bank-sized program, but the same order applies: inventory, rank, upgrade, ask.
A simple one-page summary
- Inventory public key use.
- Rank by data shelf life and exposure.
- Enable hybrid ML-KEM and update software.
- Build agility and automate certificates.
- Question vendors and get dates in writing.
- Pilot post-quantum signatures for long-lived keys.
- Test, stage, monitor.
The mood here should be confident, not fearful. The threat is manageable, the standards exist and a plan beats a panic. Nothing here is legal, security or financial advice, and the QNT memecoin is independent of Quantinuum Ltd and unrelated to any migration program or vendor mentioned. See the risk factors.
Sources and further reading
- eucrim: Europol report on post-quantum migration for financial institutions (January 21, 2026 report)
- Europol: call for action on the transition to post-quantum cryptography
- OpenSSH: post-quantum cryptography
- Cloudflare docs: post-quantum support list
- NIST: post-quantum cryptography project
- Cloudflare blog: 2029 target (April 30, 2026)
Reported as of 2026-10-09. Standards and rollout numbers change often, so check the primary documents before relying on any figure. This is education, not financial advice. The QNT memecoin is independent of Quantinuum Ltd, the real company, and of any lab or government.
Frequently asked questions
Where should a company start with post-quantum migration?
With an inventory of everything that uses public key cryptography, then rank each use by how long its data must stay secret and how exposed it is.
Can a small business skip this?
Not entirely, but much of the work is automatic: updating browsers, operating systems, CDNs and SSH gets you key exchange protection. Ask vendors about their plans.
What are the quick wins?
Enable hybrid ML-KEM where available, upgrade OpenSSH and TLS libraries, remove weak cryptography and automate certificate renewal.
Do banks have specific guidance?
Europol and partners published a risk based prioritisation report for financial services on January 21, 2026.
Does this tell me anything about buying QNT?
No. The token is an independent memecoin, unrelated to any company or program here. Nothing on this page is financial advice.
Keep reading
- Crypto Agility Explained: Preparing for Algorithm Change
Crypto agility is the ability to swap cryptographic algorithms without rebuilding a system. Learn why it matters for the post-quantum shift and for blockchains. - Harvest Now, Decrypt Later: The Quantum Threat Explained
Harvest now, decrypt later means collecting encrypted data today to unlock it with a future quantum computer. What it is and who should care. - Government Post-Quantum Deadlines: NIST, NSA CNSA 2.0 and Federal Migration
The dates governments have set to move off RSA and elliptic curves: NIST 2030 and 2035, NSA CNSA 2.0 milestones, and the January 1, 2027 acquisition rule. - Hybrid Key Exchange in TLS Explained: How Your Browser Is Already Quantum Ready
A plain English guide to X25519MLKEM768, the hybrid handshake that now protects a large share of web traffic against harvest now, decrypt later attacks.
All Quantum policy and governments guides | Back to top | Search the site
Main pages: Quantum computing explained | Quantum and crypto | Companies | Quantum news | Glossary