How a WPMove migration works

Two addresses, two application passwords. WPMove reads the source and writes to the target through the WordPress REST API — nothing to install, no FTP, no database export.

The migration pipeline

Everything runs on our servers, in a background queue that resumes on its own after a timeout. You can close the tab: an email tells you when it is done.

Source
Your current site

Read through its REST API. Nothing is changed on it.

GET /wp-json/wp/v2/…
wpmove.appBackground queue
  1. Countingwhat will move, per content type
  2. Contentposts, pages, custom post types, terms
  3. Mediafiles downloaded and re-uploaded, 5 at a timeAll plans, yearly quota
  4. Rewritelinks, images and block references
  5. Commentsthreads, dates and authorsOptional
Resumes after a timeoutPause at any timeEmail when done
Target
Your new site

Receives content and files through its REST API.

POST /wp-json/wp/v2/…

Your application passwords are stored encrypted and are only ever sent to your own two sites.

Five steps in the app

The migration screen walks you through the same five steps every time and saves your settings as you go — reload the page, nothing is lost. Save a pair of sites as a profile and it waits for you under My migrations.

  1. Sites

    Enter the source and the target, then test both connections. A connection that works is saved; a failure says which side and why.

  2. Content

    Tick the content types — with the number of items each one holds — or pick specific posts by title.

  3. Options

    Media, categories and tags, comments, authors, WooCommerce customers and orders, what to do with content already on the target, sync mode — and, if you want, the site’s own settings, menus, widgets, shop settings and theme design.

  4. Analysis

    Runs on its own when you get there: volumes, conflicts, what will not come across, and a table of every setting that will change on the target.

    On every plan
  5. Run

    Start, then follow each phase live with counters, elapsed time and the log.


What each phase does

1 · Content

Posts, pages and custom post types are read page by page and created on the target with their title, content, excerpt, status, date, featured image and page template. Categories and tags are recreated with their hierarchy and descriptions; reusable blocks are migrated and re-linked.

WooCommerce products are rebuilt through WooCommerce itself: product type, prices, stock, attributes, variations, gallery, downloadable files, linked products and reviews.

Content already on the target is skipped or updated — your choice.

2 · Media

Files are downloaded from the source and uploaded to the target five at a time, keeping their original date. A file that was already transferred is reused, never uploaded twice.

Media is included in every plan, with a yearly quota: on Free, 100 images inside your content (featured images are not counted); more on paid plans — topped up with credit packs.

3 · Rewrite

Once the files are on the target, every link, image and file URL pointing to the old site is rewritten to the new one, and image and reusable-block IDs are translated. Only the posts that actually change are updated.

4 · Comments

When “Import comments” is ticked, comments follow their posts with their threads and original dates — including those awaiting moderation, which stay that way. Commenters arrive as guests; spam and trash stay behind.

5 · Menus, widgets and site settings

When you ask for it, menus follow — navigation and classic menus, every link pointed at the pages just migrated — then widgets, into the target’s matching widget areas. Then the homepage, posts page, site icon and logo are set on the target — again pointing to the pages and files just migrated, never to the source’s numbers — and, if you like, the title, tagline, language, timezone and date formats. Each change is logged.


Options

Set them in the Options step. Each is remembered for your next migration.

Authors

Each post keeps its author. An author already on the target is found by email and used as is; otherwise the account is created there with the same role — and no email is sent to them. Administrators of the source become editors, unless you decide otherwise for this migration: the analysis names them first. Off by default.

WooCommerce customers

Customer accounts follow with their billing and shipping addresses. An account already on the target (same email) is left as it is; otherwise it is created there — no email is sent, and the customer chooses a password with “Lost your password?”. 25 accounts created a year on Free, 500 on Starter, 1,500 on Pro, unlimited on Unlimited — accounts already on the target don’t count; Starter and Pro can top up with customer packs. Off by default.

WooCommerce orders

Orders follow at their original dates — created, paid, completed — with their lines matched to your products by SKU (variations included), shipping, taxes, totals exactly as on the source, refunds, the notes your team wrote and the coupons they used. No email reaches your customers, stock and coupon counters don’t move, and no money is refunded again. The old order number is kept; running it again never duplicates an order. Needs the free Connector on the target — otherwise the migration does not start. Brings the customers along. 25 orders a year on Free, 1,000 on Starter, 5,000 on Pro, unlimited on Unlimited; Starter and Pro can top up with order packs. Off by default.

