Title: dev env -> test env -> live env
Last modified: May 20, 2024

---

# dev env -> test env -> live env

 *  Resolved [cais4you1](https://wordpress.org/support/users/cais4you1/)
 * (@cais4you1)
 * [2 years ago](https://wordpress.org/support/topic/dev-env-test-env-live-env/)
 * Hello.
 * I’m excited about your plugin and the stagging functionality that you provide.
   Before we buy your pro plugin, we would like to see how the plugin works.
 * We develop websites for multiple clients and our focus is to do the development
   on our subdomains, we would like to sync the changes to the client’s subdomain
   and only after approval migrate the changes to the production system.
 * Since we know that clients add content on the production system we would need
   to know how to synchronize the data. I will give a real example from practice,
   which is happening to us:
 * We make a clone of a production site on which we start development. In the meantime,
   the client makes changes to his production part. In the phase when we are ready
   to migrate our changes to the live production it is necessary to include the 
   changes that the client has made on his production part.
 * DEV environment: our development on our subdomain: subdomain1.cais4you.sk
   TEST
   environment: test environment where the changes we make from DEV environment 
   and PROD environment are displayed. subdomain1.clientdomain.skPROD environment:
   clientdomain.sk
 * Please provide a short description on this status.
 * Thank you

Viewing 1 replies (of 1 total)

 *  Plugin Contributor [alaasalama](https://wordpress.org/support/users/alaasalama/)
 * (@alaasalama)
 * [2 years ago](https://wordpress.org/support/topic/dev-env-test-env-live-env/#post-17768452)
 * Hi [@cais4you1](https://wordpress.org/support/users/cais4you1/)
 * The (Dev > Staging > Production) setup can be made following [this guide](https://wp-staging.com/docs/cloning-a-staging-site-testing-push-method/).
 * We recommend exporting the new data added to the production site during the development
   period, then importing them into the staging site right before the push, this
   way you will ensure the staging site has the most recent data you would like 
   to see on the production site after the push.
 * For posts/pages and other default WordPress contents, you can check [this guide](https://wp-staging.com/docs/syncing-posts-or-pages-from-production-site-to-staging-site/),
   and for WooCommerce-related content, please check [this one](https://wp-staging.com/docs/skip-woocommerce-orders-and-products/#Export_Import_WooCommerce_Orders_Recommended_Option).
 * Thanks, 
   Alaa

Viewing 1 replies (of 1 total)

The topic ‘dev env -> test env -> live env’ is closed to new replies.

 * ![](https://ps.w.org/wp-staging/assets/icon-256x256.png?rev=2972932)
 * [WP STAGING - WordPress Backup, Restore & Migration](https://wordpress.org/plugins/wp-staging/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-staging/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-staging/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-staging/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-staging/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-staging/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [alaasalama](https://wordpress.org/support/users/alaasalama/)
 * Last activity: [2 years ago](https://wordpress.org/support/topic/dev-env-test-env-live-env/#post-17768452)
 * Status: resolved