Skip to main content
Theme

Tutorial

Migrate a WordPress site

This walks through a whole migration of a WordPress site to a new Insites v6 instance: every published page with its design, whatever built it, the posts as a database table with a collection page, the media library, the people, the forms, the redirects, and a WooCommerce shop, which keeps selling on the new site through the site's own Stripe account. A site of around 50 pages, 60 posts and 600 files takes about 20 minutes for the dry run and about an hour and a half to load and check. You can close the page at any point: the migration carries on, and you come back to it from Migrations in the menu on the left.

What you need
  • A new, empty Insites v6 instance, the Developer role on it, and an access token from its CLI tab in Insites Console. How to create one.
  • A WordPress user made for the tool, with the Administrator role, and an Application Password for it, made in its profile. The site must be on https. How to make one.
  • Or, for a site that cannot make an Application Password (a free WordPress.com site), its export file, from Tools, Export, All content. What moves from a file.
  • If a security plugin such as Wordfence switched Application Passwords off, its setting switched back on for the move.
  • If a plugin keeps your form entries (Flamingo, WPForms Pro, Gravity Forms): each form's entries exported as a CSV. More on the export.
  • If Yoast SEO Premium or Rank Math keeps the site's redirects: their export (a CSV from Yoast, an Apache or Nginx file from Rank Math).
  • If the site has a WooCommerce shop: access to the Stripe account it will be paid into. You add its keys after the migration.

How the wizard works

A migration has seven stages: Source, Destination, Transform, Plan, Load, Verify and Launch. Each stage is split into a few short steps, listed down the side of the page. The footer at the bottom always holds Back, where you are, and the one thing to do next. When the next thing cannot be done yet, the footer says why. Nothing is written to the new instance until you approve the plan and type its code.

1. Source: connect the WordPress site

  1. Sign in and click New migration.
  2. On Where are you coming from?, choose WordPress site. A platform that is not listed? The last tile, Request a platform, tells us which one you use.
  3. The next screen asks only for The site's address: the address visitors use, for example https://www.example.com. For a site of a multisite network, give that one site's own address. Press Next.
  4. The key screen lists what to have ready for WordPress and shows how to make an Application Password, step by step. Type the user's name into WordPress user name, paste the password into Application Password, and press Connect and check.

The tool checks the address is the site the password belongs to, and that the user has the Administrator role. If the password is refused, the test says why: a wrong password, no such user, or Application Passwords switched off. What each one means. It then lists what the user can read under Can read.

What it holds then groups the site the way WordPress does: Pages and design, Media library, Forms, People, WooCommerce shop and Redirects. Each part says whether it is copied, and what is left for you, such as the comments or the plugins.

2. Destination: connect the v6 instance and start a dry run

  1. Press Log in to Insites Console. Console opens in a new tab. Create a new, empty v6 instance there (how), come back to the tool and press Next.
  2. In Insites Console, open the new instance and its CLI tab. Press Get my token and copy the token.
  3. Back in the tool, give the v6 instance URL, paste the token into Console access token, and press Connect and check. The tool checks your role and that the token is for this instance. More on the token.
  4. What it holds shows what the new instance has already. A new one holds only the platform's own starting content.
  5. Choose Dry run and press Read the source.

A dry run reads both sides and reports exactly what a migration would do. Nothing is written anywhere, and it can become the real migration later without reading the site again. The tool reads the media library, the people and the shop through the REST API, and every page from the live site, loading each one in a browser to find the files its scripts fetch. A progress bar shows while it reads.

3. Transform: check where everything goes

The stage opens with Analyze, which reads the whole site, and Next opens once the read is done. Each step says first whether it needs a decision.

  • Pages and code: each published page and product page, with the address it keeps. A page made in Elementor, the block editor or another page builder is copied as the HTML it shows, and is no longer edited in the builder. The posts' collection page is listed here too: when the tool could not settle its layout, choose the proposed layout, static copies of each post's page, or neither. Posts as collections.
  • Databases: posts, and each other post type, as a table with a row per item, with its Advanced Custom Fields as columns; each taxonomy, the comments and the menus' links as tables of their own.
  • Assets: the media library, and the theme's and the plugins' stylesheets, scripts and images the pages load. Every one is copied unless you untick it.
  • Forms: every Contact Form 7, WPForms and Gravity Forms form, recreated in the Insites form builder with the table it saves to. A Contact Form 7 form's workflow email goes to the address its own settings sent to; type who the others go to. The autoresponder is made switched off for you to turn on later. For a plugin that keeps entries, add each form's CSV under it.
  • Users: every WordPress user, copied as a person with a CRM contact and no password. Nobody is given admin rights.
  • Ecommerce: the shop's products, variations, categories, orders and payments.
  • Redirects: the redirects from the Redirection plugin and the ones the tool found on the live site. Paste a Yoast SEO Premium or Rank Math export and press Use this list; a redirect in your list wins over one the tool found for the same address.
  • CRM, Events, Locator and Other: usually nothing to decide, and each step says what is copied.
  • Advanced: rules for an unusual migration, to change a name, fix a value, or leave a row out, each with a reason. They start closed, and most migrations need none of them.

