• Live server where customer adds content and articles, which are store in the database
  • Staging server where we add new functionality, fields, sections and more

When the development of the new functionality on the staging server is complete, it should be merged with the new content of the live server.

How easy is this to handle? Is it as easy as just importing the staging db server into the live server one? Will not existing content be overwritten?

2 Answers 2


The way we do it is we take a copy of the live database when we begin development work, do the dev work on local/stage, get sign off... then manually add the new fields etc onto the live database. Otherwise, you're going to lose data.

I don't know of any way you could automagically merge two different databases.

One method to help speed up copying fields from one database to another (which is what you're doing) is to use the Field Manager plugin, which can export fields as JSON from your staging version, and you can import that JSON using Field Manager again on the live version. You'll still need to manually assign those fields to the associated sections.


Another way you could try is to check out Database & Asset Syncing Between Environments in Craft CMS written by @nystudio107 on the Slack channel. I'm sure he'd be able to help with any sticking points.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.