← Compare FileSpin

Migration guide

Move media from ImageEngine to FileSpin

Move to FileSpin with every original reconciled and a working delivery route. Start with a catalogue refresh: find the right original, review the change, prepare card and banner outputs, and verify delivery across the pages that use them.

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

ImageEngine reads your originals from your own origin, so the migration copies them straight from there: the web server, S3 bucket or Google Cloud Storage behind each delivery address. Business metadata comes from the CMS, PIM or database that holds it. The manifest records each delivery address, origin, object path, directives and origin access rule, and retained revisions come from your origin’s version history.

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

Origin paths and product identifiers map to FileSpin assets and business fields. Your image outputs become FileSpin processing settings, with a source-path-to-FileSpin-ID manifest.

Collections

Collections built from origin folder paths or your business data

Versions

The revisions you keep, retrieved alongside the current files

Access

Roles, private delivery and review workflows set up in FileSpin

Delivery

Each ImageEngine directive is rebuilt as the matching FileSpin output in your image builders and responsive markup. Device sizes, crops, formats, quality and cache refresh are checked against current output before cutover. On ImageEngine Kube (self-hosted), the delivery hostname is yours and points at your Kube deployment, so your team switches it at cutover.

History

Delivery analytics stay in ImageEngine; FileSpin records delivery and share analytics from cutover

An illustrative ImageEngine record (origin path, product ID, season, an output directive, a delivery URL, and device detection settings 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 ImageEngine 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.

ImageEngine migration questions

Do our ImageEngine URLs keep working?
No. ImageEngine URLs carry ImageEngine directives, so the migration switches each image reference to a FileSpin URL using the manifest, with each directive rebuilt as the matching FileSpin output. Your originals stay at your own origin, and FileSpin copies them from there.
Can we keep working in ImageEngine during the migration?
Yes. ImageEngine keeps delivering from your origin throughout, and your team keeps publishing as usual. FileSpin copies from the same origin, and the final sync picks up anything added or changed before each route switches.
Do metadata and folders come across?
Yes. ImageEngine keeps no separate metadata or folders, so there is little to move from it. Your origin’s folder paths and the product data in your CMS, PIM or database map to FileSpin fields and collections, so your team can search and organise by business fields.
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 read access to your origin storage or server, and an export of your business data from the system that holds it.

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 ImageEngine origin files: source IDs beside FileSpin asset IDs, file, metadata and collection checks, and one exception where an output size was rebuilt to match the product page
Reconciliation report with synthetic source records: one row per source origin file, its FileSpin ID and checks, and the exception resolved before sign‑off.

Plan your ImageEngine 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.