Update customers and orders already migrated

On a later run, orders already migrated are made identical to the source again — status, dates, lines, totals, coupons, refunds and notes added since — still with no email to your customers and no stock change. An order you changed on the target since is left as it is, never overwritten. Customer accounts created by WPMove get their addresses and name again; an account that already existed on the target is never changed. Updates don’t use your quota: when it is used up, they still run and only new orders and accounts wait. Needs version 2.1.32 or later of the free Connector on the target. Off by default.

Analyze before migrating

A report of what would move, what your plan allows and what could go wrong — addresses already taken on the target, page builders, hidden content types — before a single item is written.

Skip or replace

Content and media already on the target are skipped by default, so a migration can be re-run safely. Untick to update them instead.

Specific items

Search the source by title and migrate only the posts or pages you pick — with their media.

Sync mode

Only migrate what changed since your last successful migration to the same target. Ideal to keep a staging or backup site up to date.

Media library only

Transfer files without any post — the whole library or picked items, within the media quota.

Retry failed items

After a run, retry only what failed, in one click, without reprocessing the rest. All plans.

Saved profiles

Save a pair of sites with its options as a named profile, then run it again from My migrations — sync, retry what failed or analyze, in one click. Each pair keeps its own memory of what was already migrated. Passwords stay encrypted on our servers. One profile on the Free plan, as many as you like on paid plans.

Scheduled sync

On a paid plan, a saved profile syncs on its own, every day or once a week, in the time window you choose — set it from My migrations or at the Options step, nothing to install. Each run only carries what changed since the last successful one, with the profile’s options; content deleted on the source stays on the target. It never runs over your own work: while a migration is running or paused, or the migration screen holds unsaved changes, it waits and tries again every hour. You get an email only when something was migrated or failed; after three failed runs in a row, it pauses and tells you why.

Site settings

Homepage, posts page, site icon and logo, plus title, language, timezone and date formats if you like. Off by default: right for a copy of a site, not for a merge into an existing one. The analysis lists every change first. Never the site address, the admin email, the theme or plugins.

Shop settings

WooCommerce’s own settings — store address, currency and price formats, units, stock and review options, tax options, accounts, the look and sender name of shop emails, shop pages (cart, checkout, terms) found by their address — plus tax classes and rates, shipping classes, and shipping zones with their methods and costs. Only what differs is written, nothing on the target is deleted, and running it again changes nothing. Never payment methods (their settings hold your account keys), email addresses or WooCommerce’s internal options. Off by default; the analysis counts every change first.

Theme design

Between two sites using the same theme: global styles (palette, typography, background, additional CSS) and the templates and template parts you edited in the Site Editor — their navigation and reusable blocks pointed at the target’s — or, for a classic theme, the Customizer settings and additional CSS (the free Connector on both sites). Only what differs is written; a template only the target has edited stays as it is. Off by default; with a different theme on the target, the analysis tells you and nothing is copied.

Menus

Navigation and classic menus, every link pointed at the migrated content; a link to something not migrated stays visible as a plain link. Off by default. The target’s header shows the migrated menu only when it has no menu of its own — the analysis tells you which.

Widgets

Block widgets, core widgets and plugin widgets — those a plugin keeps closed to the REST API through the WPMove Connector on the target — in the same order, with their menus, images and links pointed at the migrated ones. Only into widget areas the target’s theme also has and that are still empty — never on top of widgets already there. Off by default. A block theme has no widget areas; the analysis says so.

Custom fields, Elementor and ACF

WordPress’ REST API only carries the fields a plugin has opened to it — most do not. The free Connector, installed on both sites, closes the gap — in one click from the Sites step, with an administrator account on each site.

Custom fields

Elementor layouts, ACF fields, SEO metadata and page templates travel with their post, images referenced by ACF included.

Quiet comments

Migrated comments are written directly, without moderation rules and without one email per comment to the post author.

Plugin widgets

With “Widgets” ticked, widgets whose plugin keeps them closed to the REST API are copied by the Connector on the target.

A deeper analysis

The report can then check addresses already taken on the target and page builders in use on the source.

Ready? It takes two minutes to set up.

Free plan: up to 25 items per migration, no card required.

WPMove
Privacy Overview

This website uses cookies to improve your experience. Strictly necessary cookies are stored in your browser as they are essential for WPMove to function. We also use third-party analytics cookies to understand how visitors use WPMove — only with your consent.