3-year cost calculator
Pre-filled for Microsoft Entra ID → ForgeRock. Adjust every figure with your own numbers.
Every figure here is an illustrative estimate, not a vendor quote. Defaults are editable starting points compiled from public information; real, binding pricing comes from the vendor or an authorized distributor. See our methodology.
All figures are illustrative and fully editable — adjust the cost-per-user and migration inputs with your own numbers. Not guaranteed vendor pricing (defaults reviewed May 2026). For a binding quote, use the request form below to reach an authorized distributor or partner.
Quick comparison: Microsoft Entra ID vs ForgeRock
Common trade-offs teams weigh when staying on Microsoft Entra ID versus moving to ForgeRock. These are general, commonly-reported considerations — not statements of fact about any vendor — so check them against your own contract and the vendors' current terms.
- Already in production — no migration effort or risk
- Mature ecosystem with vendor support and SLAs
- P1/P2 licensing tied to Microsoft 365 tiers
- Advanced features gated behind premium SKUs
- Per-user costs across the whole directory
- Deep coupling to the Microsoft ecosystem
- Ongoing per-user (p1 / p2) cost to budget for
- Higher vendor lock-in to weigh
- Commercial option with vendor support and SLAs
- Cost model: Per-user + modules
- Requires a migration (~18 weeks, high effort)
- Per-user + modules cost
- Higher operational learning curve
Why teams evaluate alternatives to Microsoft Entra ID
Reasons commonly cited by users and in public industry coverage for re-evaluating Microsoft Entra ID. These are general, reported considerations — not statements of fact about Microsoft — and may not reflect your situation or the vendor's current terms. Verify against your own contract before deciding.
- P1/P2 licensing tied to Microsoft 365 tiers
- Advanced features gated behind premium SKUs
- Per-user costs across the whole directory
- Deep coupling to the Microsoft ecosystem
The migration plan
Roughly 18 weeks for a mid-size estate, in six phases.
Tooling & automation
Stand up the new identity provider, import users and groups via LDAP/SCIM, re-register applications as OIDC/SAML clients, migrate MFA enrollment, and cut over app by app.
OffVendor's wizard pre-fills these scripts with your environment — inventory export, disk/schema conversion, bulk provisioning, and validation.
Frequently asked
Is migrating from Microsoft Entra ID to ForgeRock worth it?
For most teams facing rising Microsoft Entra ID costs, yes — ForgeRock (per-user + modules) typically lowers 3-year total cost of ownership, though the right answer depends on workload complexity and in-house skills. Use the calculator to model your own numbers.
How long does a Microsoft Entra ID to ForgeRock migration take?
A typical mid-size estimate is around 18 weeks across six phases — discovery, design, pilot, waved production migration, validation, and decommission. Larger or more complex estates take longer.
What tools are used to migrate from Microsoft Entra ID to ForgeRock?
Stand up the new identity provider, import users and groups via LDAP/SCIM, re-register applications as OIDC/SAML clients, migrate MFA enrollment, and cut over app by app.