Discover the live source
Atlas reads the configured PingFederate runtime and records its version, applications, protocol settings, signing material, authentication policy, and source evidence digest.
Migration walkthrough
Move from PingFederate without a blind cutover.
See Atlas discover a populated PingFederate estate, reconcile identities and applications, map equivalent controls, and operate both platforms in parallel until each application and cohort is ready to move.
Live workbench capture
One migration journey, entirely inside Atlas.
The walkthrough follows the operator experience from source readiness through inventory, application mapping, control comparison, parallel routing, cohorts, and the final evidence chain.
How it works
Preserve authority while the route changes.
Atlas treats migration as a controlled series of observable application decisions. PingFederate remains the named source route during discovery and early cohorts, and every Atlas route is introduced through a measurable gate.
Normalize and reconcile
Users, groups, memberships, roles, lifecycle state, and application assignments are mapped into the universal directory with source identifiers and conflict status preserved.
Map the controls
OIDC, OAuth, SAML, signing, PKCE, PAR, DPoP, session, lifecycle, and audit objectives are paired with Atlas controls and explicit acceptance tests.
Run both platforms
Each application carries its own active route, Atlas evaluation mode, pilot cohort, readiness evidence, and PingFederate rollback posture.
Move by cohort
Applications progress from observe to shadow, pilot, expansion, and approved cutover only when current evidence and positive and negative protocol tests satisfy the gate.
Bind the evidence
The source snapshot, import preview, reconciliation results, route state, and verification outcome are joined into a reviewable migration receipt.
What the walkthrough covers
Seven views make the migration state visible.
Every view answers a distinct operator question, keeping estate scale, source authority, unresolved work, active routes, rollback, and proof in one continuous story.
Overview
Readiness, estate scale, migration stages, source authority, and the current parallel-run posture.
Inventory
Import progress for identity records, groups, memberships, and the source basis for each object class.
Applications
Twenty-four OAuth/OIDC clients and twelve SAML connections with route, evaluation, rollback, and readiness state.
Control map
Equivalent security objectives, implementation mappings, review items, and evidence tests.
Parallel run
Source-primary, Atlas-shadow, reconciliation, and bounded pilot routes across the application portfolio.
Cohorts and cutover
Independent pilot, mission, and workforce waves with approval, test, and rollback gates.
Evidence
Source snapshot digest, Atlas evidence head, import preview digest, and governed import session.
Continuity model
Cutover is the final route decision, not the first migration action.
Atlas can observe, reconcile, and compare outcomes while PingFederate continues to serve production traffic. The organization changes one approved application and cohort at a time, with the incumbent route retained as the explicit rollback target until acceptance is complete.
Source primaryPingFederate servesAtlas discovers and observes
→Bounded pilotAtlas serves a cohortOutcomes compared and verified
→Approved routeAtlas becomes primaryRollback remains rehearsed