- Matching file counts alone do not establish a successful migration.
- Preserve context through approved mappings and traceable identifiers.
- Treat access, change capture and business acceptance as validation workstreams.
1. Define exactly what must be preserved
Build the validation scope before extraction begins. A successful transfer job can still omit historical versions, required metadata or relationships, or grant the wrong access. The acceptance model should describe what the business needs in the target and how that will be demonstrated.
- Native files and required renditions.
- Metadata, classification, versions and version labels.
- Folder placement, document relationships and linked processes.
- Owners, identities, groups and effective permissions.
- Retention information, legal holds and required historical audit evidence.
Whether an element can become a native target feature depends on the source, target and chosen approach. Unsupported features need an agreed retained representation or another approved treatment.
2. Agree mappings and keep item-level traceability
Define how Documentum types, fields, identities and access rules map to the target. Record transformations, default values, excluded fields and features without a direct equivalent. Assign a traceable identifier linking each source item and version to its target result.
If historical audit events cannot be imported as native events, agree an evidence format, access method and retention treatment. Do not silently drop information because the target has no matching field. Include authoritative identifiers and relationship mappings in reconciliation records.
3. Build a reconciliation model that explains the totals
Account separately for successful items, failed transfers, approved exclusions and unresolved exceptions. Check the item list as well as aggregate totals: equal counts can conceal a duplicated file and a missing one.
| Validation area | What to check | Evidence / acceptance approach |
|---|---|---|
| Files and renditions | Correct items, formats, size and integrity | Item-level results; agreed checksums for unchanged binaries; conversion-specific checks when transformed |
| Metadata and classification | Required values, type mapping and transformation rules | Field-level reconciliation, required-field checks and approved mappings |
| Versions and relationships | Agreed history, labels, links and source-to-target associations | Version/relationship reconciliation and representative navigation tests |
| Identity and permissions | Intended effective access, inheritance and restricted content | Allow/deny tests with representative business accounts |
| Retention and audit evidence | Required context survives in an approved target or retained form | Governance-owner review and retrievable evidence |
| Changes during migration | New, updated, deleted and permission-changed items are handled | Delta logs, cutoff records and final reconciliation |
| Business use | Users can find, open and use the right content | Approved user-acceptance scenarios and sign-off |
4. Test effective access with business users
Permission names and inheritance rules may behave differently across platforms. Test users who should be allowed to read or change content and users who should be denied access. Include sensitive content, external users and relevant inherited permissions.
Check effective behavior rather than assuming an ACL label means the same thing in both systems. Administrative access is useful for diagnostics but cannot substitute for business-role testing. Record unintended access and blocked legitimate work as exceptions.
5. Rehearse changes made during migration
When users continue working during an initial load, define how additions, updates, deletions, new versions and permission changes will be captured. Rehearse the final synchronization and agree which activity must stop during cutover.
Record the cutoff, the system of record at each stage and how the final source state is compared with the target. A change event in a log does not by itself prove that every downstream application has applied that change.
6. Give every exception an owner and a decision
Keep damaged files, missing identities, invalid metadata, unsupported relationships and failed transfers in a visible exception register. Each item needs its impact, owner, treatment, retest result or approved acceptance decision.
Do not hide unresolved items in technical logs or classify them as successful transfers. The business should understand what is excluded, what remains outstanding and what risk it is accepting. Use exhaustive reconciliation for the agreed inventory and risk-based behavioral tests where full manual inspection is impractical.
7. Complete business acceptance before decommissioning
Ask business owners to test representative tasks: finding the correct document, opening the required version and completing the relevant process. Governance teams should be able to retrieve the evidence they need.
Keep the source under the agreed access and retention arrangements until validation, business acceptance and applicable retention obligations are addressed. Decommissioning is a separate approved decision, not an automatic consequence of a successful import. For the broader delivery sequence, see TechTiera’s enterprise content migration guide.
Turn the validation checklist into a migration acceptance plan
Assign an owner and an acceptance rule to every validation area before the pilot. Record what must pass, how exceptions are approved and which evidence must be available at cutover. Separate repository migration from a client change such as Webtop to D2; a new interface does not by itself prove that content has moved or needs to move.
TechTiera’s Documentum migration services cover assessment, mappings, migration execution and acceptance planning. Review DocOrbit’s export and import approach, then use the agreed source and target scope to select the validation checks.
What should the final migration validation pack contain?
- Approved scope, source inventory and target mapping rules.
- Source-to-target identifiers and reconciliation reports.
- File, rendition, metadata, version and relationship results.
- Effective-permission and business-process test evidence.
- Exception decisions, fixes and retest records.
- Delta, cutoff and cutover records.
- Business acceptance and the approved source-retention/decommissioning decision.
For an implementation or upgrade that includes data movement, make these outputs a named workstream in the implementation plan or upgrade checklist.
Working checklist
Use this checklist to record your review. Selections stay in this browser view and are not submitted.
0 of 6 checked
Frequently asked questions
Are matching document counts enough to validate a migration?
No. Equal totals do not show that the correct items, versions and relationships arrived. Use item-level reconciliation together with file-integrity checks, metadata validation, effective-access tests and business acceptance.
Can we use checksums after converting documents?
Checksums are useful for unchanged binary files. Intentional conversion normally changes the bytes, so use agreed conversion-specific checks, content/readability tests and acceptance criteria instead of expecting identical hashes.
How should audit history be handled when the target cannot import it?
Agree an approved retained evidence format, link it to the relevant source/target items, and define access and retention. Do not describe the history as natively migrated unless the target actually supports and validates that import.
Should every migrated item be manually inspected?
Account for every in-scope item through reconciliation and agreed automated checks. Use risk-based samples for business behavior and visual inspection where appropriate, including difficult formats, sensitive permissions and known exceptions.
When can the original Documentum repository be retired?
After reconciliation, exception decisions, business acceptance, final change handling and applicable retention/legal-hold requirements have been addressed, with approval from the relevant owners. A successful transfer job alone is not sufficient.



