Note: This guide covers the automated asset migration from Bynder 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 offers an automated migration option for customers moving assets from Bynder to Frontify. This migration is designed to transfer assets and structured metadata with minimal manual preparation, using secure access to your Bynder environment and a defined migration scope.
This option is best suited for teams that want to move from Bynder to Frontify while preserving asset integrity and selected metadata, without needing a manual metadata sheet setup or heavy IT involvement.
Typical project duration is 1–4 weeks, depending on asset volume, asset size, metadata complexity, and customer readiness.
Is this migration option right for you?
The Bynder automated migration is a good fit if:
You are moving assets from Bynder to Frontify.
Your assets are stored in the Assets section of Bynder.
You want to migrate asset files and structured metadata.
You can provide the required Bynder admin access.
You can define which assets and metadata should be migrated.
You can avoid making changes in Bynder once the migration has started.
This migration is designed to be streamlined and structured. However, not every asset type, metadata field, or Bynder data point can be migrated automatically.
What is included
The automated migration can include:
Asset files
Title
Description
Creator
Tags
All custom metadata, or a pre-agreed subset of custom metadata
The exact metadata scope should be confirmed before the migration begins.
What is not included
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.
The automated migration does not include every data point from Bynder. The following are excluded:
Files over 500 GB
Version history (only the latest version of each asset is migrated.)
Attachments
Asset relations
Collections
Archived assets
Expiry dates
Copyright data
Watermark data
Bynder multi-language features
Workflow section content. Only assets from the Assets section are included.
Any data unavailable through the Bynder API to the OAuth user
API-related limitations or errors from Bynder
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 Bynder admin access
1. Provide secure Bynder admin access
Frontify needs the required Bynder admin access to set up the migration.
The admin access must allow the creation of OAuth apps in Bynder. This is required so the migration can connect to Bynder and transfer assets programmatically.
Access details should be shared through an approved secure channel.
2. Define the migration scope
2. Define the migration scope
You will need to confirm which assets should be migrated.
There are two common options:
Migration scope | Description |
All assets | All eligible assets in scope are migrated. |
Assets marked through a custom metaproperty | Only assets tagged or marked with a specific Bynder custom metaproperty are migrated. |
If you only want to migrate a subset of assets, your team must mark those assets in Bynder before the migration setup is completed.
3. Confirm the metadata scope
3. Confirm the metadata scope
You will also need to confirm which metadata should be transferred.
There are two common options:
Metadata scope | Description |
All custom metaproperties | All eligible custom metadata available to the OAuth user is migrated. |
Pre-agreed subset | Only selected custom metadata fields are migrated. |
Confirming this before the migration begins helps avoid unnecessary data transfer and keeps your new Frontify library easier to manage.
4. Pause changes during migration
4. Pause changes during migration
Once the migration starts, avoid making changes to the assets or metadata included in the migration scope.
Changes made in Bynder during the migration may not be reflected in Frontify and can affect the consistency of the migrated data.
Migration process
The Bynder automated migration follows three main stages.
Stage 1: Preparation
During preparation, your team works with Frontify to confirm access, scope, and metadata requirements. This stage includes:
Providing required Bynder admin access
Confirming whether all assets or only marked assets should be migrated
Confirming whether all custom metadata or a selected subset should be migrated
Preparing any required Bynder metaproperty tagging
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 the Bynder API
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 the 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
Descriptions
Creator information
Tags
Custom metadata
Any agreed asset subset or metaproperty-based scope
Customer responsibilities
To keep the migration running smoothly, your team is responsible for:
Providing the required Bynder admin access
Ensuring the admin access allows OAuth app creation
Confirming which assets should be migrated
Marking assets through a custom metaproperty, if only a subset should be migrated
Confirming which custom metadata should be migrated
Avoiding changes in Bynder 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 Bynder’s API to the authorized OAuth user.
This means that some data may not be available for migration if it is restricted by Bynder permissions, unavailable through the API, or affected by API-related limitations or errors from Bynder.
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 Bynder automated migration process. Bynder is a third-party platform and may change its API behavior, permissions, export capabilities, available metadata, or system functionality at any time.
Frontify does not control Bynder’s API, system availability, rate limits, permissions model, data structure, or how Bynder exposes assets and metadata to authorized users. Your team is responsible for ensuring that the correct assets and metadata are available to the OAuth user used 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: