Move a site or make a staging copy

  • advanced
  • staging
  • migration
  • licenses
  • permalinks

Updated

To move a WordPress site to a new host or domain, or make a staging copy, copy the database and files with your host's clone tool or a migration plugin. Then work through a short checklist on the new address: site URL, licenses, permalinks, and anything that lives in the Customizer.

Import/Export is not a full site backup. It copies settings, not pages or media.

Before you copy

  1. Export Styles, Settings, and Additional CSS from Dirigible → Import/Export on the live site. Keep those files even if the clone should copy the database.
  2. Note which Dirigible plugins are active, and that you have license keys for them.
  3. If you use an OpenRouter AI key, a Google Maps key, or tracking IDs, you'll confirm those after the move.

How do I copy the site?

Use your host's staging or clone tool if it has one. Most managed WordPress hosts include one in their dashboard, and it's the simplest route: it copies the database and files and usually updates the address for you.

Without one, a migration plugin such as Duplicator or All-in-One WP Migration packages the site on the old host and unpacks it on the new one. Follow that tool's steps, then work through the checklist below.

What to check after the copy

Work through these on the new URL, in this order.

1. Confirm the site URL

In Settings → General, WordPress Address and Site Address should match the new address, including https://. Your host's clone tool usually sets this. If images or admin links still point at the old domain, use the host's search-and-replace tool (or ask them to run it) before you keep going.

2. Re-activate licenses

A new address looks like a new site to licensing.

  1. Go to Dirigible → Licenses.
  2. Click Re-Activate on each Active card so the key is checked from the new address.
  3. On a brand-new install with no keys, paste each key and click Activate.

Details: Add license keys for your Dirigible plugins.

3. Refresh permalinks

Go to Settings → Permalinks and click Save Changes without editing anything. That rebuilds event, people, and other plugin URLs. See Fix 404 errors by refreshing permalinks.

4. Bring over Customizer values if they're missing

If the clone copied the database, styles and settings are already there. If you built a fresh WordPress and only copied files, import the JSON from step 1:

  1. Import Styles, then Settings.
  2. Paste Additional CSS into Appearance → Customize → Additional CSS if you use it.
  3. Re-upload logos if images don't appear.

Dirigible settings survive a child-theme switch. Additional CSS does not. If the staging site is on a different child, paste the CSS there.

5. Confirm keys and tracking

  • Dirigible → AI / OpenRouter: the saved key is in the database, so a true clone still has it. A fresh install needs the key pasted again.
  • Dashboard → Tracking & Privacy: tracking IDs and Custom Embeds.
  • Google Maps, if you use Locations.

Turn Track Admin Sessions off on a live site. It's fine on while you test staging.

How do I keep a staging site out of Google?

On the staging site, go to Settings → Reading and check Discourage search engines from indexing this site. Leave it unchecked on the live site.

A few more staging habits:

  • Don't use the same OpenRouter key limit you rely on for production if you'll be generating a lot of test alt text. Give staging its own key, or skip AI there.
  • The site pop-up still runs. Limit it to a page you don't mind, or leave Enable off on staging.

Check that it worked

  • Homepage, an inner page, and the mobile menu.
  • A Gravity Form submit.
  • An event URL, a people or location page, and shop/checkout if you use them.
  • Licenses still Active after a reload.

Related guides

Built by Dirigible Studio. Get in touch