Make Changes Safely

The safest way to change your site is to test the change on a copy first. Every Kinsta site comes with a free staging environment, so you never need to experiment on the site your visitors are using.

The safe-change workflow

  1. Create or refresh your staging environment from live.
  2. Make and test your change on staging.
  3. Take a manual backup of your live site.
  4. Push the change from staging to live.
  5. Check your live site. If anything’s wrong, restore the backup.

Use your free staging environment

Why it matters: A plugin update, theme change, or new PHP version can break a page in ways you won’t see until a visitor does. Staging is a separate, private copy of your site where you can find those problems first.

When to use it: Before updating WordPress core, major plugins, or your theme; before changing PHP version; and for any design or code work.

How to start: In MyKinsta, select your site, click the environment name (for example, Live), select Create new environment, and clone your live site into a standard environment. For step-by-step instructions, see Create a WordPress Standard or Premium staging environment. If you need more resources, or several environments for different projects, see the premium staging add-on under Add-Ons.

Push changes to live

Why it matters: Once a change works on staging, pushing it to live copies it across in one step, without redoing the work by hand.

How to start: See Push Environments. You can push the whole site, or use a selective push to send only the files and folders or database tables you choose. When pushing database tables, you can run an automatic search and replace so links point to the right domain. You can also push from live to staging, which is a quick way to bring new posts and uploads into your test copy. Kinsta automatically backs up the environment you’re pushing to before the push starts.

Watch out for: Pushing the whole database replaces the live database. Any orders, comments, form entries, or new users added to your live site since staging was created will be lost. On a store or membership site, push only files, or select specific database tables and leave out tables such as WooCommerce’s order tables. On a multisite network, a full database push affects every subsite.

Back up before any risky change

Why it matters: Daily backups may be up to a day old. A manual backup taken just before a change means you can roll back without losing anything.

How to start: Create a manual backup under Backups. You can also restore a backup to staging, which is useful for checking an older version without touching live.

Update URLs across your site with Search and Replace

Why it matters: Changing your domain or moving to HTTPS can leave old URLs stored throughout your database.

How to start: Use the Search and Replace tool in MyKinsta. Kinsta takes a backup automatically before making the replacement, and can clear your site cache afterwards. Try the replacement on staging first if you’re unsure what it will match.

Start new sites from an existing one

Why it matters: If you build several similar sites, setting up the same theme and plugins each time takes hours.

How to start:Clone a site to create a new site from an existing one, including its theme, plugins, and settings.

Show visitors a maintenance message during updates

Why it matters: While plugins or themes are updating, visitors could see a half-updated page. Maintenance mode shows them a short message instead.

How to start: You can turn on maintenance mode when updating plugins or themes in MyKinsta. See WordPress Maintenance Mode.

Watch out for: If an update fails, the site can get stuck showing the message. To fix it, delete the .maintenance file from your site’s root folder using the File Manager, SFTP, or SSH.

In your routine

Use the safe-change workflow for anything bigger than a minor plugin update: New major WordPress versions, theme updates, PHP upgrades, and new plugins. A monthly check that a backup restores to staging means you’ll know your safety net works before you need it. See Your Maintenance Routine.

Was this article helpful?

© 2013 - 2026 Kinsta Inc. All rights reserved. Kinsta®, MyKinsta®, DevKinsta®, and Sevalla® are trademarks owned by Kinsta Inc.The WordPress® trademark is the intellectual property of the WordPress Foundation, and the Woo® and WooCommerce® trademarks are the intellectual property of WooCommerce, Inc. Uses of the WordPress®, Woo®, and WooCommerce® names in this website are for identification purposes only and do not imply an endorsement by WordPress Foundation or WooCommerce, Inc. Kinsta is not endorsed or owned by, or affiliated with, the WordPress Foundation or WooCommerce, Inc. Legal information