Now visit the Flows tab of Drupal Content Sync and hit "Add flow":

Select "import":

Provide a unique name for your flow:

If you're connecting the site to multiple pools that require different configuration, make sure to use a unique name for each workflow.
If you have multiple production sites, you can share the same configuration with the same name across these sites.

Enable your Root Entities

For each root entity type you want to import, you have to enable it. Root entity types are the entity types that are not dependent on another entity. Typically, these are your Nodes and Blocks. If you want to push Media or Taxonomy items individually, you can also configure them as root entities:

For Content Staging you won't need any unpublished content on live. So make sure to check the "Ignore unpublished content" checkbox:

Set the Import option either to "All" to pull any changes immediately to production or "Manually" if you want your editors to import them on demand:

Make sure the pool you created above is set to "Forced" or "All" import or "Allow" for "Manually" importing:

We recommend that you not only create and update content on your Content Stage but that you also delete it from there. In this case deleting a content on your Stage will also delete it on your Production site. To configure this, check the "Import Deletion" box:

If you want your editors to be able to delete content on live manually, check the box below it as well. If you only want editors to be able to delete content via the Content Stage site, don't check the box below.

If you're using Content Staging we recommend that you only allow editors to edit sites on their Content Stage environment. To enforce this, select "Forbid local changes and update" at the "Import updates" setting:

What are the alternatives?
DIsmiss local changes- Your editors can still make changes on the production site. But if new content arrives from stage, it will overwrite any changes you did on your production site directly.
Ignore updates completely- This will only import the content from stage once. You can then change it on your production however you like. This is not a recommended setting for content staging as you can't update content from your stage anylonger.
Update unless overwritten locally- Your editors can check an "Overwrite" checkbox individually for each content. As long as that checkbox is set, the Stage cannot update this entity anylonger. Only after you remove the checkbox will the stage be able to perform updates again.

Leave all other settings untouched.

Go through All Fields below the Entity Type Config

Check if you require the field values on your production site.

If you do want to import this on the production site, make sure the handler is set to a "Default" handler and "Import" is set to "Yes". If the handler is set to "Not Configurable" that means this field is required and we're importing it already regardless of your configuration.

If you do not want to import this on the production site, make sure the handler is set to "Disabled".

What does Merge Local Changes mean?
If you have chosen "Update unless overwritten locally" above, you can make changes to all these entities on your production site as well. If you still want to receive updates on paragraphs for example, you can chose to merge remote updates into your local updates. As soon as you check the "Overwrite" checkbox on the content, all field updates are ignored unless you chose "Merge local changes" on the field. In that case the Content Stage can still delete, update and add values on this field but your local updates will also be kept and merged into the remote updates.

Leave all other settings untouched.

Setup your Dependent Entities

Go through all entities that are referenced in your root entities above. This can easily be done by checking the reference fields of your root entity types. You can simply enable them:

Once they all have been enabled, ensure to also recheck the referenced entity types since those might also have references to other entity types which have to be imported.


Hit "Save" and wait for the export to finish:

Once the export is done, you will see a success message.