Flows are standard Drupal config entities, so that your sitebuilders can easily export the configuration from one site and then import it onto another site so you don’t have to do the same configuration manually again and again.

There’s also a Copy remote Flow option available when you start configuring a new site. That way you can select a remote site and any one of their Flow configurations onto your new site. You can even mirror existing configuration from another site, meaning to swap push and pull- so when you have configured a publishing site with everything you need, you can just go ahead and use the Copy remote Flow action on a subscribing site, choose to mirror the config and it will apply the same configuration from your publishing site to subscribe to the exact same content.

Integrity checks

Our highest goal with Content Sync is to prevent broken content- we want everything to be exactly the same on subscribing sites as it was on the publishing sites. That’s why we document how every one of your content types is configured per site and make sure that before pulling a content item, it’s fields match the fields of the source site. For example if you have one site that has a new field Image description but it’s missing on the source site of your images, Content Sync will not import the content but instead put out a warning that there’s a configuration mismatch in your sites that needs to be addressed first.

There’s a button available to site builders called Show version mismatches that will point out the exact differences between the field configuration of entity types for all of your connected sites.


We extend Content Sync with new functionality every month, adding support for additional modules, content types and field types along the way. If there’s anything you’re missing, do let us know! We’re happy to help ?

There’s even an option to develop your own handlers per entity type and field type for the really fancy.

The only thing we won’t syndicate are user accounts due to the impact on your site’s security.


If your content type is enabled to create new revisions, Content Sync will do the same. So anytime an update is pulled from a remote site, a new revision will be created. This allows you to quickly switch back to an older revision.


By default, Content Sync will include all of your fields when pushing or pulling content. You can overwrite this per field to exclude fields whose content you don’t want to syndicate, e.g. if they’re site-specific.