Skip to main content

Legacy migration

Legacy IDM migration to a modern stack

Oracle IM, IBM SIM, CA Identity Suite, Microsoft MIM/FIM — migrated to SailPoint or Evolveum midPoint with phased cutover.

Talk to an architect
Migration · Workflow Six-step path

What we deliver

Full migration from legacy IDM stacks — including the opportunity to fix what was wrong on day one.

Migration stages

  • Discovery and gap analysis

    Inventory of identity stores, target apps, custom code, integrations. Risk register and target platform recommendation.

  • Target platform selection

    Decision framework: SailPoint ISC / IIQ vs Evolveum midPoint. TCO, fit-for-purpose, vendor strategy.

  • Phased cutover plan

    Source-by-source migration, parallel-run during validation windows, rollback procedures, communication plan.

  • Identity model harmonisation

    Attribute lineage, identity merge / split, role re-baseline. Opportunity to fix what was wrong on day one of the legacy stack.

  • Custom code re-implementation

    Workflows, connectors, adapters re-written in the target platform's idiom — not 1:1 ported.

  • Decommissioning and audit

    Controlled shutdown of the legacy environment, archive of audit trails, final-state validation.

Source platforms we migrate

  • Oracle Identity Manager / OIG
  • IBM Security Identity Manager (SIM)
  • CA Identity Suite
  • Microsoft MIM / FIM, OneIdentity, Sun IM

Start with assessment

2–3 week migration assessment — risk register, target platform recommendation and phased plan before any cutover.

See Modernization Concept →