Post-quantum cryptography is unusual because the hard part is not waiting for the threat. The hard part is moving before the threat fully arrives. If organisations wait for an undeniable “Q-Day” headline before acting, they will already be late. The transition from quantum-vulnerable public-key cryptography to quantum-resistant alternatives will take years, touch thousands of systems, and depend on vendors, protocols, certificates, hardware, applications and supply chains that most enterprises do not fully map today.

NIST’s message is now unambiguous: the first PQC standards are final and ready to be implemented, and organisations should begin the transition immediately. Google Cloud’s latest roadmap says it plans to achieve full post-quantum readiness by 2029. The UK National Cyber Security Centre says 2035 is the target date for completing migration, with a phased roadmap that starts now and reaches the first major planning milestone by 2028.

These are not contradictory positions. They describe the same reality from different angles. Google is stating a cloud-provider target. NCSC is setting a broader ecosystem deadline. NIST is saying that organisations no longer have a standards excuse to delay. Together they imply something clear: the migration window has already opened.

The Risk Date Is Uncertain. The Migration Dates Are Not.

The temptation is to debate which date is “right.” That is mostly the wrong argument. Migration planning should not be driven by a single predicted year when quantum computers become cryptographically relevant. It should be driven by data sensitivity, system lifetime, regulatory exposure and the sheer organisational effort required to replace vulnerable cryptography in a controlled way.

“Harvest Now, Decrypt Later” Means the Risk Can Begin Years Before the Breakthrough.

The clearest reason to start early is not a working quantum computer tomorrow. It is the possibility that adversaries collect encrypted traffic and stored data now, intending to decrypt it later when enough quantum capability exists. NIST, Google Cloud and multiple national cyber agencies explicitly point to this store-now-decrypt-later scenario as a reason to move before the technology becomes operational at scale.

In other words, the first migration priority is not “everything.” It is the subset of systems whose confidentiality, authenticity or integrity requirements extend far enough into the future that quantum compromise would still matter.

Post-Quantum Migration Is Mostly an Inventory and Agility Problem.

The public narrative often treats PQC migration as an algorithm swap. In practice it is much closer to a technology estate transformation. Organisations need to know where public-key cryptography is used, which applications depend on it, which certificate chains and HSMs are involved, which protocols need hybrid support, which devices cannot be upgraded, and which third-party products remain blocked on vendor roadmaps.

The Algorithms Are Ready. The Ecosystem Around Them Is Not Fully Finished.

NIST’s first finalised standards — ML-KEM for key establishment and ML-DSA and SLH-DSA for digital signatures — removed a major source of uncertainty. But standardisation is only the start of deployment. Products, libraries, certificate frameworks, firmware, embedded systems and procurement processes all need to adapt.

This is why the organisations that start earliest may not be the ones panicking about quantum headlines. They may simply be the ones with the best cryptographic discipline: strong asset inventories, clear data classification, upgradeable architectures and procurement teams that already ask vendors for quantum roadmaps.

Six Enterprise Moves for the PQC Transition

The most important cultural change may be this: stop asking whether quantum computers are “really close.” That question sounds practical, but it often becomes an excuse for paralysis. The more useful question is whether the organisation is becoming easier or harder to migrate. Every year spent improving cryptographic agility is helpful even if Q-Day arrives later than expected. Every year spent ignoring the issue increases the eventual transition cost.