Use caseContent platform exit
Fourteen million Documentum objects have to move, rights and metadata intact. Copying is the easy part; proving nothing was lost is the project.
The docbase is counted before anything movesEvery document gets its own line in the reportA person signs each wave before the next one starts
Some documents need a person · each one is named, with its reason
14.2 million objects in five types, and nothing moved during the scan. 6.2 million sit in the generic type and need a folder rule before they can be mapped.
source · scan of prod_ecm, March 4The Documentum renewal notice sits on the CIO's desk at a US industrial manufacturer, eighteen years after the docbase went live. The last developer who knew the custom types has retired, and nobody wants to be the one who loses a contract version or opens an HR folder to the wrong group. The copy is the easy part. The proof is what everyone fears.
That is why the runbook is built around evidence. The operations engine counts the docbase before touching it, applies a written mapping, and writes one line per document for every batch it moves. The team reads a report and decides, wave by wave.
The runbook has four beats, and they never change order: count first, map in writing, prove on a pilot, then move the rest in waves that each carry their own report. Ten steps play them out on prod_ecm, from Marc's first scan to the closed campaign.
Before a single document moves, the team knows what is in the source, where it will land and who will read it.
Marc Olsen, the repository administrator, connects the operations engine to the docbase and starts a discovery scan. It reads types, folders, versions and rights in place. Nothing moves during the scan.
By the next morning he has the real numbers, and they differ from the 2019 architecture document. The report becomes the work list of the project.
Nadia Haddad, the migration lead, maps every source type to a class of the new repository with Marc. ctr_number becomes Contract number, the repeating attribute ctr_sites becomes a multi-value property, and the generic objects are mapped by folder, one rule per cabinet.
An attribute that is dropped is dropped on purpose, with the reason written next to it.
Documentum grants rights to users and groups of the docbase. Marc maps each group to a directory group of the new repository and each permit level to a role. The inventory has already listed the groups still in use, including some whose members left the company.
One cabinet, every rule, the full report: the pilot is where the mapping meets real data.
Nadia picks the 2019 contracts cabinet: 48,210 objects, all versions, a mix of PDF and Word. It is big enough to hit the edge cases and small enough to rerun in an afternoon. The target is a staging space that business users cannot see yet.
Marc starts the batch at 1:00 p.m. The workers extract each object with its versions, apply the mapping, load into staging and check what arrived. The counts are shown per stage, so a drop between two stages is visible at once.
The 123 exceptions fall into four reasons. Marc fixes the rule where the rule is wrong, hands the missing files to the Documentum team, and reprocesses only the failed objects. The rest of the batch is not touched.
Once the reruns are done, Nadia opens the reconciliation report. Every document has its own line: extraction, transformation, controls, ingestion, with the Documentum identifier and the new one side by side.
Fourteen objects remain, the ones with no content file in Documentum. The source team confirms they were already broken there.
The pilot rules are frozen. The rest of the docbase moves in waves, each with its own report and its own sign-off.
Priya Raman owns the contract records. She picks fifty contracts across the years and opens each one in the viewer, straight from the staging space, with no download. She compares the properties with what she knows of the contract.
Nadia plans six waves over eleven weeks, one business domain at a time, the largest volumes on weekends. Each wave reuses the frozen mapping, produces its report and waits for its sign-off before the next one starts.
Wave 3 hit a storage slowdown on a Saturday. It resumed from the point where it stopped, without restarting the batch and without duplicating anything.
When the last wave is signed, Nadia closes the campaign. The docbase is set to read-only, so nobody keeps filing there by habit, and stays available until the switch-off date the business agreed on.
The runbook, the mappings and the six reports are filed in the new repository as the record of the migration.
Every batch on this runbook closes in one of three states, and the state decides what the team does next.
Counts, versions, properties and rights agree, line by line, with the source.
Then: the migration lead signs and the next wave can start.A bad value, a missing file, an unmapped group. Each one is named with its reason.
Then: the rule or the data is fixed, and only those documents run again.The counts do not agree, or a rule produced the wrong result on many documents.
Then: the next wave waits until the team has found the cause and decided.It signs no wave. It switches nothing off. It does not choose which attribute to drop or which group may read the HR files. Across the ten steps on this page, every binding decision is made by a named person, and filed.
The engine counts, applies the written rules and reports. The control is in the runbook, so it holds when the volumes are fourteen million.
Taken from prod_ecm and its six waves. A docbase with other types and other rules will give other counts.
Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.
Switching off a platform this old takes three signatures: the CIO's, the administrator's and the records owner's. What each one gets in return:
Everyone agrees the platform has to go, and nobody can promise nothing will be lost.
You inherited a docbase you did not build, with a rights model nobody wrote down.
You are asked to sign that your records arrived, without seeing them.
With one cabinet. Take the part of the docbase that worries you most, scan it, map it and run it as a pilot. A cabinet that size gives you an answer within weeks.
The source stays untouched until you decide to freeze it, and the new repository stays invisible to users until a wave is signed.
See it live
Share the list of types and rights groups of your Documentum, FileNet or OpenText platform. We will draft the first mapping with your team and scope a pilot on one cabinet.