Selection and implementation
Migrating to a new DAM: assets, metadata and cutover planning
Quick answer
A DAM migration is a data project with four workstreams: triage what to move, map metadata field by field, rehearse with trial loads, and cut over with a short freeze and delta load. Migrating 100,000 to 500,000 assets typically takes 8 to 16 weeks. Under the EU Data Act, SaaS vendors must support switching within defined notice and transition periods.
Key takeaways
- Triage before you move: in practitioner experience, 20% to 40% of legacy assets are duplicates, superseded versions or obsolete.
- Metadata mapping, especially rights and expiry fields, carries more risk than moving the binary files.
- Run at least one trial migration on a 5% to 10% sample and one full rehearsal before cutover.
- Redirect or rewrite embedded asset URLs on websites and marketplaces, or images will break on go-live day.
- The EU Data Act limits switching notice to two months and abolishes switching charges from 12 January 2027.
A DAM migration succeeds when it is planned as a data project with four workstreams: triage, metadata mapping, rehearsal and cutover. Moving 100,000 to 500,000 assets typically takes 8 to 16 weeks (editorial estimate), and the binary files are the easy part. The risk sits in metadata, rights information and the asset URLs embedded in websites and marketplaces.
Triage: decide which assets to migrate
Triage reduces volume, cost and search noise before a single file moves. Classify every asset into one of four groups: migrate (approved and current), archive (superseded and worth retaining), delete (true duplicates and abandoned work) and review (unclear rights or ownership). In practitioner experience, 20% to 40% of a legacy library falls into archive or delete.
Use checksums to find exact duplicates and visual similarity tools for near-duplicates such as resized exports. The so what: a smaller, cleaner library improves the first impression of the new DAM, which directly supports adoption in the weeks after go-live.
Metadata mapping: the highest-risk workstream
Metadata mapping decides whether users can find assets on day one and whether rights restrictions survive the move. Map every source field to a target field with an explicit conversion rule, aligned with the target metadata model and taxonomy.
| Data element | Migration approach | Typical risk |
|---|---|---|
| Binary files and renditions | Bulk transfer by API or object storage; regenerate renditions | Long transfer windows for video |
| Embedded metadata (IPTC, XMP) | Read on ingest | Conflicts with database values |
| Database metadata | Export to CSV or JSON, map, normalise vocabularies | Free-text values and spelling variants |
| Rights and expiry data | Map to structured date and licence fields | Lost expiry dates create legal exposure |
| Versions and relations | Migrate approved versions; archive history | Volume doubles if all versions move |
| Collections, users, permissions | Rebuild in target | Over-broad access after go-live |
| Public asset URLs | Map old to new and redirect | Broken images on web and marketplaces |
Decide which source wins when embedded IPTC or XMP data conflicts with database values; the database is usually more current. Treat rights fields as a separate quality gate and review them with legal, using the principles in rights and licence management in DAM.
Cutover planning for a DAM migration
Cutover is a rehearsed sequence; the go-live weekend should hold no surprises. A typical plan follows six steps.
- T minus 8 weeks: trial migration of a 5% to 10% sample covering every asset type and business unit.
- T minus 4 weeks: full rehearsal load into a staging environment, with timed transfer runs.
- T minus 2 weeks: initial full load into production.
- T minus 1 week: content freeze in the legacy system; urgent uploads go to a logged holding area.
- Cutover weekend: delta load, URL redirects or CDN rewrites, integration switch, smoke tests.
- Hypercare: four weeks of daily issue triage; legacy system read-only for three to six months.
Public URLs need particular care. If product images on your webshop point to the old DAM or image CDN, plan redirects or rewrite the references in your CMS and PIM; see dynamic media and image CDNs for delivery options.
Your exit rights under the EU Data Act
The EU Data Act, Regulation (EU) 2023/2854, applying from 12 September 2025, strengthens your position when leaving a SaaS DAM. Providers of data processing services must allow switching on a maximum notice period of two months, complete the switch within a transitional period of 30 calendar days in principle, and keep data retrievable for at least 30 days afterwards. Until 12 January 2027 they may charge only reduced switching charges capped at their direct costs; from that date, switching charges are abolished.
The so what: request a full export of files, metadata, versions and audit logs in an open format early in the project. The switching rules cover data processing services such as SaaS. When you leave an on-premises installation such as Extensis Portfolio or Northplains Xinet, your licence contract governs the exit, so arrange export scripts and server access in advance. Data location also matters for the target; check EU data residency requirements before the first load.
What to do next
- Run a triage on a sample of 1,000 assets to estimate the migrate, archive and delete split.
- Build a field-level mapping sheet with a conversion rule and an owner for every field.
- Request a full test export from your current vendor, citing your Data Act switching rights where relevant.
- Schedule the trial migration, full rehearsal and cutover dates in the implementation roadmap.
- Inventory every public asset URL in use and agree the redirect approach with your web team.
Frequently asked questions
How long does a DAM migration take?
For 100,000 to 500,000 assets with moderate metadata quality, a migration typically takes 8 to 16 weeks including triage, mapping, trial loads and cutover, in practitioner experience. Very large video libraries or poor legacy metadata can extend this. The cutover itself usually takes a weekend plus a one-week content freeze.
Should you migrate all assets to a new DAM?
Migrate approved, current and legally usable assets in full, archive superseded versions in low-cost storage, and delete true duplicates. Moving everything inflates storage cost and pollutes search results from day one. Keep a read-only copy of the legacy system for three to six months as a safety net.
Can a SaaS DAM vendor charge you for exporting your data?
Under the EU Data Act, Regulation (EU) 2023/2854, providers of data processing services may charge only reduced switching charges capped at their direct costs until 12 January 2027, and no switching charges from that date. Ordinary contractual service fees may still apply, so check your contract terms.