Skip to main content

Brandfolder Automated Migration to Frontify

Learn how Frontify’s automated Brandfolder migration works, what is included, what is excluded, and what your team needs to prepare before migration begins.

Note: This guide covers the automated asset migration from Brandfolder supported by the Frontify Professional Services team only. It does not apply to migrations performed by third-party agencies, partners, or clients completing self-migration.


Overview

Frontify’s Brandfolder automated migration is a structured way to move eligible Brandfolder assets and metadata into Frontify with minimal manual setup.

This migration is designed for teams moving from Brandfolder to Frontify who want to preserve asset structure and metadata through a faster, easier, and more cost-effective migration process. To get started, your team provides secure access to your Brandfolder account, confirms the specific Brandfolder to migrate, and avoids making changes to assets or metadata once migration begins.

The migration is completed programmatically through API-based tools. Typical project duration is 1–4 weeks, depending on total asset volume, asset size, metadata complexity, and customer readiness.

Important: This is a service-free automated migration. It does not include consultation, migration strategy, data analysis, metadata cleanup, or working sessions with Frontify. All communication takes place asynchronously by email, and no meetings are included as part of this migration process.


Is this migration option right for you?

The Brandfolder automated migration is a good fit if:

  • You are moving assets from Brandfolder to Frontify.

  • Your assets are located within Brandfolder’s DAM.

  • You want to migrate asset files and supported metadata.

  • You want Brandfolder Sections mapped to Frontify folders.

  • You can provide the required Brandfolder admin access.

  • You can confirm the specific Brandfolder that should be migrated.

  • You can avoid making changes to assets or metadata during the migration.

This migration is designed to be streamlined and structured. However, not every asset type, metadata field, or Brandfolder data point can be migrated automatically.


What is included

The automated migration can include:

  • Asset files

  • Title

  • Author

  • Description

  • Tags

  • All custom metadata

  • Attachments

  • Brandfolder Sections mapped to Frontify folders

The included data is based on what is available through Brandfolder’s API and within the agreed migration scope.


What is not included

The automated migration does not include every data point from Brandfolder.

The following are excluded:

  • Files over 500 GB

  • Version history
    Only the latest version of each asset is migrated.

  • Asset relations

  • Archived assets

  • Asset expiry date information

  • Custom previews

  • Brandfolder Labels

  • Copyright information

  • Watermark information

  • Multi-language features

  • Assets outside Brandfolder’s DAM

  • Data unavailable through Brandfolder’s API

  • Metadata not listed in the inclusions

  • Errors caused by missing or incorrect data

  • Limitations caused by Brandfolder’s API

  • Data analysis or manual metadata enrichment

These exclusions help keep the migration automated, predictable, and efficient.


Before the migration begins

Before Frontify can begin the automated migration, your team will need to complete the preparation steps below.

1. Provide secure Brandfolder admin access

Frontify needs Brandfolder admin credentials to set up the migration.

This includes:

  • UI access with username and password

  • Permissions required to enable API access

Access details should be shared through an approved secure channel.

2. Confirm the specific Brandfolder to migrate

Your team needs to confirm which Brandfolder should be migrated.

This is especially important if your organization manages more than one Brandfolder or if only a specific Brandfolder is included in the migration scope.

3. Confirm that the assets are ready for migration

Once the migration begins, avoid making changes to the assets or metadata included in the migration scope.

Changes made in Brandfolder during the migration may not be reflected in Frontify and can affect the consistency of the migrated data.


Migration process

The Brandfolder automated migration follows three main stages.

Stage 1: Preparation

During preparation, your team works with Frontify by email to confirm access and migration scope. This stage includes:

  • Providing Brandfolder admin credentials

  • Ensuring permissions are available to enable API access

  • Confirming the specific Brandfolder to be migrated

  • Confirming that assets and metadata are ready for migration

The timing for this stage depends on customer readiness.

Stage 2: Execution

Once preparation is complete, Frontify sets up and runs the migration. This stage includes:

  • Allocating engineering resources

  • Preparing the migration setup

  • Scheduling the migration

  • Programmatically transferring assets through API-based tools

Technical setup typically takes around 3 business days. After setup, import speed is typically around 10,000–30,000 assets per day, depending on asset size and metadata complexity. The exact timeline depends on total asset volume and migration scope.

Stage 3: Review and completion

After the migration is complete, Frontify performs a post-migration review and shares a migration report. This stage includes:

  • Validating migrated assets

  • Generating and sharing a migration report

  • Customer review of migrated assets and metadata

  • Customer confirmation of completion by email

The post-migration review typically takes around 1 business day. One validation cycle is included.


Customer review period

After handover, you have a 1-month error reporting window to report migration-related issues.

During this period, review a representative set of migrated assets and metadata to confirm that the migration has been completed as expected.

We recommend checking:

  • Asset files

  • Asset titles

  • Authors

  • Descriptions

  • Tags

  • Custom metadata

  • Attachments

  • Frontify folder placement based on Brandfolder Sections

  • Any agreed scope or exclusions


Customer responsibilities

To keep the migration running smoothly, your team is responsible for:

  • Providing the required Brandfolder admin credentials

  • Ensuring the account has permissions required to enable API access

  • Confirming the specific Brandfolder to migrate

  • Ensuring the assets and metadata in scope are ready before migration begins

  • Avoiding changes in Brandfolder once migration begins

  • Reviewing the migrated assets and metadata after handover

  • Reporting any migration-related issues within the review window


Important limitations

The automated migration depends on the data and files available through Brandfolder’s API.

This means some data may not be available for migration if it is restricted by permissions, unavailable through the API, outside Brandfolder’s DAM, missing from the supported inclusions, or affected by API-related limitations or errors from Brandfolder.

Frontify cannot migrate data that is not available through the API connection used for the migration. If this affects a small, manageable number of assets, we recommend uploading those assets manually to your Frontify library through the UI.


Disclaimer

This article is intended as general guidance for the Brandfolder automated migration process. Brandfolder is a third-party platform and may change its API behavior, permissions, available metadata, file access, or system functionality at any time.

Frontify does not control Brandfolder’s API, system availability, permissions model, data structure, or how Brandfolder exposes assets and metadata to authorized users. Your team is responsible for ensuring that the correct Brandfolder is confirmed and that the required assets and metadata are available through the access provided for migration.

The final migration scope, timing, pricing, and responsibilities are confirmed in the signed Scope of Work (SOW).


Download our a sample process timeline below:

Did this answer your question?