---
canonical: https://amplience.com/developers/docs/dev-tools/content-sync/syncing-content/
title: Syncing content
description: Learn how to sync content across hubs, repositories and folders using Amplience Dynamic Content.
image: https://cdn.media.amplience.net/i/ampproduct/sync-single-content-dialog-with-radio-buttons?w=1200&h=630
image_width: 1200
image_height: 630
audience: Business User
date_published: 2026-03-18
date_modified: 2026-07-29
---

# Syncing content

Once sync has been setup, you can transfer content by using Dynamic Content or the [Content Management API](https://amplience.com/developers/docs/apis/content-management/). 

> **Note: Content sync capabilities**
> Your plan determines sync capabilities - such as how many items you can sync. See [What is my content sync plan?](https://amplience.com/developers/docs/dev-tools/content-sync/faq/#what-is-my-content-sync-plan).

## Pre-sync checklist

Even though your administrator has set up mappings, it's worth checking the following to help smooth the process:

- **Permissions** - Ensure you have the [developer role](https://amplience.com/developers/docs/dev-tools/content-sync/#role-based-permissions) (or higher) on both the source and destination hubs. 
- **Schema validation** - If schema validation is required, you can pre-empt schema validation issues by ensuring that content schemas and types match in the source and destination hubs for the content being synced.
- **Localized content** - If you're syncing localized content, matching locales must exist on the source and destination hubs. See [How sync handles localized content](https://amplience.com/developers/docs/dev-tools/content-sync/faq/#localized-content).
- **Extensions** - Check whether the content includes any extensions. These will not be synced and should be recreated in the destination hub to prevent issues with the content.

> **Tip: Sync limitations**
> For information about what's included in sync operations, see [Scope and limitations](https://amplience.com/developers/docs/dev-tools/content-sync/faq/#scope-and-limitations).

## Starting a sync

To start a sync from Dynamic Content, select the **Sync** option from the content library (shown below) or from the authoring experience.

> **Tip:** You can select up to 20 content items to sync.
> 
> You can also start a sync using the [Content Management API](https://amplience.com/developers/docs/apis/content-management/).

![Selecting Sync in Dynamic Content](https://cdn.media.amplience.net/i/ampproduct/sync-menu-option?w=1880&fmt=png 'Selecting Sync in Dynamic Content')

> **Note:** In Dynamic Content, the option to "Sync" is available for content only when:
> 
> - The repository from which you want to sync content is [mapped to a repository in a different hub](https://amplience.com/developers/docs/dev-tools/content-sync/#mappings)
> - You have the [developer role](https://amplience.com/developers/docs/dev-tools/content-sync/#role-based-permissions) (or higher) on both the source and destination hubs

## Settings for syncing content

When using Dynamic Content to sync content, the Sync dialog provides a range of settings.

![Sync dialog in Dynamic Content](https://cdn.media.amplience.net/i/ampproduct/sync-single-content-dialog-with-radio-buttons?w=1880&fmt=png 'Sync dialog in Dynamic Content')

### Destination hub

This option is displayed only if multiple hubs are mapped for the selected content.

### Job Label

Use the label to help you clearly identify the sync operation in the Jobs list. See [Viewing sync status](#viewing-sync-status).

### Sync options

When syncing content, you can choose whether to:

- **Sync all source hub content** - Completely overwrite the content on the destination hub to match the source hub

- **Sync updated source hub content only** - Transfer only content that has changed on the source hub, retaining any changes made only on the destination hub

This simple example illustrates the difference between the sync options:

![Example showing how sync options affect destination hub content](https://cdn.media.amplience.net/i/ampproduct/ve-sync-model-lm?w=580&fmt=png&)

### Ignore schema validation

This option is only available if the **source and destination hubs** are set up to allow schema validation to be ignored. See [Schema validation and sync](https://amplience.com/developers/docs/dev-tools/content-sync/setting-up-sync/#schema-validation-and-sync).

If this option isn't available, ask your administrator to enable it for you. 

## Viewing sync status

The status of a sync will be one of the following:

| Status         | Description                                                           | 
|:---------------|:---------------------------------------------------------------------|
| `Completed`    | Job finished successfully — the chosen content has been synced        | 
| `Created`      | Job has been requested and is waiting for another job to finish first |
| `In progress`  | Job is currently running, duration depends on job size              |
| `Failed`       | Job could not complete — content may be partially synced. See [Resolving failed sync jobs](https://amplience.com/developers/docs/dev-tools/content-sync/syncing-content/#resolving-failed-sync-jobs).|  

Each time content is synced, a sync job is created and shown in the Jobs list. 

### Checking the sync Jobs list

To check the status of sync operations, in Dynamic Content click the "Jobs" icon in the masthead.

![Identifying when a sync job has run in Dynamic Content](https://cdn.media.amplience.net/i/ampproduct/sync-masthead-icon?w=1880&fmt=png 'Identifying when a sync job has run in Dynamic Content')

> **Tip: Notification of recent sync jobs**
> If a sync job has started since you last viewed the list of jobs, the "Jobs" icon is updated with an "i" (shown above).

The "Jobs" list shows all sync jobs for your current hub. For example, if you're working in `Hub 1` within Dynamic Content, you will see jobs such as `Hub 1 → Hub 2`, and `Hub 3 → Hub 1`.

![The Dynamic Content Jobs list showing sync jobs status](https://cdn.media.amplience.net/i/ampproduct/sync-jobs-list?w=1880&fmt=png 'The Dynamic Content Jobs list showing sync jobs status')

### Displaying additional sync details

To see detailed information about a sync job, double click on it in the Jobs list:

![Sync panel in Jobs list](https://cdn.media.amplience.net/i/ampproduct/sync-completed-job?w=1880&fmt=png 'Sync panel in Jobs list')

> **Tip: What are sync Outputs?**
> Sync **Outputs** are the total number of items synced in a job. This includes all items within the content graph.

### Publishing synced content

Once a sync finishes successfully, you can publish content directly from the Sync Job details, by clicking **Publish to "*hub name*"**.

The Publish option is only available after a successful sync.

After publishing, the Sync Job details update to show that the content is published.

![Published synced content shown in Sync Job details](https://cdn.media.amplience.net/i/ampproduct/sync-publish?w=1880&fmt=png 'Published synced content shown in Sync Job details')

> **Note:** The Sync Job details show publishing status regardless of where the content was published from (for example, the [Content Library](https://amplience.com/developers/docs/user-guides/basics/dynamic-content/content-library/#the-content-library-window)). The time since publishing is only displayed if the **latest version** of the content is published. For more information, see [publish status](https://amplience.com/developers/docs/user-guides/produce-content/publish/#publish-status).

## Checking revision history for sync

Successful sync operations are recorded in the [revision history](https://amplience.com/developers/docs/user-guides/produce-content/revisions/) of both the source and destination content.

> **Info:** Newly synced items always start at v2 in the revision history.

Each entry in the revision history shows the sync outcome (**content changed** or **unchanged**) and the direction (**to** or **from**), in the following format:

- `Sync (with changes) to hub "[hub-label]" (Job ID [job-id]) on [date-time-stamp] by [user-name]`

- `Sync (no changes) to hub "[hub-label]" (Job ID [job-id]) on [date-time-stamp] by [user-name]`

- `UPDATED via sync from hub "[hub-label]" (Job ID [job-id]) on [date-time-stamp] by [user-name]`

- `Sync (no changes) from hub "[hub-label]" (Job ID [job-id]) on [date-time-stamp] by [user-name]`

For example:

![Checking sync revision history in Dynamic Content](https://cdn.media.amplience.net/i/ampproduct/sync-version-history?w=1880&fmt=png 'Checking sync revision history in Dynamic Content')

> **Note:** The actual revision history of content is not synced. See [Scope and limitations](https://amplience.com/developers/docs/dev-tools/content-sync/faq/#scope-and-limitations).

## Resolving failed sync jobs

Sync jobs can fail for several reasons. Common causes include:

- **Content graph exceeds the number of items that sync supports** - The job is marked as **Failed** in the Jobs list. You can resume the sync by restarting the job from where it stopped.

    For more details, see [How content graph size affects syncing](https://amplience.com/developers/docs/dev-tools/content-sync/faq/#how-does-content-graph-size-affect-syncing).

- **Number of items to sync exceeds your plan allowance** - Your sync plan limits how many items you can sync each month. Learn more about [content sync plans](https://amplience.com/developers/docs/dev-tools/content-sync/faq/#what-is-my-content-sync-plan).

When a sync job fails, content is transferred only up to the point of the error. After identifying and fixing the cause, you can retry syncing to complete the process.

To find details of why a sync job has failed, click on it in the "Jobs list" to display the job details, then click on the "Errors" tab.

![The Jobs list showing a failed sync job in the Sync details panel](https://cdn.media.amplience.net/i/ampproduct/sync-error-details-panel?w=1880&fmt=png 'The Jobs list showing a failed sync job in the Sync details panel')

> **Tip:** The ~~Sync~~ icon indicates that the sync job has failed.

## Related pages

[Using the CLI tool to copy and migrate schemas and types](https://amplience.com/developers/docs/dev-tools/cli-tool/copy-import-export/#migrate-schemas-and-content-types)