Skip to main content
Theme

Connectors

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 WordPressMovesWhat happens
PostsMovesA 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 showsMovesA Data table each, with a collection page. Items under the post type's archive keep their addresses.
Custom post types the REST API hidesPartlyTheir pages move from the live site; their fields cannot be read, and the plan names them. The export file reads them.
PagesMovesRead 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)PartlyThey move as the HTML they show, so they look the same, but they are no longer edited in the builder.
Categories and tagsMovesA Data table each, a row a term with its parent. Each item's row lists the names and the ids.
Custom taxonomiesMovesThe same as categories, and a names column on the item's table.
Blog index, category, tag and author archivesPartlyCopied as static pages at their address, as they looked on the day. They do not update. Every page of each author's list is copied for an author with published posts; an author with no posts gets a redirect to the blog page, or to the home page when the site has none. Every page of each category or tag list is copied. A page number the old site does not have answers 404, as on WordPress. A page number below any other page, such as /privacy-policy/page/2/ or a post's /page/2/, redirects to the page itself, as WordPress does.
A post type's archive pagePartlyBecomes 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 APIMovesA typed column each on the post type's table, in a Custom fields group.
Advanced Custom Fields in groups hidden from the REST APIPartlyNot 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 contentPartlyKept as JSON text in one column.
Featured imagesMovesCopied, and the row's image column names the copy.
Media libraryMovesEvery original copied; a smaller size only where a page uses it.
Approved comments and comments waiting for approvalMovesA Comments table, with the post, the reply and the person's name, email and website.
Spam and trashed commentsNot yetCounted and left on WordPress.
The comment formNot yetIt no longer sends: the Comments table keeps the comments to show again.
Classic menusMovesDrawn in every page as they were, and copied as a Menu items table in order.
Block theme navigationPartlyDrawn in every page as it was; it is not in the Menu items table.
WidgetsPartlyDrawn in every page as they were; a widget that works when a visitor asks does not.
Drafts, private, pending and scheduled itemsNot yetCounted and left on WordPress.
RevisionsNot yetNever read.
Password-protected pagesNot yetOnly the prompt is public: named for you to rebuild.
ShortcodesPartlyMoved as the HTML WordPress drew; one the old site showed as text is named.
Other languages (WPML, Polylang, TranslatePress)PartlyThe main language moves; the others are named and left.
A multisite networkPartlyOne site per migration.

People

On WordPressMovesWhat happens
UsersMovesA person with a CRM contact each, without a password.
PasswordsNot yetWordPress never gives one out: the To do list asks people to set one.
RolesNot yetNobody is given admin rights on the new site.

Search engines

On WordPressMovesWhat happens
A page's title, description and sharing tagsMovesCopied in the page's head as the SEO plugin wrote them.
Each post's own Yoast SEO title and descriptionMovesKept on the row and printed per post by the collection layout.
Each post's own Rank Math title and descriptionPartlyRank 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 postMovesThe canonical is the post's own new address; og:url and per-post structured data are left out rather than repeated.
Sitemap and robots.txtMovesInsites serves /sitemap.xml; robots.txt is copied and points to it.

Redirects

On WordPressMovesWhat happens
Redirection plugin rulesMovesRead through its REST API.
Redirection pattern and conditional rulesNot yetNamed and left: a redirect page answers one address.
Yoast SEO Premium redirectsMovesFrom its CSV export, read by its column names.
Rank Math redirectsMovesFrom its Apache or Nginx export: exact rules move, patterns are named.
Redirects WordPress makes when an address changesMovesFound by asking the live site about old addresses.

Forms

On WordPressMovesWhat happens
Contact Form 7 formsMovesRebuilt in the Insites form builder with a table and the workflow email to the form's own recipient.
Contact Form 7 entries (Flamingo)PartlyFrom Flamingo's CSV export, added on the Forms step.
WPForms formsMovesRebuilt in the form builder.
WPForms Pro entriesPartlyRead through a WPForms entries ability where the site offers one; otherwise from the export.
Gravity Forms formsMovesRebuilt in the form builder.
Gravity Forms entriesMovesRead through its REST API v2 when switched on; otherwise from the export.
File upload fieldsNot yetNamed and left off the rebuilt form.
Elementor Pro formsMovesRebuilt in the form builder, with the look and field names they had, popups included. The email goes to the form's own recipient with its own subject.
Elementor Pro submissionsMovesRead from Elementor Pro with the same Application Password. Submissions of an old form no copied page shows move too, into a table of their own, with no form rebuilt for them.
Other form plugins (Ninja Forms, Formidable)Not yetCounted; they stay as drawn and no longer send.

WooCommerce

On WordPressMovesWhat happens
WooCommerce products, variations and categoriesMovesInto the Insites Ecommerce module.
Orders and paymentsMovesKept in the Ecommerce module, linked to their contact.
Customers and guest buyersMovesCRM contacts.
Cart and checkoutPartlyA new cart and a Stripe checkout on the new site, once its keys are added.
Coupons, shipping, tax and order emailsNot yetNamed on the plan and the To do list.
Product reviewsNot yetCounted and left.
Subscriptions, memberships and bookingsNot yetPlugin data the tool does not read.

What ran on the server

On WordPressMovesWhat happens
What plugins did on the serverNot yetNamed, plugin by plugin, on the To do list.
Email sent through a mail pluginNot yetAn email sending job on the To do list.
Scheduled jobs (WP-Cron)Not yetNamed in the plugins job.
Theme and plugin PHPNot yetNo WordPress code runs on the new site: the pages move as WordPress drew them.

Connecting

On WordPressMovesWhat happens
An Application Password for an AdministratorMovesRefused for any other role, with why a password was refused.
A site with Plain permalinksMovesRead through ?rest_route=.
A site with no Application Passwords (a free WordPress.com site)PartlyConnects with its export file: no plugins, settings, redirects, shop or non-authors.