Copy an Environment Using Push or Pull

If you have made changes to an environment and now you want to copy those changes to another environment, you can use the “Push to” or “Pull from” action in the User Portal.

In this article, we will show you how to push or pull changes in any environment in any site in your WP Engine account.

Please note that if you are copying a multisite network, we recommend reading the Multisite Deployment Best Practices article first. 

If you need to copy an older checkpoint, you can use the Copy Environment tool as described in this article or use the backup and restore functionality.

Prefer to watch a video?

---

What are “Push to” and “Pull from” actions?

When you are ready to copy changes from one environment to another, you can use the “Push to” or “Pull from” action. Both of these actions work in the same way, so the only real difference is where you’re starting the copy process from.

“Push to” action

The “Push to” action allows you to push the contents of the currently selected environment to another environment.

For example, if you have been working on your website in the staging environment and now you are ready to publish everything to your live website, you can push staging to production.

“Pull from” action

The “Pull from” action allows you to pull the contents from another environment into the currently selected environment.

For example, if you want to add a new plugin, but you want to test it for compatibility before activating it on your live website, you can pull production to staging and then do all your testing there.

---

How to push or pull content between environments

1. Select the environment you want to start the copy process from.

• On the Sites page, select the site you are working on.
• Select the correct environment at the top of the page.
  • If you want to push content from this environment to another one, select the source environment.
  • If you want to pull content from another environment into this one, select the destination environment.

2. Click the Actions menu to reveal the options and then select either Push to or Pull from.

3. Select the destination or source environment.

• If you are using “Push to…”
  • Select the destination environment – the one you want to push content to.
    • The source environment is grayed out because you cannot change it on this page. However, if you selected the incorrect environment, you can click the site name in the breadcrumb menu at the top of the page to start over.

• If you are using “Pull from…”
  • Select the source environment – the one you want to pull content from.
    • The destination environment is grayed out because you cannot change it on this page. However, if you selected the incorrect environment, you can click the site name in the breadcrumb menu at the top of the page to start over.

4. Choose the content you want to include in the copy.

• Full environment: A full environment copy includes all the files and all database tables in the environment.
  • See what the file system includes.
  • See what the database includes.
    • We do not recommend pushing the entire database to the production environment. If you do, the production database will be completely overwritten. This can cause the live website to lose important data like new orders or new users, so be very careful when choosing this option.

• Custom: A custom copy includes all the files. See what the file system includes. In addition, you can choose which version of content to include and whether or not to include the database (as shown in the image below).
  • Select a version to push or pull.
    • The current environment: The current, most recent version of the content will be included in the copy. 
    • Select a backup point: A previous version from your selected backup point will be included in the copy..
  • Do you want to include the database? See what the database includes.
    • Check the box to include the database in the copy. 
    • If you are copying the current version of the environment, you will be given the option (after checking the box) to include all database tables or only specific database tables. However, only the entire database can be copied from a backup point.

5. Click Review details at the bottom of the page to confirm your selections.

6. Review your selections on the next page.
   • If something does not look correct, you can click the site name in the breadcrumb menu at the top of the page to start over.

7. Enable notifications.
   • If you would like to receive an email notification when the copy is complete, enter your email address.
     • We do recommend enabling this notification because it’s the only way you will know when the process is complete.

8. Finally, click the Push changes or Pull changes button to start the copy process.
   

---

What happens during the copy process?

After the copy request is submitted:

• If you are copying the current environment, the source is backed up before the copy to ensure the copied content is fresh.
• The destination is backed up before and after the copy.
• The destination is overwritten.
• An automated search and replace from the source domain to the destination domain is performed on all included database tables. This ensures all website URLs are correct when the process is finished.
  • On a multisite network, this search and replace may look different than expected, so we recommend reviewing the WordPress Multisite article before starting the copy process.
• The cache is automatically cleared on the destination environment to make sure everyone sees the new and updated content.
  

---

What happens after the copy is complete?

When the process is complete, and if you enabled the email notification, you will receive an email at the address(es) you provided confirming it was successful. Additionally, we will create a backup checkpoint of the destination environment.

Please note that copies of large environments may take a while. Also, once a copy has been started, do not make additional changes to either environment until the process is complete.

---

What specific content is included in a copy?

Each copy process includes the entire file system, but copying the database is optional. You can choose to include, partially include, or exclude the database.

File system

The file system includes all media, theme files, plugin files, scripts, wp-config.php, core files, etc.

