← Compare FileSpin

Migration guide

Move media from Canto to FileSpin

Build a reconciled asset library and a working delivery route. Start with a seasonal campaign: find the approved image, prepare a storefront card and banner, share the launch collection, and replace a product image at its destination.

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

Canto OAuth access, a complete Search / Filter inventory and authorised original downloads provide the starting point. Keep content IDs, tags, custom fields and album membership together in the export manifest. Search results already carry the metadata. Search allows 200 calls a minute and content details 500; requests over 1,000 records return HTTP 400. API tokens last one month. Follow pagination and back off on HTTP 429. Retrieve originals rather than MDC master-image renditions; inventory historical versions separately.

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 Canto albums and asset membership to FileSpin collections. Map custom fields to the selected schemas, and record portal audiences and approval states for destination configuration.

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

Canto portal and MDC references are replaced with FileSpin URLs; recipient access and image transformations are rebuilt and tested on the real storefront.

History

Past requests, downloads, review histories and usage records archived from Canto

An illustrative Canto record (content ID, custom fields, keywords, album, original file and approval state) 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 Canto 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.

Canto migration questions

Do our Canto links keep working?
No. Canto portal, direct and MDC links are served by your Canto 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 Canto during the migration?
Yes. Canto’s webhooks, with last-modified filters, 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. Tags, keywords, custom field values, approval status and album membership come from Canto’s search results and are mapped to your FileSpin schemas and collections; albums become 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 API keys with download permission.

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 Canto assets: source IDs beside FileSpin asset IDs, file, metadata and collection checks, and one exception where a rendition was downloaded instead of the original and then replaced
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 Canto 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.