Migrations are where estates drift into exposure. A legacy system runs alongside its replacement during a transition, and a metric that counts both can turn an ordinary upgrade into a finding. OpenPass migration rights, expressed as dual entitlements, exist to cover that overlap. Used carefully, they let a buyer carry legacy entitlements forward and run the old and the new in parallel without a double count. Used carelessly, the overlap window expires mid project and the parallel run becomes the basis of the next claim.
OpenText expects estates to move: between deployment models, between product versions, and into the cloud. The framework builds in the overlap that migration requires, which is one of its genuine advantages over a patchwork of older schedules. But migration rights are only as strong as their drafting, and the buyer who assumes the overlap is automatic and unlimited discovers otherwise when the audit clock starts.
What dual entitlements grant
Dual entitlements grant the right to run a legacy deployment and its replacement at the same time during a defined migration window, without being counted as two separate licensed deployments. Without that right, a migration creates a temporary period of apparent overuse: the same workload, licensed once, appears to run twice. A metric that counts both, and an audit timed during the transition, produces a finding for usage that is entirely legitimate. Dual entitlements remove that artefact by recognising that a migration is one workload in transition, not two workloads in production. The mechanics of how they apply during a transition are covered in dual entitlements during an OpenPass migration.
A migration is one workload in transition, not two workloads in production. Dual entitlements exist to make the contract see it that way. Without them, an ordinary upgrade looks like overuse.
The drafting that decides whether the right holds
The value of a migration right lives in three details: the length of the overlap window, the scope of what it covers, and what happens when it ends. An overlap window too short for a realistic project timeline forces the buyer to choose between rushing the migration and falling out of compliance. A window that covers only some products in the estate leaves the others exposed. And a window that ends abruptly, with no grace for a delayed cutover, turns a slipped project plan into a finding. Each of these should be negotiated explicitly rather than accepted as drafted, because the vendor's default tends toward the narrowest reading of all three.
The buyer should align the overlap window with the actual project plan, with margin for the delays that real migrations encounter, and should ensure it covers every product line involved in the transition. This is part of negotiating the agreement as a whole, which is why migration rights belong in our OpenPass enterprise agreement negotiation work and should be negotiated alongside the other protections in audit protections to negotiate into an OpenPass agreement.
Carrying legacy entitlements forward
Beyond the overlap itself, there is the question of how legacy entitlements convert into the new agreement. An estate that has held entitlements for years, often across both OpenText's own ECM line and the Micro Focus products acquired later, brings a complex history into the OpenPass conversion. The ECM line, including Documentum, Extended ECM, Content Suite, eDOCS, and InfoArchive, is governed by the OpenText end user license agreement. The Micro Focus security, DevOps, and COBOL products are mostly governed by the Additional License Authorizations. Carrying both sets of legacy entitlements forward correctly means reading both governing frameworks, which is the work of our ALA and entitlement review track.
The risk in conversion is that legacy entitlements are undercounted, so the buyer pays again for rights it already holds, or that they are mischaracterised, so the new metric counts them differently from the old. The defense is the same reconstruction that underpins any OpenPass negotiation: an independent view of what the estate actually holds and uses, set out in building an OpenPass target baseline before negotiation. Legacy entitlements are an asset, and they should be carried into the new agreement at their full value, not quietly discounted in the conversion.
Where migration rights meet the audit
Migration is one of the most common triggers for a finding, precisely because the overlap creates the appearance of overuse. An audit timed during a transition, against a metric that counts both the legacy and the replacement systems, can produce a large number from entirely legitimate activity. A buyer with well drafted dual entitlements can answer that finding by pointing to the migration right. A buyer without them faces a finding priced at full list, with back maintenance and audit cost stacked on top, for running a migration the vendor expected them to run. The way a finding like this is reduced and converted forward is set out in converting an audit finding into a clean OpenPass deal.
How this works in practice
In a recent engagement, an estate midway through a platform migration faced a finding that counted both the legacy system and its replacement as separate production deployments. The defense rested on the migration context: the two systems represented one workload in transition, and the parallel run was a normal feature of the project, not additional consumption. Reconstructing the position to show the migration timeline, and then writing dual entitlements with an adequate overlap window into the forward agreement, removed both the present finding and the future risk. The same workload could complete its migration without generating another claim. The broader method behind this sits in the complete OpenText audit defense playbook, and comparable outcomes are collected in our engagements.
Protecting the transition
Migration rights and legacy entitlements are two sides of the same protection: the right to move without paying twice, and the right to carry forward what you already hold. Negotiate the overlap window to match a realistic project plan, ensure it covers every product in the transition, and reconstruct your legacy entitlements so they convert at full value. Done well, the migration completes without a finding and the legacy rights survive the conversion intact. Done poorly, an ordinary upgrade becomes the vendor's next claim. If you are migrating an OpenText or Micro Focus estate, or converting into OpenPass during a transition, open a case before the overlap becomes an exposure.
When an OpenText or Micro Focus audit notice arrives, the first seven days carry more weight than any week that follows them. OpenText Audit Defense is an independent, buyer side firm founded in 2020 by former vendor compliance leadership. Across more than 200 defended audits we have reduced the average finding by 68 percent and mitigated more than $90M in claims against vendor positions. We do not resell OpenText software and we are not affiliated with OpenText Corporation. To open a case, use the contact form on this site.