Please note that a file system copy is fully destructive, meaning everything in the destination environment will be overwritten. If a file exists in the destination environment, but not in the source environment, it will be removed from the destination environment during the copy. There are no file system exclusions.

If you select to copy the file system only, no database information will be copied to the target environment. The database will remain as-is.

Database tables

The database includes all posts, pages, users, custom post types (for example: WooCommerce orders), and some settings. It is also possible for the database to contain theme and plugin settings. This varies, though, so if you are unsure, you can reach out to the theme or plugin author to ask.

When the database is included in a copy, a search and replace will automatically be run to update the source domain to the destination domain. Learn more about this process here.

If the environment is a multisite network, this search and replace will work similarly, but the results may look different than expected. We recommend reviewing this article before copying.

All database tables

This option overwrites the entire database of one environment with the entire database of another environment.

If you choose to include all database tables in the copy:

• Tables that exist in both the source and destination will be overwritten in the destination.
• Tables that exist in the source but do not exist in the destination will be added to the destination.
• Tables that do not exist in the source, but exist in the destination will be left as-is in the destination.

Specific database tables only

This option allows you to include specified database tables, excluding others. Only tables that exist in the source environment can be selected.

If you choose to include specific database tables only in the copy:

• Selected tables that exist in the destination will be overwritten in the destination.
• Selected tables that do not exist in the destination will be added to the destination.

When selecting the specific database tables option, you can either select specific database tables, or you can use “select all” tables, and then search or scroll through the list of tables and exclude specific ones.

Here are some example scenarios where you might want to copy only specific database tables:

• You have installed a theme or a plugin and only want to copy the tables related to it. You may need to refer to your plugin or theme support if you are not sure which tables hold the data you do not want to overwrite.
• You have added content to the target environment since the last copy and you hope to preserve that data when pushing it back.

To exclude pages and posts, do not select the following tables:

_posts
_postmeta

To exclude users, do not select the following tables:

_users
_usermeta

If you are using WooCommerce, you may want to exclude certain order data or user information from the deployment. In this case, do not include the following tables:

_posts
_postmeta
_woocommerce_order_items
_woocommerce_order_itemmeta

When using WooCommerce, we recommend enabling High Performance Order Storage, which separates orders into dedicated tables. This can simplify deployments by allowing those tables to be selected or deselected. Learn more here. When High Performance Order Storage is enabled, posts and postmeta are not used. Instead, the orders tables to exclude are:

_wc_orders
_wc_order_addresses
_wc_order_operational_date
_wc_orders_meta

For more information on deploying WooCommerce, see WooCommerce Best Practices.

---

Copying the database to production

We typically do not recommend copying a database to a production environment because the database will be rewritten entirely with the staging or development environment contents. This destructive process can cause the loss of important data, such as new orders or users.

If you added posts or pages to the staging or development environment that you want to copy to another environment, the easiest solution is to use the default WordPress Export/Import Tools to manually migrate that content to production. If more specific export parameters are necessary, then WP All Export has more customizable export options.

Alternatively, if you have added content to production, but you need to push or pull the staging or development environment database for some other reason, you will need to export the content from production before the copy, and then import it back to production after the copy is complete. The default WordPress Export/Import Tools can be used for this, as well as WP All Export for more customizable export options.

If you are using a theme that stores settings in the database, it would be best to make the changes on production and leverage the Preview Site theme feature as well as our Backup system.

If you are deploying a WooCommerce site, we recommend reviewing WooCommerce Best Practices first.

---

Copy tips

1. User Portal 301/302 redirects, SSL certificates, custom cache exclusions, Nginx rules, and other custom WP Engine server configuration options.
   • These items will not be copied using the Copy Environment process. These rules exist if added manually, and in most cases will not cause issues when excluded from a copy. The WP Engine Support team is happy to manually copy over any custom rules if necessary, by request.
2. We suggest enabling a maintenance page on the Source environment before initiating the copy process.
   • This can help you prevent any visual discrepancies, downtime, or missed orders. You can enable maintenance mode with a plugin or by leveraging default WordPress functionality.
3. To speed up a copy, reduce the scope of the content.
   • Reduce or offload storage to reduce overall size. Learn more here.
   • Optimize the database to minimize database size. Learn more here.

Specific plugins or themes can be duplicated by using the file system instead of performing a copy process. Plugins are stored in wp-content/plugins and themes can be found in wp-content/themes. You can access files by downloading a full or partial backup, by using SFTP, or with SSH Gateway.

---

NEXT STEP: Learn about the WP Engine backup and restore system