Prove the migration path
30–90 Day PQC Migration Pilot
Move one bounded workload from discovery through governed hybrid or PQC cutover, with rollback, reconciliation, and evidence.
Best forCTOs, platform leaders, application owners, and security teams that need production-shaped proof before a wider programme.
Format30–90 days, depending on scope and dependencies
Commercial modelMilestone-based written quotation after technical scoping
Decision outcomes
What this engagement is designed to answer
The engagement succeeds when the named owners can make and defend the next decision.
A validated target architecture for one agreed workload
A governed migration wave with approvals, recovery controls, and rollback criteria
Measured interoperability and operational impact
A repeatable playbook for the next migration waves
Delivery
What you receive
Final scope and acceptance criteria are captured in the written order form.
01Pilot charter, success measures, and responsibility matrix
02Baseline inventory and dependency map
03Hybrid or PQC target-state implementation
04Cutover, rollback, and recovery exercise evidence
05Reconciliation report and scale-out recommendation
Evidence boundary
Prerequisites and exclusions
These boundaries protect both the buyer and QNSI from treating a scoped engineering engagement as proof it cannot provide.
Prerequisites
- A bounded workload and accountable owner
- Non-production or controlled production change window
- Access to application, identity, key, network, and observability owners
Not automatically included
- Enterprise-wide migration
- Independent assurance or regulatory approval
- Third-party licence and infrastructure charges