<p>You don't wish to just pull down the production environment to your development server? This is how we solve this problem at work, by only editing the production server's database and then pulling it when it is updated.</p>

<p>There are quality scripts for syncing environments from the command line. You can simply run <code>./pull_db.sh</code> and it will do everything for you.
<a href="https://github.com/nystudio107/craft-scripts" rel="nofollow noreferrer">https://github.com/nystudio107/craft-scripts</a></p>

<p>There are also new craft 3 plugins for export/import but I have not had much success so far.</p>

CC BY-SA 4.0
2018-06-01T13:17:25.847Z
I thought about it more and I guess it does make the most sense to pull down everything.
Danielle Frappier
CC BY-SA 4.0
2018-06-01T15:09:00.093Z
I'm glad you agree, it can be one of the most dangerous parts of working with craft. It is easy to overwrite data, especially if you add a third 'staging' environment. I think a better solution is coming soon with the newer craft 3 plugins.
Clark Nelson
CC BY-SA 4.0
2018-05-31T17:30:29.407Z
2018-05-31T17:30:29.407Z
Clark Nelson
<p>I have a dev server and a production server, they are on two different databases. The editors will only be logging into the production space to add content. I'm looking for an easy (but still manual) way to export content. I rather not do an entire database dump every time. </p>

<p>Any thoughts? </p>

<import><export>
Importing/Exporting, but not everything
# Importing/Exporting, but not everything

(Asked by: username_0 on 2018-05-31)

I have a dev server and a production server, they are on two different databases. The editors will only be logging into the production space to add content. I'm looking for an easy (but still manual) way to export content. I rather not do an entire database dump every time.

Any thoughts?

**Tags:** import, export

---

## 1 answers

### Answer by username_1 on 2018-05-31. Score: 0 | Accepted answer

You don't wish to just pull down the production environment to your development server? This is how we solve this problem at work, by only editing the production server's database and then pulling it when it is updated.

There are quality scripts for syncing environments from the command line. You can simply run `./pull_db.sh` and it will do everything for you.
<https://github.com/nystudio107/craft-scripts>

There are also new craft 3 plugins for export/import but I have not had much success so far.

> **Comments:**
> **username_0**: I thought about it more and I guess it does make the most sense to pull down everything.  
> **username_1**: I'm glad you agree, it can be one of the most dangerous parts of working with craft. It is easy to overwrite data, especially if you add a third 'staging' environment. I think a better solution is coming soon with the newer craft 3 plugins.  

---

