OpenText ECM cloud migration and dual entitlement

Moving an ECM estate to the cloud rarely happens overnight. For months, sometimes longer, the old on premises system and the new cloud platform both run. That overlap is a normal feature of a careful migration, and it is also the exact window an audit reads as paying for the same thing twice.

A migration of Documentum, Extended ECM, or Content Suite to a cloud platform is a phased exercise. Content is copied, validated, and cut over in stages, and during that period the source system stays available so the business keeps working and so nothing is lost if a phase has to be rolled back. Running both estates at once is sound practice, but it produces a license picture in which the same users and the same content appear in two places. Dual entitlement is the contractual mechanism that allows this overlap, granting the right to run both the migrating and the target deployment for the migration period. An audit that ignores the dual entitlement, or reads the overlap as duplicate consumption, can build a finding that charges for capacity the migration provisions already cover. Because the OpenText EULA places compliance on the licensee, the buyer must be able to show that the overlap was a sanctioned migration, not unlicensed duplication.

What dual entitlement covers during a migration

OpenPass, OpenText's enterprise licensing framework, is built around a single contract with a defined term and dual entitlements for migration. The dual entitlement exists precisely because a real migration cannot be instantaneous. It grants the right to operate the source and the destination together for the migration window, so the buyer is not forced to choose between an unsafe big bang cutover and paying twice for a planned transition. The scope of that grant, how long it runs, which deployments it covers, and what counts as the migration period, is defined in the agreement, and reading it precisely is the foundation of the defense.

The principle to hold to is that overlap during a sanctioned migration is licensed, not a shortfall. The same user working in both the old and new system during cutover is exercising one entitlement across two deployments, not consuming two. The finding must reflect the dual entitlement, and where it does not, the correction is to apply the contract the buyer already holds.

Where a cloud migration finding overstates

The overlap counted as duplication

The central overstatement is treating the simultaneous operation of source and target as two separate consumptions. During the migration window the dual entitlement covers both, and counting them as duplication ignores the grant. Establishing the migration timeline and mapping it to the entitlement period is the answer.

The migration window read too narrowly

A finding may accept that a dual entitlement exists but read its term so tightly that part of a genuine, still running migration falls outside it. The migration period is what the agreement and the project records define, not the shortest reading available, and this is the same interpretive discipline applied across the wider entitlement, examined in our ALA and entitlement review track.

Decommissioned source systems still counted

Once a phase has cut over and the source is retired, it should leave the count. A finding that still counts a decommissioned source repository charges for a system the business no longer runs, the same problem set out in decommissioned Documentum repositories still on the audit.

Defending a cloud migration finding under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. In that window we take over the channel and ensure the migration timeline, the cutover phases, and the dual entitlement terms are documented before any overlap is read as duplication.

Reconstruct. We build the effective license position independently. We map the migration project against the dual entitlement period, establish which deployments are source and which are target at each phase, and identify the decommissioning dates for retired systems. The reconstructed position shows the overlap as a licensed migration, not duplicate consumption.

Rebut. We challenge the finding line by line. Where the overlap has been counted as duplication, we apply the dual entitlement. Where the migration window has been read too narrowly, we establish the genuine period from the project records. Where decommissioned source systems remain in the count, we remove them. Each correction rests on the migration evidence and the agreement terms.

Resolve. We settle on the corrected position and, where it serves you, convert forward into an OpenPass agreement that records the dual entitlement clearly, including the migration window and the decommissioning of source systems, so the next audit cannot rebuild the finding from the transition overlap.

An anonymised outcome

The reason a migration overstatement is expensive is the standard remedy. On noncompliance the licensee is deemed to have acquired licenses at then current list price, owes back maintenance and support, owes first year maintenance on the new licenses, and reimburses the cost OpenText incurs performing the audit, so reading a sanctioned overlap as duplication multiplies through four charges. In our anonymised insurance engagement, case file E-01, a Documentum centred ECM finding fell from $7.2M to $1.6M, a 78 percent reduction. That engagement turned on disqualifying ineligible accounts, and the discipline of holding a count to what the contract actually grants is exactly what corrects a migration overlap read as duplication.

Treat the overlap as the contract intended

The lasting lesson is that a cloud migration is a contractual event the dual entitlement was written to cover, and a finding that ignores it is reading the project as if the transition were never authorised. The overlap is real, the consumption appears in two places, and the audit will count both unless the buyer supplies the migration timeline and the entitlement terms that explain it. That evidence converts an apparent doubling into a single licensed transition, which is what the agreement always intended.

For a buyer, the practical step is to keep the migration project timeline, the cutover phases, the decommissioning dates, and the dual entitlement terms together as a single record, so a migration finding can be answered with the project rather than the snapshot. To prepare that material, read how to reconcile Documentum entitlements before an audit, and to see how migration fits the wider defense, read our ECM and Documentum audit defense track. If a finding has charged for a sanctioned migration overlap, open a case.

Where to go next

For the full method behind a Documentum finding, read our complete OpenText audit defense playbook for 2026. To understand how cloud subscriptions are measured once migration completes, read Core Content cloud subscription audit considerations.