← Compare FileSpin

Migration guide

Move media from Acquia DAM to FileSpin

Build a reconciled asset library and a working delivery route. Start with a multi-channel product release: find an asset using business metadata, collect approval, create web outputs and check both the PIM reference and storefront result.

There are two ways to run the move. Both start with an inventory and a representative sample before the full transfer.

Assisted migration
We provide the necessary tools to migrate assets from on-premise and cloud storage while your technical team runs the migration, including metadata mapping, import and validation.
Managed migration by FileSpin
The FileSpin team carries out the migration: source extraction or export coordination, field mapping, import, validation and cutover support. Your team grants source access and signs off the result.
Four migration stages, retrieve, map and import, validate and cut over, showing who carries out each one in an assisted migration and in a managed migration by FileSpin
Who carries out each stage in an assisted and a managed migration.

1. Retrieve the source files and records

Generate an authorised Acquia DAM API user token and use the recommended V2 API to search and retrieve assets. The source offers paginated/search-scroll inventory and asset download links, alongside CSV metadata exports. Download access depends on original-format and asset-status permissions, including released, expired and unreleased assets. Export metadata types and controlled values with the asset records; embedded file metadata alone is not the complete DAM record. The API allows 50 requests a second and returns HTTP 429 beyond that. For more than 10,000 assets, use the search-scroll endpoint (up to 100 per page).

Retrieval uses an authorised source account, with credentials kept out of exports, screenshots and public URLs. Each completed inventory page and download is saved, so interrupted work resumes where it stopped, and expired download links are refreshed.

2. Create a manifest you can reconcile

One record per source file or retained version: source system, asset ID, file or version ID, original name, source path, file type, bytes, a checksum recorded at download, tags, custom metadata, collection membership, rights information and source update time. The FileSpin asset ID and transfer status are added as work progresses.

Original files are kept separate from thumbnails and delivery renditions. Every exception, such as a missing original, a restricted download or an unsupported format, is listed with its resolution.

3. Map what moves and what gets rebuilt


Part of the library

What happens

Originals

Authorised source files downloaded and reconciled against the manifest

Metadata

Map metadata types, categories and collections into FileSpin schemas and collections. Keep product Entries and syndication relationships separate from the media record and retain source IDs for joins.

Collections

Membership rebuilt from source IDs after import

Versions

The revisions you keep, retrieved alongside the current files

Access

Roles, private delivery and review workflows set up in FileSpin; past review decisions archived

Delivery

Embed links, portals, Drupal integrations, Entries and Syndicate flows are inventoried; delivery references switch to FileSpin as each consumer is ready.

History

Past requests, downloads, review histories and usage records archived from Acquia DAM

An illustrative Acquia DAM record (asset ID, metadata, category, collection, version, and product Entries and syndication links not moved here) mapped to a FileSpin record in the E-Commerce schema with SKU 31077 and season SS27, and the collection recreated with the destination asset IDs
A Acquia DAM record (synthetic example) mapped to the imported FileSpin asset.

4. Import and check a sample

The sample includes several file types, a multi-value metadata field, an asset in more than one collection, a retained revision and restricted content. Files are loaded, FileSpin IDs recorded, mapped metadata applied and relationships rebuilt.

In an assisted migration, your team stages the retrieved files with the tools we provide and loads metadata through the mapping. In a managed migration, the FileSpin team carries out these steps.

The sample passes when:

  • The correct file and intended version opens in FileSpin.
  • Required fields, types and controlled values match the mapping.
  • Collection membership counts match and related assets resolve.
  • Version records and current files match the scope.
  • An authorised user gets access and an unauthorised user is refused.
  • A content owner finds the selected assets by business fields and completes a review.
  • Real pages, players and feeds return the intended output, including after a replacement.
  • A test campaign link and a share download appear in Delivery Insights and Share analytics.
  • If agent work is included, its first run touches only the selected assets, stays within budget and reports its outcome.
  • Every exception is listed and resolved before the full run.
FileSpin Overview showing users, assets, collections, shares and total storage used
FileSpin Overview: compare asset and collection counts with the source inventory.
FileSpin AI Usage account ledger listing credit grants and debits with amount, running balance and operation source
AI Usage ledger: credits used by each agent run, for the budget check.

Acquia DAM migration questions

Do our Acquia DAM links keep working?
No. Acquia DAM embed and portal links are served by your Acquia DAM account, so the migration replaces each reference with a FileSpin URL using the ID manifest. Your pages then get the sizes and formats they need straight from the FileSpin link.
Can we keep working in Acquia DAM during the migration?
Yes. Acquia DAM’s update notifications, which cover metadata and version changes, picks up new, changed and deleted assets, and the final sync brings them across before any route switches.
Do metadata and collections come across?
Yes. Metadata values, controlled vocabularies, categories and asset groups are exported through the API and CSV exports and mapped to your FileSpin schemas and collections, without duplicating files. The mapping is checked on a sample before the full transfer.
Do we need to run the migration ourselves?
No. In a managed migration, the FileSpin team carries out the transfer. In an assisted migration, we provide the tools and your technical team runs it. Either way, you provide an API token that can download released, expired and unreleased originals.

5. Cut over

1. Set the switch-over
Agree when FileSpin becomes the system of record and how new uploads and replacements are handled.
2. Final sync
Pick up the last changes through the source’s change mechanism or a refreshed inventory, import them and reconcile counts.
3. Switch one route first
Move a selected collection or application route to FileSpin, then test public output and protected access.
4. Expand and retire
Keep the source available through the recovery window, with a rollback for each route, then expand and retire it.

6. Sign off the result

  • Every in-scope source file has a destination ID or an accepted exception.
  • Required metadata, relationships, versions and access controls pass the agreed checks.
  • Applications use the intended delivery route and updates appear correctly.
  • The exception report, ownership map and recovery procedure are handed over.
Reconciliation report for four synthetic Acquia DAM assets: source IDs beside FileSpin asset IDs, file, metadata and collection checks, and one exception where a category held the season and was mapped to the season field
Reconciliation report with synthetic source records: one row per source asset, its FileSpin ID and checks, and the exception resolved before sign‑off.

Plan your Acquia DAM migration with FileSpin. Tell us the size of your library, the history you need and the systems it feeds, and we’ll scope an assisted or managed migration with you.