--- canonical: https://amplience.com/developers/docs/dev-tools/content-sync/ title: Content sync description: Overview for content sync, including setting up mappings and sync jobs. image: https://cdn.media.amplience.net/i/ampproduct/sync-unidirection-lm?w=1200&h=630 image_width: 1200 image_height: 630 audience: Business User date_published: 2026-03-18 date_modified: 2026-05-27 --- # Content sync overview When working with Dynamic Content, you’ll typically use multiple hubs to keep your development, testing and production separate. **Content sync** makes it easy to copy content between these hubs, helping you manage content safely and efficiently across environments. > **Note:** Content sync capabilities - such as the number of items you can sync - vary depending on your [sync plan](https://amplience.com/developers/docs/dev-tools/content-sync/faq/#what-is-my-content-sync-plan). ## What is content sync? Content sync lets you efficiently transfer content between hubs in multi hub set ups, providing a user friendly alternative to using the CLI tool for moving, copying, and cloning content. It transfers content along with all of its relationships, localized content and hierarchies **between repositories across different hubs**. ## What you can use it for Content sync simplifies a range of common workflows: * Promoting new features and related content from development to test hubs, and then to production hubs * Copying live production data to development or test hubs for building and testing new features safely * Running stress tests against realistic datasets without affecting live content ## How sync works Once sync has been set up - by configuring **mappings** between source and destination hubs - you can control syncing content between those hubs. Sync operations are driven by changes in the source hub. ### Mappings Mappings establish relationships between **repositories** in different **hubs**, and the **direction** that content will flow. A mapping has two parts: - **Hub mapping** – Defines the source and destination hubs, and the sync direction (one-way or two-way) - **Repository mappings** – Define which repositories can be synced with repositories in other hubs Mappings only need to be created once and remain persistent, so they can be reused for future sync jobs. An administrator must configure mappings before content can be synced. Learn how to [Configure mappings](https://amplience.com/developers/docs/dev-tools/content-sync/setting-up-sync). You do not need to map to the folder level - sync automatically creates and manages the folder structure. See [How sync handles folders](https://amplience.com/developers/docs/dev-tools/content-sync/faq/#how-does-sync-work-with-folders). Once mappings are set up, admins and developers can sync content between those repositories. See how to [Sync content](https://amplience.com/developers/docs/dev-tools/content-sync/syncing-content). > **Info: Content graphs** > To keep all related content together, content sync considers each content item and its linked content as a single connected structure, called a content graph. > > See [How content graph size affects syncing](https://amplience.com/developers/docs/dev-tools/content-sync/faq/#how-does-content-graph-size-affect-syncing). ### Sync direction When content is synced, the direction is determined by the hub mapping, and can be either: - **One-way** – Transfers content in a single direction (for example, from Production to Test), helping protect production environments from accidental overwrites: ![Unidirectional syncing between hubs](https://cdn.media.amplience.net/i/ampproduct/sync-unidirection-lm?w=1880&fmt=png&) - **Two-way** – Transfers content in both directions between a pair of hubs (for example, between Test and Staging hubs), supporting development and testing activities. ![Bidirectional syncing between hubs](https://cdn.media.amplience.net/i/ampproduct/sync-bidirection-lm?w=1880&fmt=png&) ### Sync settings During the initial sync of content, every item in the content graph is transferred to the destination hub. For subsequent syncs, settings allow you to control aspects of the process. For example, you can choose to sync either all content items (making the source and destination match), or only content items that have been modified in the source hub since the previous sync. For more information, see [Settings for syncing content](https://amplience.com/developers/docs/dev-tools/content-sync/syncing-content/#settings-for-syncing-content). ## Role-based permissions To help prevent against accidental or unintended syncing, roles and permissions are used to control who is allowed to setup and use sync. - **For setting up and configuring sync:** - To set up sync and configure mappings, you must have the admin role on both the source and destination hubs in each mapping. - **For syncing content and viewing sync information:** - To **view mappings**, you must have the developer role (or above) on both the source and destination hubs - To **sync content**, you must have the developer role (or above) on both the source and destination hubs - To **list and view sync jobs**, you only need the Member role on hubs ## Related pages [Content Management API](https://amplience.com/developers/docs/apis/content-management/)