Multi-source DAM migration: mapping conventions and reconciliation · 3 min 45 · Video in French, reconstructed data.
Project visuals
Interface screenshots, reconstructed deliverable extracts and workflow illustrations are labelled. All visuals use fictional content and metadata, with client branding removed. Select an image to view it full size.
The engagement
Vetoquinol's marketing assets were scattered across a vendor SFTP, country SharePoint sites, Box, a third-party DAM for Asia-Pacific, a WordPress site and ad-hoc transfers. Everything had to be consolidated into a single Bynder, subsidiary by subsidiary, with a shared taxonomy, collections, and a rights model spanning country, business unit, brand and external agency.
We handled the migration in batches, formalizing two mapping conventions between the source folder trees and the target taxonomy, since the sources shared neither depth nor filing logic. Each batch was reconciled field by field after import, and missing files were traced back to their root cause rather than merely counted.
The group DAM is now populated and indexed. Every batch has its reconciliation report and itemized discrepancy list, which allowed gaps to be fixed at source, down to a folder missing from a delivered archive, instead of surfacing in production.
Takeaway
A takeaway for your project
We reconciled each subsidiary’s migration to identify discrepancies and resolve them at their source.
Technologies
- Bynder
- SharePoint
- Box
- WordPress
- SFTP
Your next step
Do your subsidiaries use separate media libraries?
Describe the sources to consolidate, countries involved and target classification model. We help prepare the mappings and acceptance checks for each batch.
Discuss your project