Bridge DocStream — the Dutch/Belgian engineering DMS rich in technical metadata — and Microsoft SharePoint, where stakeholders, clients and subcontractors expect to access documents. Use DMS Sync Manager as an ongoing bridge OR as a one-shot migration when you're moving off DocStream entirely.
Three steps to keep DocStream and Microsoft SharePoint in sync.
DocStream connects via a tenant-issued API key. Microsoft SharePoint uses OAuth 2.0 against Microsoft Entra ID, app-only or delegated. Both connections are project-scoped and stored encrypted.
Pick a DocStream folder/project as the source and a SharePoint document library as the destination. DocStream custom metadata columns map to SharePoint columns so the destination library is searchable by the same fields.
Run continuously (hourly / daily) for ongoing bridge use, or trigger a single backfill run for a one-time migration. File type, status, and last-modified filters apply in both modes.
A few real-world scenarios.
"Projects rarely fail in design — they fail when teams can't trust they're looking at the latest version."
Yes. Each DocStream revision becomes a new SharePoint version, preserving SharePoint's native versioning. The DocStream revision identifier is also written into a configurable SharePoint column.
Yes. Sync rules can map any DocStream metadata column to a SharePoint column. The mapping is configured per sync task.
By default, deletions are not propagated — destination keeps the historical record. An optional rule can sync deletions if you want strict mirroring.
Yes. Set the sync task to "one-shot" mode and run once. It backfills the entire DocStream folder set into SharePoint with metadata mapping intact, then archives itself.
DMS Sync uses SharePoint's chunked upload sessions for large files and exponential back-off for the DocStream API. A multi-year DocStream archive typically completes a backfill in hours, not days.
Book a demo and we'll walk you through setting it up for your project.