OpenText migration
Transition from OpenText Identity Manager to Microsoft Entra in controlled stages.
UNIFY helps customers move from Novell, NetIQ, and OpenText Identity Manager environments to Microsoft Entra using coexistence, function-by-function transition, and clear control evidence.
From OpenText Identity Manager to Entra
Many identity estates still carry design choices made when Novell Identity Manager, NetIQ Identity Manager, or OpenText Identity Manager sat at the centre of provisioning, directory synchronisation, and governance workflows. Those environments often remain deeply connected to line-of-business applications, authoritative sources, and operational processes that cannot simply be turned off.
Modernising to Microsoft Entra rarely succeeds as a single replacement event. In practice, the transition usually requires coexistence, staged migration, and a clear control model that preserves continuity while legacy functions are progressively retired or reworked.
- A phased transition is often safer than a forced cutover.
- Some legacy capabilities can be retired quickly; others need to coexist for longer.
- The goal is controlled modernisation, not a cosmetic platform swap.
Executive Summary
Microsoft Entra gives organisations a stronger modern identity control plane for access, governance, and cloud-era security patterns. But many organisations considering Entra still depend on legacy Identity Manager implementations for connectors, workflow logic, entitlement handling, and downstream provisioning.
That is why this transition needs to be treated as an architecture and delivery problem rather than just a product replacement exercise. Success depends on understanding which functions are truly being performed today, where authoritative data lives, which integrations remain business critical, and how those capabilities can be migrated or contained without operational disruption.
UNIFY supports this transition with a pragmatic approach:
Coexistence before retirement
Retain legacy components where needed while Entra-aligned services are introduced in a controlled sequence.
Function-by-function transition
Separate provisioning, governance, directory, and presentation concerns so they can move at different speeds.
Control and evidence first
Prioritise auditability, access assurance, and operational traceability throughout the change.
Modernisation with continuity
Use integration and orchestration patterns to connect legacy dependencies to the modern control plane while transition work continues.
This allows organisations to modernise toward Entra without assuming that every downstream application, workflow, or directory dependency is ready to move on day one.
Why These Environments Are Hard To Replace
Legacy Identity Manager environments often do much more than they first appear to do. Over time, they may have become responsible for:
Directory synchronisation
Moving identity data between HR systems, directories, and business applications with logic accumulated over many years.
Provisioning workflows
Creating, updating, suspending, or removing access across applications that may not support modern standards natively.
Governance controls
Embedding approvals, role handling, attestation, or lifecycle decisions inside a platform that was never documented as a single business process.
Custom integrations
Maintaining brittle but business-critical links to LDAP directories, file-based processes, service desks, or specialist applications.
That hidden complexity is why big-bang replacement is often the wrong assumption. Before anything is migrated, organisations usually need a clear inventory of what the legacy platform is really doing and which outcomes must remain intact.
A Practical Transition Pattern
Most successful transitions to Entra follow a staged pattern rather than a single migration event:
1. Discover
Map connectors, workflows, authoritative sources, entitlement logic, and application dependencies so the current operating model is understood.
2. Separate concerns
Identify which responsibilities belong in Entra, which require an integration layer, and which remain temporarily in the legacy platform.
3. Run in parallel
Introduce modern identity controls and selective cutovers while preserving service continuity for systems not yet ready to change.
4. Transition by cohort
Move applications, identity domains, or lifecycle functions in manageable groups based on readiness, risk, and business criticality.
5. Retire deliberately
Decommission legacy components only after target-state controls, evidence, and operational support arrangements are proven.
This approach reduces delivery risk and avoids forcing every part of the identity estate to modernise at the same pace.
Coexistence Is Usually Part Of The Plan
In many environments, OpenText Identity Manager remains important during transition because some capabilities are still anchored to legacy applications or operating models. Coexistence can be used to:
Preserve downstream integrations
Keep critical provisioning and reconciliation patterns running while replacement interfaces are built or simplified.
Protect control outcomes
Maintain joiner, mover, leaver, and access governance behaviour while new controls are introduced in Entra.
Contain legacy dependencies
Allow hard-to-replace directories, authentication dependencies, or application connectors to remain stable during broader modernisation.
Sequence operational change
Give support teams, business owners, and assurance stakeholders time to validate new patterns before legacy functions are withdrawn.
Coexistence does not mean keeping two strategies forever. It means using time deliberately so modernisation can be governed rather than rushed.
What Moves To Entra
The destination architecture varies, but Microsoft Entra is commonly used to take on a growing share of:
Modern access control
Conditional access, stronger authentication, external identity, and policy-driven access outcomes.
Lifecycle and governance
Identity governance, access review, entitlement handling, and modern lifecycle controls where they align with the target operating model.
Cloud-era integration patterns
API-based provisioning, standards-based federation, and cleaner application onboarding for systems ready to align with Entra.
A more durable control plane
Centralised identity policy and evidence that better supports audit, security uplift, and ongoing architecture simplification.
Where native Entra capability is not enough on its own, organisations often need an additional orchestration layer to bridge authoritative sources, legacy targets, and staged delivery requirements. That is where UNIFYConnect can support a practical transition model.
What Good Looks Like
A successful transition away from Novell, NetIQ, or OpenText Identity Manager is not defined by how quickly a legacy platform disappears. It is defined by whether the organisation ends up with:
Clear visibility
An understood identity architecture with known ownership, dependencies, and control points.
Operational stability
A modernised platform that improves security and governance without destabilising the applications and processes the business still depends on.
Provable assurance
Evidence that lifecycle, access, and governance outcomes remain effective throughout the transition.
A realistic end state
A target model that can evolve over time rather than recreating another tightly coupled legacy stack.
If your organisation is planning how to move from OpenText Identity Manager toward Entra, UNIFY can help shape a roadmap that reflects the reality of your environment rather than forcing a one-size-fits-all migration story.
Talk to UNIFY