---
canonical: https://amplience.com/developers/docs/dev-tools/content-sync/setting-up-sync/
title: Setting up content sync
description: Learn what you need to do as an administrator to set up content sync for developers to sync content using Amplience Dynamic Content.
image: https://cdn.media.amplience.net/i/ampproduct/sync-setup-hub-mappings-doc-hub?w=1200&h=630
image_width: 1200
image_height: 630
audience: Business User
date_published: 2026-06-24
date_modified: 2026-07-29

---

# Setting up content sync

This guide explains how to set up Amplience content sync, including permissions and mapping configuration, ready for developers to sync content.

> **Note:** To set up content sync you will need [hub administrator permissions](https://amplience.com/developers/docs/dev-tools/content-sync/#role-based-permissions).

## Setup considerations

As part of setting up sync, you should:  

- Check whether sync users want the option to ignore schema validation. See [Schema validation](#schema-validation-and-sync).
- Ensure sync users have the developer role (at least), on the hubs they want to sync. See [Permissions](https://amplience.com/developers/docs/dev-tools/content-sync/#role-based-permissions).

## Configuring sync mappings

Mappings determine which repositories in one hub will sync with repositories in other hubs.

You can create and manage mappings using Dynamic Content (shown below), and also using the [Content Management API](https://amplience.com/developers/docs/apis/content-management/). 

![Dynamic Content mappings window showing some sync mappings](https://cdn.media.amplience.net/i/ampproduct/sync-setup-hub-mappings-doc-hub?w=1880&fmt=png 'Dynamic Content mappings window showing some sync mappings')

> **Tip: Permissions for configuring mappings**
> You must have the hub admin role on both hubs in a mapping, to create, edit, and delete mappings. See [permissions](https://amplience.com/developers/docs/dev-tools/content-sync/#role-based-permissions).

**To configure mappings using Dynamic Content:**

1. From the Dynamic Content "Settings" menu, choose "Hub mapping":

    ![Accessing mappings from the Settings menu](https://cdn.media.amplience.net/i/ampproduct/sync-setup-menu-item-doc-hub?w=1880&fmt=png 'Accessing mappings from the Settings menu')

2. Select the hubs between which content will be synced, and the [sync direction](https://amplience.com/developers/docs/dev-tools/content-sync/#sync-direction). Then click **Get repositories**:

    ![Setting up hub mappings with Dynamic Content](https://cdn.media.amplience.net/i/ampproduct/sync-setup-enter-hub-mappings-doc-hub?w=1880&fmt=png 'Setting up hub mappings with Dynamic Content')

    If the mapped source and destination hubs use different asset stores, a warning is shown. You can proceed, but any synced content referencing media from missing asset stores cannot be published. See [Mismatched asset stores](#asset-stores-and-media).

3. Set the required repository mappings. Note, the repository mapping direction is determined by the hub mapping.

    :::tip
    
    Where possible, Dynamic Content suggests mappings based on similar repository names across hubs, but you can adjust them as needed.
    
    :::

    ![Suggested repository mappings in Dynamic Content](https://cdn.media.amplience.net/i/ampproduct/sync-setup-suggested-repo-mappings-doc-hub?w=1880&fmt=png 'Suggested repository mappings in Dynamic Content')

> **Tip: Tips for mapping repositories**
> - You don't need to map every repository in the hub, only those that are relevant to the content being synced
> - Sync automatically takes care of folder mappings for you - see [How does sync work with folders?](https://amplience.com/developers/docs/dev-tools/content-sync/faq/#how-does-sync-work-with-folders)
> - Repositories must be mapped to the corresponding type of repository, for example, a slot repository must be mapped to a slot repository

## Asset stores and media

When content is synced, media references are included, but the media files themselves are not. Therefore, to ensure referenced media is available to synced content, both the **source and destination hubs need to use the same [asset store](https://amplience.com/developers/docs/knowledge-center/key-terms/#asset-store)**. 

For example, when syncing *Content A (including images)* from ***Prod Hub (Repo A)*** to ***Dev Hub (Repo A)***:

**If both hubs are connected to the same asset store**:
```text
Prod Hub (Repo A) — Asset Store: Media Store 1
   │
   │  Content A + image references
   ▼
Dev Hub (Repo A) — Asset Store: Media Store 1

Result:
- Images are available in Dev Hub
- Content syncs and can be published
```

**If the hubs are connected to different asset stores**:
```text
Prod Hub (Repo A) — Asset Store: Media Store 1
   │
   │  Content A + image references
   ▼
Dev Hub (Repo A) — Asset Store: Media Store 2

Result:
- Images are not available in Dev Hub
- Synced content cannot be published
```

The asset store can be within Content Hub or a different asset management system, such as Bynder.

### Mismatched asset stores

When you map hubs with different asset store configurations, a warning highlights the mismatch. For each hub, the message lists the asset stores that are configured on that hub but not on the other.

![Warning of mismatched asset stores for mapped hubs](https://cdn.media.amplience.net/i/ampproduct/sync-mismatch-asset-store-1?w=1880&fmt=png 'Warning of mismatched asset stores for mapped hubs')

Syncing can still continue with mismatched asset stores, but any content that references media stored in a mismatched asset store will fail to publish because those assets are unavailable to the hub.

## Schema validation and sync

**Schema validation** helps maintain the integrity of synced content, and runs by default during syncing. It checks each content item against its associated schema and content type on the destination hub. Any content items that fail validation are not synced.

> **Info: Deciding if schema validation is required...**
> It's recommended to use schema validation when syncing content to production hubs.
> 
> When configuring sync mappings you may need to confirm with developers which hubs require schema validation.

To ignore schema validation, an admin user must enable the **Ignore schema validation** property on both the **source and destination hubs**. See [Hub properties](https://amplience.com/developers/docs/user-guides/basics/dynamic-content/settings/#properties).

> **Note:** As a safeguard, enabling **Ignore schema validation** on the hubs doesn't apply it automatically - it must also be selected each time a sync starts, or schema validation will run as normal. See [Starting a sync](https://amplience.com/developers/docs/dev-tools/content-sync/syncing-content/).

## Updating mappings

You can update both the hub and repository parts of a mapping.

Before changing mappings, consider the following:

- Updating the source hub or repository - This may cause previously synced content to be overwritten with content from the new source

- Updating the destination hub or repository - This may create duplicate content across hubs. The updated mapping will only affect future sync jobs and will not affect content that has already been synced

> **Info: Let users know if you update a destination mapping**
> This will help them to find where content has been synced to.