Skip to main content

How do I migrate assets to or within Frontify?

An overview of your migration options in Frontify — whether you're moving assets from an external DAM, uploading manually, or duplicating content between accounts.

"Migration" in Frontify covers a few different scenarios, and the right path depends on what you're moving and where it's coming from. This article gives you an overview of all the options so you know where to start.


Which type of migration do you need?

Scenario

Best option

Moving assets from an external DAM or cloud storage (large or complex)

Regular migration via Professional Services

Moving assets from Bynder, Brandfolder, Dropbox, or Google Drive

Automatic migration

Moving a small library with minimal metadata (under 100GB)

Manual upload

Duplicating Guidelines, Projects, or Libraries between Frontify accounts

Content duplication request


Option 1: Regular migration (Professional Services)

This is the most common path for large or complex asset migrations. Frontify's Professional Services team handles the import, but there's preparation work on your end first.

What you do:

  1. Export your assets from your current DAM, or ask your DAM provider to do it for you.

  2. Upload the assets to an Amazon S3 bucket — your CSM provides the credentials.

  3. Fill in the Frontify metadata sheet template with the required fields (ID, filename, location, title) and any optional fields such as tags, copyright, and custom metadata.

  4. Share the completed sheet with your CSM.

What Frontify does: verifies the assets against your metadata sheet and runs the migration import.

How long does it take? Roughly 2 to 3 weeks if everything goes smoothly, or 1 to 2 months for more complex migrations. The import run itself takes approximately one day per 150GB.

Important: do not make any domain changes or redirects during the migration run, as this will cause it to fail.

Who to contact: your Customer Success Manager (CSM) to kick off the process, agree on scope, and discuss costs.


Option 2: Automatic migration

Available if your assets are currently in Bynder, Brandfolder, Dropbox, or Google Drive. This replicates your existing folder and metadata structure with minimal customisation and is significantly cheaper than a regular migration.

Steps:

  1. Grant Frontify access to your current platform.

  2. Discuss the project scope with your Frontify contact.

  3. Frontify runs the migration — your assets and metadata appear in Frontify.

Who to contact: your CSM or Frontify contact to get started.

For full details, see Frontify Automatic Migrations.


Option 3: Manual upload

If you have a smaller library (under 100GB) with little or no metadata, you can migrate assets yourself by uploading them directly via the browser into Frontify and applying metadata using Bulk Actions. No Professional Services involvement is needed and there is no cost.

For instructions, see Uploading Assets to Frontify.


Option 4: Content duplication between Frontify accounts

If you need to copy Guidelines, Projects, or Libraries from one Frontify account to another, this is handled through a duplication request rather than a migration. The original content stays intact — only a copy is created in the destination account.

To request a duplication:

  1. Include the URLs of all content to be duplicated and the destination brand URL.

  2. Provide a time window when the duplication can happen — you should not be actively working on the content during this window.

Who handles it: the Frontify Support team runs the duplication.

Note: some content types cannot be duplicated, including Publisher Template Libraries, Personal Projects, Essentials fonts and colors, automations, and share links. A few things also need to be manually reconnected after duplication, including library frontends in guidelines and public links.


Not sure which option applies to you?

Reach out to your Customer Success Manager — they'll point you in the right direction. If you don't know who your CSM is, contact Frontify Support and we'll help.

Did this answer your question?