Browse before moving
Navigate source and destination repositories, inspect folders and documents, and scope the content set before starting a transfer.
Enterprise content transfer desktop app
Move files, folders, metadata, and permissions between content systems with a deliberate workflow built for migrations, cleanups, and controlled bulk transfers.
The app is designed around connector-based browsing, explicit source and destination selection, and transfer sessions that teams can test before they write. Current connectors include OpenText Content Server, SharePoint, and Windows Filesystem, with ServiceNow and additional filesystems on the roadmap.
Navigate source and destination repositories, inspect folders and documents, and scope the content set before starting a transfer.
Mirror folder trees, preserve file dates where supported, and handle duplicate documents by skipping, overwriting, or adding a new version.
Carry OpenText category payloads into uploads and prepare path-based or filename-based metadata rules for repeatable imports.
Apply configured Content Server permissions after import, including user and group selections and common access templates.
Simulate transfers without writes, review expected outcomes, then retry failed items without restarting the entire job.
Track progress, throughput, skipped items, failures, and final results through live logs and exportable transfer reports.
Content Management Bridge keeps migration work understandable: connect, preview, transfer, and audit.
Add repository connections and authenticate with the credentials required by each system.
Choose source and destination nodes through the built-in browser instead of hand-editing paths.
Run controlled uploads or downloads with concurrency limits, duplicate handling, and cancellation.
Review counts, failures, skipped files, elapsed time, and logs for migration evidence.
For SharePoint access, Content Management Bridge uses Microsoft Entra ID so organizations can keep sign-in, consent, and access policy under their tenant controls. The app requests only the permissions needed for configured content operations, and transfer actions are initiated by the signed-in user.
Connection settings and transfer activity are handled in the desktop app. Secrets and tokens should be stored using operating-system credential storage where supported.
The app is intended to access repositories selected by the user or administrator, then move content only when a transfer is explicitly started.
The Privacy Policy and Terms of Service are available for Azure app registration review and customer consent workflows.
Use Content Management Bridge when content work needs visibility, repeatability, and a clear audit trail.