Content sync repository mappings
Release date: 11th November 2026
Content sync lets you copy content between Amplience content hubs. Content is synced along with its linked content, localized content, and hierarchies.
Admins set up content sync by creating mappings, which define the source and destination hubs and which repositories content is synced between.
When an admin changes the destination repository in a content sync mapping, previously synced content is now moved to the new destination repository. Before this change, the next sync created new copies in the new repository and left the existing content in the original repository. Moving the content avoids duplicate copies in the destination hub.
- When content is moved - Content items are moved the next time they’re included in a sync job, whichever sync option you choose. Items that aren’t included stay in the original destination repository until they’re synced.
- Folders - The folder structure is created in the new destination repository.
- Schema validation - Content items that fail schema validation aren't moved and stay in the original destination repository.
- Revision history - Each moved content item has a record of the move added to its revision history.
- Plan allowance - Moved content items count toward your monthly sync allowance and are included in the Outputs total for the sync job.
For more information, see Updating mappings.