High Level Overview

This section provides an overview of the project structure, migration approach and key activities.

💬 Phase 1 – Initiation

This phase introduces the migration process and tools, including the IDaaS Application Migration Portal. Applications listed in ServiceNow’s CMDB are validated, and key stakeholders are identified.

The portal provides visibility into application inventories and migration progress across different regions.

🧭 Phase 2 – Discovery

Delivery managers and migration teams review application data to ensure it is complete and accurate. Any missing metadata is flagged for update.

The portal offers dashboards tailored to different roles, helping users monitor readiness and progress.

🔎 Phase 3 – Assessment

Applications are evaluated against predefined readiness criteria. These include completion of the Application Readiness Review and the presence of an admin account in Entra ID. Applications that meet these requirements are marked as ready in the portal and can proceed to the next phase.

See the section of prerequisites for more information.

📅 Phase 4 – Planning

IDaaS project team coordinate migration timing and assess potential downstream impacts. This phase ensures that all systems and dependencies affected by the migration are identified and prepared for the transition.

🏗️ Phase 5 – Implementation

An application owner initiates the application migration through the portal. Once testing is complete, the application status is manually updated to confirm cutover and signal readiness for production deployment.

⛑️ Phase 6 – Hypercare & Transition

After migration, a four-week hypercare period begins. During this time, the migration team remains available to support troubleshooting and issue resolution. After hypercare, the application transitions to business as usual, and PwC ID integration is disabled 30 days after cutover.

App teams MUST raise a decom request via the portal to decommission the PwC ID endpoints post successful transition to EntraID.