SCIM Provisioning During an ERP Cutover: What to Freeze, What to Sync
Blog post from SSOJet
ERP cutovers create significant identity-management risks because legacy and new systems must operate simultaneously while HR-driven joiner, mover, and leaver events continue. The recommended approach is to treat identity as a formal migration workstream, establish a stable `externalId` such as an employee ID for reconciliation, freeze structural changes to roles, groups, and SCIM attribute mappings after testing begins, and continue provisioning and especially deprovisioning throughout the transition. Organizations should shadow-provision the new ERP through a second Okta or Microsoft Entra ID SCIM application assigned to the same groups, then reconcile users, memberships, roles, and integration accounts across the identity provider and both ERPs daily, treating unexplained differences as go-live blockers. Because Okta generally deactivates rather than deletes users and Entra provisioning runs on scheduled cycles, cutover runbooks should include on-demand provisioning for urgent terminations and test how each ERP handles SCIM deactivation requests. On go-live, the new ERP should become the access authority while legacy accounts are made read-only or deactivated rather than deleted, preserving audit records and enabling a simpler rollback; after successful operation through month-end, teams can retire the legacy connector, archive access records, review unused roles, and move non-human accounts to more secure credential-management methods.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Platform Engineering | 13 | 2,014 | 399 | 102 | +19% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.