Console · Migration Tool
What moves from WordPress
Last updated 2 November 2026
What moves from WordPress
Every WordPress feature a site commonly uses, and whether the tool moves it to Insites. Use it before you start, to know what a site will need after the load. WordPress explains how the tool reads a site.
Moves The new site has it and behaves the same. Partly Some of it moves: the table says which part does not. Not yet The tool does not move it: the table says what to do.
Why the design moves whole. The tool reads each published page as a visitor gets it, with its theme's and its plugins' stylesheets, scripts, fonts and images. So a page looks the same whatever built it. What a plugin did on the server when a visitor asked, such as a search or a booking, does not happen on the new site.
Content
| On WordPress | Moves | What happens |
|---|---|---|
| Posts | Moves | A Data table, a row a post, with an Insites CMS collection page. Each post keeps its address where the permalinks allow; otherwise it moves under /posts with a 301 from the old one. |
| Custom post types the REST API shows | Moves | A Data table each, with a collection page. Items under the post type's archive keep their addresses. |
| Custom post types the REST API hides | Partly | Their pages move from the live site; their fields cannot be read, and the plan names them. The export file reads them. |
| Pages | Moves | Read from the live site at their own address, with their design and every file they load. |
| Pages made with a page builder (Elementor, Divi, WPBakery, the block editor) | Partly | They move as the HTML they show, so they look the same, but they are no longer edited in the builder. |
| Categories and tags | Moves | A Data table each, a row a term with its parent. Each item's row lists the names and the ids. |
| Custom taxonomies | Moves | The same as categories, and a names column on the item's table. |
| Blog index, category, tag and author archives | Partly | Copied as static pages at their address, as they looked on the day. They do not page or update. |
| A post type's archive page | Partly | Becomes the collection page's list at the same address, as it looked on the day: new items do not appear in it. |
| Advanced Custom Fields in groups shown in the REST API | Moves | A typed column each on the post type's table, in a Custom fields group. |
| Advanced Custom Fields in groups hidden from the REST API | Partly | Not readable through the REST API, and the plan says so; read from postmeta when the site is connected with its export file. |
| ACF groups, repeaters and flexible content | Partly | Kept as JSON text in one column. |
| Featured images | Moves | Copied, and the row's image column names the copy. |
| Media library | Moves | Every original copied; a smaller size only where a page uses it. |
| Approved comments and comments waiting for approval | Moves | A Comments table, with the post, the reply and the person's name, email and website. |
| Spam and trashed comments | Not yet | Counted and left on WordPress. |
| The comment form | Not yet | It no longer sends: the Comments table keeps the comments to show again. |
| Classic menus | Moves | Drawn in every page as they were, and copied as a Menu items table in order. |
| Block theme navigation | Partly | Drawn in every page as it was; it is not in the Menu items table. |
| Widgets | Partly | Drawn in every page as they were; a widget that works when a visitor asks does not. |
| Drafts, private, pending and scheduled items | Not yet | Counted and left on WordPress. |
| Revisions | Not yet | Never read. |
| Password-protected pages | Not yet | Only the prompt is public: named for you to rebuild. |
| Shortcodes | Partly | Moved as the HTML WordPress drew; one the old site showed as text is named. |
| Other languages (WPML, Polylang, TranslatePress) | Partly | The main language moves; the others are named and left. |
| A multisite network | Partly | One site per migration. |
People
| On WordPress | Moves | What happens |
|---|---|---|
| Users | Moves | A person with a CRM contact each, without a password. |
| Passwords | Not yet | WordPress never gives one out: the To do list asks people to set one. |
| Roles | Not yet | Nobody is given admin rights on the new site. |
Search engines
| On WordPress | Moves | What happens |
|---|---|---|
| A page's title, description and sharing tags | Moves | Copied in the page's head as the SEO plugin wrote them. |
| Each post's own Yoast SEO title and description | Moves | Kept on the row and printed per post by the collection layout. |
| Each post's own Rank Math title and description | Partly | Rank Math does not put them in the REST API: the collection layout prints the post's title and no description. |
| Canonical address, og:url and structured data per post | Moves | The canonical is the post's own new address; og:url and per-post structured data are left out rather than repeated. |
| Sitemap and robots.txt | Moves | Insites serves /sitemap.xml; robots.txt is copied and points to it. |
Redirects
| On WordPress | Moves | What happens |
|---|---|---|
| Redirection plugin rules | Moves | Read through its REST API. |
| Redirection pattern and conditional rules | Not yet | Named and left: a redirect page answers one address. |
| Yoast SEO Premium redirects | Moves | From its CSV export, read by its column names. |
| Rank Math redirects | Moves | From its Apache or Nginx export: exact rules move, patterns are named. |
| Redirects WordPress makes when an address changes | Moves | Found by asking the live site about old addresses. |
Forms
| On WordPress | Moves | What happens |
|---|---|---|
| Contact Form 7 forms | Moves | Rebuilt in the Insites form builder with a table and the workflow email to the form's own recipient. |
| Contact Form 7 entries (Flamingo) | Partly | From Flamingo's CSV export, added on the Forms step. |
| WPForms forms | Moves | Rebuilt in the form builder. |
| WPForms Pro entries | Partly | Read through a WPForms entries ability where the site offers one; otherwise from the export. |
| Gravity Forms forms | Moves | Rebuilt in the form builder. |
| Gravity Forms entries | Moves | Read through its REST API v2 when switched on; otherwise from the export. |
| File upload fields | Not yet | Named and left off the rebuilt form. |
| Other form plugins (Elementor, Ninja Forms, Formidable) | Not yet | Counted; they stay as drawn and no longer send. |
WooCommerce
| On WordPress | Moves | What happens |
|---|---|---|
| WooCommerce products, variations and categories | Moves | Into the Insites Ecommerce module. |
| Orders and payments | Moves | Kept in the Ecommerce module, linked to their contact. |
| Customers and guest buyers | Moves | CRM contacts. |
| Cart and checkout | Partly | A new cart and a Stripe checkout on the new site, once its keys are added. |
| Coupons, shipping, tax and order emails | Not yet | Named on the plan and the To do list. |
| Product reviews | Not yet | Counted and left. |
| Subscriptions, memberships and bookings | Not yet | Plugin data the tool does not read. |
What ran on the server
| On WordPress | Moves | What happens |
|---|---|---|
| What plugins did on the server | Not yet | Named, plugin by plugin, on the To do list. |
| Email sent through a mail plugin | Not yet | An email sending job on the To do list. |
| Scheduled jobs (WP-Cron) | Not yet | Named in the plugins job. |
| Theme and plugin PHP | Not yet | No WordPress code runs on the new site: the pages move as WordPress drew them. |
Connecting
| On WordPress | Moves | What happens |
|---|---|---|
| An Application Password for an Administrator | Moves | Refused for any other role, with why a password was refused. |
| A site with Plain permalinks | Moves | Read through ?rest_route=. |
| A site with no Application Passwords (a free WordPress.com site) | Partly | Connects with its export file: no plugins, settings, redirects, shop or non-authors. |