Staging And Cloning WordPress

Use this page when a WordPress change should be tested on a copy before touching the live site. Staging is especially useful for PHP changes, large updates, theme work, and business-critical plugins.

When To Use A Clone

  • Major updates

    Test WordPress core, WooCommerce, page builders, or membership plugin updates.

  • PHP changes

    Check whether the site works on a newer PHP version before switching live traffic.

  • Design or plugin work

    Try new themes, plugins, layouts, and settings without affecting visitors.

Clone With wp-toolkit

If wp-toolkit is available on your server, use it as the first place to look for staging or cloning options.

  1. Log in to cPanel.
  2. Open wp-toolkit.
  3. Select the WordPress installation.
  4. Look for clone, staging, or copy options for that installation.
  5. Choose a staging location, such as a subdomain or folder.
  6. Create the clone and test the staging copy.

wp-toolkit options can vary

wp-toolkit features vary by server and account type. If the clone option is not available, contact Fused for help choosing the safest path.

For SSH-based cloning, use the WP-CLI workflow in cPanel's wp-toolkit cloning guide.

Review wp-toolkit and WP-CLI cloning

Do not test live payment or email workflows blindly

A clone may still contain real forms, customer data, payment settings, and email settings. Disable production payment capture and avoid sending test mail to real customers.

After Testing

Decide whether to repeat the changes on the live site or schedule a migration window. For small changes, repeating the steps manually on the live site is often cleaner than pushing a full clone over production.

Before Copying Changes Live

Confirm:

Be careful replacing a live database

A full staging-to-live push can overwrite orders, form entries, user registrations, comments, and other data created after the clone was made.

If this article did not solve it, contact Fused support and we will help from there.

Contact support