On the last step, Advanced, press Continue to the plan. Every setting.

4. Plan: read what will run

  • Summary and decisions: the numbers, and anything that would stop the load, each with a button to fix it. Each fix asks why, and the reason goes in the report. More on resolving the plan.
  • What the load carries: the pages and the files.
  • Fixes: anything the tool can fix for you, shown line by line, or a note that there is nothing to do.
  • Changes and what is not copied: what changes on the way, and what is not copied.

Check three things before you go on:

  • The pages. Every published page and product, and every list the sitemap names, is copied. A password-protected page cannot be read, so it is named for you to rebuild, and so is a shortcode the old site showed as text.
  • The posts. Each post type is a table with a collection page. Where the posts sat at the site's root, they move under /posts/ and the plan lists a redirect from each old address.
  • The shop. Products, categories, orders and payments go into the Insites Ecommerce module, and every customer with an email becomes a CRM contact. WooCommerce's cart, checkout and account pages are replaced by the new cart and checkout.
  • What is left behind. Approved comments, and those waiting for approval, are copied into a Comments table; spam and the trash stay on WordPress. Every plugin the site had switched on is named, because no WordPress code runs on the new site. Shipping zones, tax rates, coupons and order emails are named, and the To do list says what to do.

When the plan reads right, press Run it for real on its last page. It uses this exact plan.

5. Load: confirm with the plan code

Confirm the load shows the plan's code. Type it into Plan code and press Load. The tool loads the shop, the people, the files and the pages. You can close the page: we email you when the load finishes, and again when the checks finish. If the load stops, the page says why in plain words, and it can carry on from where it stopped.

6. Verify: see what was checked

The checks start by themselves when the load finishes, and usually take a few minutes. These matter most for a WordPress site:

  • Records, read again from the source: every product, order and payment matches the shop as it is at that moment.
  • Pages say the same: each copied page says the same words as the WordPress page.
  • What pages load: no page loads a file from the old site.
  • Redirects: every redirect sends visitors to its page.

Verify is five steps. Result opens with two figures: the records copied, out of the records on the old site, and the items checked that passed, out of every item checked. Then the table of what was checked. Send to GitHub sends the new site's code to your repository, where GitHub is connected. Things that need you takes you through what failed, one thing at a time, each with one thing to do about all of it. Worth a look has the page photographs and the errors the new site logged, which do not decide the verdict. The Verification log holds every verification in full. Anything you must do yourself is on the To do list too. After you fix something, press Check again. The checks.

Then try the new site. Send a test from a form: it lands in the form's table, and the workflow email arrives. The form is in Forms in the instance's admin. Add a product to the cart on its page and open /cart. Checkout says Stripe is not set up until its keys are added, which the To do list covers.

7. Launch: the launch, in time order

Launch opens with a timeline of the launch and marks where you are. The jobs only a person can do, written for this site, sit in the step they are done in: Before cutover, Cutover or After cutover. Tick each one off as you go. The jobs most WordPress sites have, in that order:

  1. Open each form in the form builder, check who its workflow email goes to, read its autoresponder and switch it on.
  2. For a shop: connect it to the site's Stripe account, then set up shipping, taxes, coupons and order emails again.
  3. Go through the plugins the plan names and rebuild what still matters: anything a plugin did on the server stopped.
  4. Add the site's domains to the new instance in Insites Console, and point their DNS at it once editing has stopped and the final sync has run. Leave the email records alone.
  5. After cutover, send each person the new site's password reset link, and give the people who look after the site admin access.
  6. Keep the WordPress site and a full backup until the 14-day watch ends. Then delete the tool's user, which revokes its Application Password, and end the hosting.
  • Cutover: going live, in order. Stop editing in WordPress, run the final sync so the new site has the last changes, move the domain, and check the site on its domain. Copy first, then cut over.
  • Nightly sync: chosen when the load finishes, and changed under Before cutover. It keeps the new site in step with the old one every night until cutover.
  • Watch: for 14 days after cutover, every page and the log, every 6 hours, with a summary email a day.
  • Report: two PDFs, each kept in the tool as well as downloaded. Summary for your client is one or two pages for the site owner. The Technical report is the whole migration. The reports.
  • Close: when the new site has run cleanly, press Close the migration, type the old site's address, or its Insites name, which the dialog shows, and press Close the migration. The migration becomes a record, and the tool removes its copies of both keys. Until then, a load can be rolled back.

Last, in WordPress, delete the user made for the tool, and switch Wordfence's setting back if you changed it.