This is a paid integration available to enterprise and boost plans |
The Sitecore Content Hub Integration enables Frontify customers to migrate and continuously synchronize assets and metadata from Sitecore Content Hub to Frontify.
The integration is designed for enterprise organizations that maintain Sitecore Content Hub as their single source of truth for assets while leveraging Frontify for brand management, collaboration, and distribution.
Introduction
This guide will help you understand the options of the Sitecore Content Hub integration / automatic migrator. If you are migrating, it will automatically transfer assets and metadata to Frontify, while if you are leveraging a synchronization, you’ll be able to use assets managed in Sitecore Content Hub directly within Frontify, in any way you could use Frontify managed assets (e.g. in Portals, Templates, Sharing, etc).
What is Sitecore Content Hub?
Sitecore Content Hub is an enterprise Content Operations platform that combines DAM, PIM, CMP, and content governance capabilities. The DAM module enables organizations to centrally manage digital assets, structured metadata, taxonomies, and relationships across global teams.
The Sitecore Content Hub Integration connects the DAM module with Frontify to enable structured asset migration and ongoing synchronization — including full metadata alignment and version consistency.
When to use the Sitecore Content Hub integration?
You are moving from Sitecore Content Hub to Frontify as your primary DAM and want a fast, cost effective method to migrate your assets to Frontify.
When you cannot fully migrate Frontify to be your primary Digital Asset Management system and want to
Enable continuous synchronization of assets and metadata
Keep Sitecore Content Hub as the single source of truth (SSOT)
Reduce manual effort and duplicate maintenance
Ensure version consistency across systems
Provide an enterprise-ready hybrid DAM architecture
What the integration does
The integration enables a scheduled, automated synchronization from Sitecore Content Hub to Frontify. The integration is one-directional sync: Sitecore Content Hub → Frontify. Changes made in Frontify are not reflected in Sitecore Content Hub. Once synced, copies of the assets, along with their metadata are fully uploaded and stored in Frontify.
Metadata changes in Sitecore Content Hub are reflected in Frontify after the next scheduled sync, while new versions of the same asset in Sitecore Content Hub create new asset versions in Frontify. This preserves the version history on both sides.
Deletions in Sitecore Content Hub result in the deletion in Frontify during the next scheduled run.
The integration support all the filetypes supported by Frontify libraries.
Setup & Configuration
Frontify will set-up this integration for you based on your configuration preferences, which are listed below.
Note: An asset which no longer meets the sync conditions is considered deleted by the integration and will be deleted in Frontify.
Libraries
This integration can be set up to target multiple Libraries in Frontify. For each library, separate sync conditions, the criteria by which assets are defined to go into that library, can be set.
Sync conditions
In Sitecore Content Hub, the assets to be synced can be determined by one or both of the following:
Specific metadata values, which can be combined with AND & OR operators
Asset relations on Sitecore Content Hub (the customizable categorization mechanism of assets in Sitecore Content Hub)
These conditions must be set up for each target Library in Frontify separately, so it is possible for example to target assets with metadata value x to Library A, while value y would go to Library B.
It is also possible to sync all assets from Sitecore Content Hub, in which case no sync conditions are required.
Metadata mapping
Asset metadata from Sitecore Content Hub is mapped to Frontify as a 1:1 metadata synchronization. All structured fields are supported by the integration. Native Sitecore fields for Description and Keywords are mapped to Frontify Description and Tags.
Getting started
Setup is done collaboratively between the Customer and Frontify. The initial setup will likely require a technical administrator of Sitecore Content Hub in steps 3 & 4 below:
Determine if you are migrating or looking for a continuous sync. Steps 2 & 3 apply only to a continuous sync).
Decide on your desired libraries and the sync conditions (see above) by which you which to synchronize assets.
A Frontify developer token will be needed for the integration. Please see the linked article for instructions on how to generate one with access to the target libraries.
Create a Client on Sitecore Content Hub and note the Client ID and Client Secret.
Request a JSON Web Token (JWT) in Sitecore Content Hub API, using the client created in step 4.
Contact your Customer Success Manager at Frontify with the sync information, tokens (Frontify and JWT) information and a desired activation day.
Your CSM will contact relevant technical teams at Frontify to set up this integration. Please allow 5 business days for activation after your message and plan your activation day accordingly.
How frequently does the sync run?
How frequently does the sync run?
The standard sync interval is once every 24h, happening during night time in Europe and the Americas.
When first connected, depending on the number of assets that match the sync conditions, the sync may take quite long to transfer all the assets and a 24h interval is not guaranteed for the first days.
Can the integration be modified to match additional needs?
Can the integration be modified to match additional needs?
This integration was built in collaboration with a Certified Technical Partner of Frontify's .NFQ. The partner can be engaged by Frontify Customers for any customization needs at their own expense. Frontify grants permission to use the integration as a starting point for any Customer needed customizations .NFQ is contracted to do. Please contact your CSM to get in contact with the Partner.
Are there known limitations?
Are there known limitations?
The integration has some caveats.
There is no immediate retry mechanism for failed assets. Frontify technical support will attempt to rerun any missed assets identified by Customers.
Currently only authorization with API token supported, but OAuth planned for next version.