Use robust criteria: data sensitivity (confidential, regulated, critical), data lifetime (confidential beyond 5–10 years?), system criticality, cryptographic exposure (asymmetric used?), dependency and control (internal vs vendor). Prioritisation should be documented, not intuitive; it enables risk tiers and clear trade-offs.
Strategy does not equal immediate migration. Short-term: visibility, documentation, monitoring, awareness. Medium-term: pilots, crypto-agile approaches, procurement requirements, policy updates. Long-term: phased migration for high-priority assets, mature standards. Staged approach reduces risk and avoids lock-in to immature solutions.
Communication should avoid alarmism and false certainty; focus on preparedness and governance. Explain why some assets are prioritized, why immediate migration is not always appropriate, how decisions are reviewed. A well-articulated strategy often matters more than early technical action.