Migration assessment
Start with an assessment, not a guess
Tell us where you are starting from. The assessment establishes what you are running, what depends on it, and the order in which it can move to Microsoft Entra ID.
What does the assessment produce?
A confirmed source architecture, an application and access inventory, the dependencies and exceptions that need decisions, the treatment for each object category, and a wave sequence with entry and exit criteria. It is the input to the Prepare stage.
What happens next
Three steps after you submit
- We review what you have shared and confirm the source platform and rough scope.
- We agree read access for discovery and what will be inventoried.
- You receive the assessment output: inventory, treatment, exceptions, and a wave sequence.
| Topic | Useful to know |
|---|---|
| Source platform | Okta, PingOne, PingFederate, or a combination. |
| Application estate | Rough application count and the main protocols in use. |
| Provisioning | Whether SCIM or directory synchronization is in place. |
| Constraints | Change freezes, business calendar, and audit requirements. |
MIGRATION ASSESSMENT
Start your migration assessment
Tell us where you are starting from. We use these details to scope the assessment and to discuss the path to Microsoft Entra ID that fits your environment.
Assessment questions
What is a migration assessment?
A structured review of your source identity platform that establishes the architecture in use, inventories applications and access, identifies dependencies and exceptions, and produces a sequenced migration plan for Microsoft Entra ID.
What do you need from us to start?
The source platform you are moving from, a sense of the application estate, and a named owner on your side. Read access for discovery is agreed before anything is collected.
Are we committing to a migration by requesting an assessment?
No. The assessment establishes scope, dependencies, and sequencing. What you do with that plan is your decision.