ElmsPark Guides

Guides › Migrating a WordPress site to PageMotor

PageMotor Migration · Updated November 2026

Migrating a WordPress site to PageMotor

The honest end-to-end walkthrough: what carries over cleanly, what needs rebuilding, and the surprises to plan for before you start.

For Thesis / Focus WordPress sites · 20-min read

The whole move, start to finish

  1. Export Steps 1 to 3. On your WordPress site. You finish with one export file, saved on your computer.
  2. Translate Steps 4 to 6. On your computer. You finish with the files PageMotor needs, and a page map to check them against.
  3. Import Steps 7 to 13. On your new PageMotor site. You finish with your design, your files and your content in PageMotor.
  4. Configure and test Steps 14 to 16. On your new PageMotor site. You finish with working forms and a site you have tested.
  5. Switch over Steps 17 and 18. At your host. You finish with the new site on your main address.
Your WordPress site stays live the whole time. You build the new site on a subdomain, and only Stage 5 changes what your visitors see.
Before you start

Is this guide the right one for your site?

  • Yes This guide covers Thesis/Focus WordPress sites, written in the Classic Editor, migrating to an existing PageMotor installation.
  • No It will not work for Divi, Gutenberg block-based sites, or WooCommerce shops: those have different export shapes and different importers. The "Beyond this guide" section, just before Troubleshooting, says what to do instead.

Prefer to watch it first?

The whole migration in 4 minutes 6 seconds, narrated, with captions. Recorded in August 2026: where the video and this page differ, follow this page. On PageMotor 0.11.5 the theme import now rebuilds your CSS by itself, so the "broken site" moment in the video is now a quick check.
Read a summary of the narration

The shape of it. The honest end-to-end walkthrough: what carries over cleanly, what needs rebuilding, and the surprises to plan for. Two to four hours in total. Transferring the images is the slowest single step.

Is this the right guide? It covers Thesis / Focus WordPress sites moving into an existing PageMotor installation. It will not work for Divi, Gutenberg block-based sites, or WooCommerce shops: different export shapes, different importers. The Beyond this guide section says what to do instead.

Three downloads, up front. The EP WP Exporter (a WordPress plugin, for your content and theme data), the PageMotor Migrator (a command-line translator into PageMotor's format), and the Focus Bridge Theme (which adds the Focus CSS hooks so most of your existing styles carry over). You will also want SFTP access and PHP 8 or newer on the machine running the translator.

Surprise one: the files are on you. The translator rewrites every image and file path to point at its new location, but it does not move the actual files. Allow 10 to 30 minutes for a small site, and longer for a large media library.

Surprise two: check the styling after import. On PageMotor 0.11.5, importing your theme data rebuilds your CSS, so the site should look right straight away. If it looks unstyled, look for a stylesheet warning in the admin, then save Design Options to rebuild it.

Surprise three: payment forms look right but do not work. Plain contact forms move across and work once you set them up in EP Email. Anything with a payment back-end, PDF generation, file upload or conditional logic shows in the right place, but the processing behind it does not come with it. If your site has order forms, read that troubleshooting entry before you start.

What migrates on its own. Pages at every nesting level with the hierarchy preserved, posts under a paginated blog listing, navigation menus (dropdowns included) and simple footer widgets. Your Focus skin CSS, custom CSS and design options. Featured images, Thesis YouTube embeds converted to lazy loading, and internal links rewritten to hierarchical paths.

What you rebuild by hand. Dynamic sidebar widgets (archives, categories, tag clouds) and any widget area other than the footer. Extra user accounts: every page is owned by your PageMotor admin. SEO titles and descriptions, image captions and comments. Gutenberg block content, WooCommerce products and orders, newsletter lists and multilingual content need a separate path.

Five stages. Export from WordPress. Translate the export. Import into PageMotor: back up the database first, install the bridge theme, import the theme data, check the styling, transfer the files. Configure and test. Then switch your main address over to the new site.

The guide has every step in order, the page map to review before importing, the payment-form troubleshooting to read before you start, and what to do for Divi, Gutenberg and WooCommerce.

Before you start

What you'll need before you start

  • WordPress admin access to install the exporter (your WordPress site needs WordPress 5.0 or later on PHP 7.4 or later).
  • A current PageMotor installation at the top of its domain, not in a subfolder (Migrator v2.4.7 is tested on PageMotor 0.11.5).
  • PHP 8.0 or later on the computer you'll run the translator from (run php -v in Terminal to check).
  • An SFTP client such as Cyberduck (free) or Transmit (Mac).

Check first Your web host must run PHP 8.2 or newer for PageMotor. That is separate from the PHP on your computer in Step 4.

In cPanel, open MultiPHP Manager and check the version next to every domain the site will use. That includes your main address, which the site moves to in Step 17.

The three downloads

Get all three before you begin.

You will also need some EP Suite plugins on your PageMotor site: EP Redirects before Step 13, and EP Email if your site has forms. Each plugin's documentation page says how to get it.

A helper, if you want one

Use this guide with any AI assistant

Download it as a prompt file, paste it into Claude, ChatGPT, Gemini or any LLM, and it will walk you through every step interactively.

Download as LLM prompt
Before you start

Three things to know before you start

These surprises catch out most first-time migrations. Reading them now saves you an hour of confusion later.

  • Surprise 1The files are on you

    The translator rewrites every image and file path in your content to point at the new location in PageMotor. It does not move the actual files. You will need your SFTP credentials and a client like Cyberduck or Transmit to copy them across yourself. Allow 10 to 30 minutes for a small site, and longer for a large media library. This is where many first migrations slow down.

  • Surprise 2Check the styling after import

    On PageMotor 0.11.5, importing your theme data rebuilds your stylesheet for you, so the site should look right straight away. If it looks unstyled, the CSS did not compile. Look for a red stylesheet warning in the admin first, then see Step 11. Older guides and the video describe a fully broken site after import: that was PageMotor before 0.11.

  • Surprise 3Payment forms look right but don't work

    Simple contact forms (name, email, message, phone) move across and work once you set them up in EP Email (Step 14). Anything with a payment back-end (Stripe, PayPal), PDF generation, file upload, or conditional logic will appear in the right place in PageMotor, but the processing behind it does not come with it. If your site has order forms, read the payment form troubleshooting entry before you start, not after.

Before you start

What moves across, and what does not

What migrates automatically

The translator converts all of this for you. Some items change shape on the way (featured images move into the page content, YouTube embeds become lazy-loading, and links use the new hierarchical paths). A few still need a step from you, as each card notes.

Pages and posts

  • Pages (all levels of nesting)Parent/child hierarchy preserved. Pages under your WordPress front page move to the top level (/home/team/ becomes /team/), with a redirect
  • Home pageCopied into the theme's Hero Content box. To change it later, edit that box in the theme Editor, not the Home page in your content list. If WordPress showed your latest posts as the home page, see what does not migrate
  • PostsNested under /blog/. This only lines up if your WordPress posts page is a top-level page with the slug blog, or you have no posts page. If yours is something else, such as /news/, change its slug to blog in WordPress before you export
  • Blog indexA fixed listing of the posts published at export time, paged in the browser. Thumbnails appear only if your Focus blog showed them. Posts you add later in PageMotor do not appear on it unless you add them by hand
  • Members-only content (MemberPress, LearnDash)Courses, lessons, downloads and membership products come in as drafts, listed in the page map. PageMotor does not carry the protection over, so protect them before you publish any. The members, courses, files and products themselves move separately: see Members, courses, downloads and bookings

Design and navigation

  • Navigation menusDropdowns included. They open on hover and keyboard focus
  • Footer widgets and menusText, custom HTML and menu widgets only. Links and images inside them are not rewritten, so fix those by hand. Other footer widgets, such as images or recent posts, are left out. On a Focus site, Focus's own footer menu and footer text box come across too (Migrator v2.4.7 and later). A copyright line with the current year is added only when there is no footer text box. Migrated with an earlier version? See the footer is a plain copyright line
  • Focus skin CSSCompiled CSS imported directly
  • Focus custom CSSIncluded in the compiled output
  • Focus design optionsColours, fonts, layout settings. Fonts and icons loaded from another service (Google Fonts, Adobe Fonts, Font Awesome) are not exported, so check them after import

Inside your content

  • Featured imagesPlaced inline at the top of the content. The files still need copying across (Step 12)
  • Focus CardsConverted to static HTML grids in your pages. A separate Cards export can also load them into the EP Cards plugin, but your pages keep the static grids until you swap in EP Cards shortcodes
  • YouTube embedsThesis [youtube] shortcodes become lazy-loading players with a thumbnail. Ordinary iframe embeds are kept as they are. A bare YouTube link on its own line stays as plain text, and [embed] shortcodes are hidden, so re-embed those by hand
  • Internal linksRewritten to hierarchical paths: /child/ becomes /parent/child/. Only exact matches are rewritten (see Step 6)
  • Contact form shortcodesGravity Forms, Contact Form 7 and WPForms shortcodes become EP Email form shortcodes. You create the matching forms in EP Email, and Gravity Forms names need checking first (Step 5 and Step 14)
  • BreadcrumbsAdded when the Thesis breadcrumbs box is installed on your WordPress site, even if you did not use it. Needs the EP Breadcrumbs plugin (Step 15)

What does not migrate automatically

Do these first, while WordPress is still in front of you

  • Password-protected pages and postsThe password does not carry over, so a protected page goes live and public. Find them in WordPress before you export and set them to private or draft
  • Scheduled and pending postsNot exported. Publish them first, or copy them across by hand
  • Redirects you set up in WordPress (a redirect plugin, or WordPress remembering a post's old address after you changed its slug)Not carried over. Before you start, list them from your redirect plugin, then add them to EP Redirects after Step 13
  • Email sign-up and opt-in boxes (Focus opt-in boxes, AWeber or Mailchimp forms)Not carried over, so the sign-up box is missing from the pages that showed it. Before you switch, note which pages had one, then add your email provider's sign-up form back by hand

Rebuild or re-enter these by hand afterwards

  • A home page that shows your latest postsNot supported. Your posts move to a new /blog/ page and the home page shows just your site name and tagline. Build a new home page by hand
  • Image captionsCaptioned images lose their caption box and alignment. The caption text stays as a plain line under the image, so tidy each one by hand. The page map counts them under "Shortcodes hidden"
  • Other WordPress shortcodes (galleries, sliders, plugin shortcodes)Turned into hidden notes in the page, closing tags included, so what they displayed is missing. The page map lists every one under "Shortcodes hidden". View the page source and search for shortcode: to find them, then rebuild that content
  • Words in square brackets, such as [sic] or Hello [first name]Kept as text from Migrator v2.4.5 on, and listed in the page map to check. Earlier versions hid them as shortcodes, so if you migrated with v2.4.4 or older, search your old site for square brackets and put any missing words back. A real shortcode with a one-word name, such as [year], now shows as text: delete or replace it
  • CommentsExported but not imported. Existing comment threads stay behind, so keep a copy of the export if you want them for reference
  • SEO titles, meta descriptions and noindex settings (Thesis's own SEO fields, Yoast, Rank Math, All in One SEO)Not carried over, so pages you had set to noindex become indexable. Re-enter them for your key pages in PageMotor, copying what your live site shows today, and set your favicon and analytics ID again
  • Dynamic sidebar widgetsArchives, categories, and tag clouds need rebuilding
  • Categories and tagsPosts keep no categories or tags in PageMotor. Old /category/ and /tag/ addresses, and their /page/2/ pages, are not redirected and show "not found". The quick fix is a redirect for each one to /blog/ in EP Redirects
  • Header, sidebar and other non-footer widget areasOnly footer widget areas migrate. The page map lists every widget area left behind, so you can rebuild its content by hand
  • Per-page templates (full width, landing page and similar)Every page uses the same PageMotor page template. The page map notes each page's old template so you can rebuild any that differ
  • Non-Focus skin layouts (BYOB and other Thesis 2 skins)The bridge builds the Focus layout. If your skin styles its own container IDs, the page map lists them and you rebuild those containers in the template editor
  • Multiple user accountsEvery page and post is owned by your first PageMotor user, usually the admin. Original author names survive only in the blog listing byline, if your Focus blog showed them. Recreate other users by hand

These need their own route

  • Gutenberg block contentClassic Editor only. Gutenberg needs a different migration path: see Beyond this guide
  • Booking set-up (Bookly)Services, packages, hours and booking questions move separately: see Booking
  • Newsletter subscriber listsExport from your email provider separately
  • WooCommerce products, orders, customersNeeds a separate migration: see Beyond this guide
  • Payment form back-endsStripe, PayPal, PDF generation and conditional logic do not migrate. Forms appear on the page, but the processing stops working
  • Multilingual content (WPML / Polylang)Not supported. The exporter has no language option, so every language comes out in one file, and translations that share an address can overwrite each other. Plan a separate path before you start
The migration Stage 1 of 5

Stage 1: Export from WordPress

  • Where you work On your WordPress site
  • What you do Steps 1 to 3
  • You finish with One export file, saved on your computer

Install the exporter plugin, pull everything out of WordPress in one file, then uninstall it. The exporter is read-only: it does not change your WordPress site in any way.

Step 1 Install the EP WP Exporter

Where: In your WordPress admin

Log in to your WordPress admin. Go to Plugins › Add Plugin › Upload Plugin (called Add New on older WordPress versions), upload ep-wp-exporter-1.4.1.zip, and activate it. That is all you need to do here.

Step 2 Run the export

Where: In your WordPress admin

Before you export, check two things in WordPress. Set any password-protected pages to private or draft, because the password does not carry over. And if your posts page is not called blog, change its slug to blog (see Posts in What migrates).

Go to Tools › EP WP Export. Make sure these boxes are ticked: Posts, Pages, Custom Post Types, Navigation Menus, Widgets & Sidebars, Media Manifest and Theme Settings. Custom Post Types starts unticked, so tick it. Leave Focus Cards unticked for this export. Click Export for PageMotor and save the JSON file that downloads. The filename includes your site name and today's date, so keep it somewhere you can find it.

This one file contains your content, menus, widgets, compiled CSS, and all your Focus skin settings. Comments are exported too, but they are not imported.

The export is a snapshot. Anything you change in WordPress after this moment is not in it. If you keep editing the old site while you build the new one, export again near the switch-over and re-run Steps 5 and 13. The content script is safe to re-run, but it overwrites any page text you have edited in PageMotor since.

Want your Focus Cards in the EP Cards plugin as well? Your pages always get the cards as static HTML. If you also want them managed in PageMotor's EP Cards plugin, run a second export: untick everything, tick only Focus Cards (for EP Cards Importer add-on). This produces a separate smaller JSON file for the EP Cards Importer. EP Cards and EP Cards Importer come with an EP Suite licence, and the EP Cards Importer page has the import steps.

Step 3 Clean up WordPress

Where: In your WordPress admin

Deactivate and delete the EP WP Exporter plugin. You are done with it.

The migration Stage 2 of 5

Stage 2: Translate

  • Where you work On your computer
  • What you do Steps 4 to 6
  • You finish with The files PageMotor needs, and a page map to check them against

The translator converts your WordPress export JSON into the files PageMotor needs. It runs from the command line and takes under a minute for most sites.

Never used Terminal? Let Claude Code run Steps 4 and 5 for you. Claude Code types the commands on your computer, runs the translator, edits the form mapping and helps with any errors. It comes with a paid Claude plan (Pro, Max or Ultra).

  1. Install the Claude desktop app from claude.com/download, sign in, and click the Code tab
  2. Put the translator zip and your export file in one folder, then start a session in that folder
  3. Set the permission selector under the prompt box to Manual, so it asks before each step
  4. Paste in this guide's prompt (the Download as LLM prompt button near the top of this page), then add: "Run Steps 4 and 5 for me. The translator zip and my export file are in this folder."

It still needs PHP on your computer, which Step 4 checks. Read the page map yourself in Step 6. The manual steps below are for anyone who prefers to run them by hand.

Step 4 Check your PHP version

Where: On your computer, in Terminal

The translator is a PHP command-line script. Open Terminal and run:

php -v

New to Terminal? Terminal is a program where you type commands instead of clicking. On a Mac, open Spotlight from the menu bar, type Terminal and click it, or open Applications › Utilities › Terminal. Type or paste a command, then press Return to run it.

Recent versions of macOS do not include PHP, so "command not found" is normal the first time. Installing it is a one-off job. Homebrew is the usual way on a Mac, and Claude Code can walk you through it.

On Windows, the translator has not been tested yet, so ask before you start (see Still stuck?).

You need PHP 8.0 or later. The translator has been tested on PHP 8.4 and 8.5. If you see "command not found", you will need to install PHP or add it to your PATH before continuing.

Step 5 Run the translator

Where: On your computer, in Terminal

Unzip pagemotor-migrator-v2.4.7.zip to a convenient location (your Downloads folder is fine).

Has your site got forms? Decide the form names first. Form names are written into your pages when the translator runs. Gravity Forms, Contact Form 7 and WPForms shortcodes all become [contact-form name="form-<ID>"], using the WordPress form ID. To give them real names, make a small JSON file of form ID to name, such as {"1": "contact", "4": "enquiry"}, and add --form-map=forms.json to the command below. If two form plugins share an ID, name the plugin in the key: "gravityforms:4", "cf7:4" or "wpforms:4". The page map lists every form it found.

Open Terminal and run:

# Navigate into the unzipped folder
cd ~/Downloads/pagemotor-migrator

# Run the translator against your export file
php translate.php /path/to/your-export.json --verbose

The translator auto-detects Focus sites and selects the Focus Bridge theme. With --verbose you see a short progress summary (page and post counts, blocks built, CSS and design options extracted), then the files it wrote and a numbered list of next steps. From Migrator v2.4.6 that list follows this guide's Steps 6 to 16, in the same order and numbering. Older versions printed a three-step list that left out the bridge theme, the files and the redirects, so if your output shows that, follow this guide instead.

"No such file or directory"? You need to be inside the unzipped pagemotor-migrator folder before running the translate command. Run ls translate.php. If you see the file listed, you are in the right place. If not, find where you unzipped it and cd there first.

When it finishes, three or four files appear in the folder you ran it from (the redirects file only when some addresses change). All their names start with your site name and the date, for example mysite-pagemotor-import-2026-10-23-141119.txt. If your site has custom post types other than Focus Cards and Modular Content, you also get one *-content-type-<type>/ folder for each: see Step 10.

  • *-pagemotor-import-<date>-<time>.txt Used in Step 9 Theme data file. Your blocks, templates, compiled CSS, design options, menus, and footer. This goes into PageMotor via the admin importer.
  • *-content.php Used in Step 13 Content migration script. Inserts all your pages and posts into the PageMotor database. Run it once while logged in as an administrator, then delete it immediately.
  • *-redirects.csv Used in Step 13 Redirects. A 301 for each old address the translator can work out from slugs: nested pages and posts (/about/, /my-post/), children of your old front page, and the front page itself. Only written when there are any. The content script adds them to EP Redirects for you if it is active. If your posts used date or category permalinks, such as /2024/05/my-post/, add those redirects yourself.
  • *-pagemap.md Used in Steps 6 and 16 Page map. Every page and post with its new PageMotor URL, content type and notes. Old WordPress addresses that change are listed in its Redirects section, not in the page table. It also lists widget areas and layout IDs that did not migrate, the forms it found, the shortcodes it hid, any words in square brackets it kept as text, your WordPress plugins with suggested PageMotor equivalents, and your first 20 media files. Use it as your testing checklist later.

Want to preview what the translator will do without writing any files? Add --dry-run to the command.

Step 6 Review the page map

Where: On your computer

Open the *-pagemap.md file before you import anything. Check that every page and post is accounted for, the new URLs look right, and there are no unexpected notes on any entries. This is also the document you will use as a testing checklist in Step 16.

One thing to expect: WordPress can serve any page at its slug directly (/about/), but PageMotor uses the full hierarchical path (/company/about/). The translator rewrites these in your content and menus, but only where the link is exactly the old address. Links with a #anchor or ?query, links in footer widgets and date-style post links are not rewritten, so search for them. The page map is the easiest place to spot-check this.

The migration Stage 3 of 5

Stage 3: Import into PageMotor

  • Where you work On your new PageMotor site
  • What you do Steps 7 to 13
  • You finish with Your design, your files and your content in PageMotor

This is the longest stage. Steps 9 and 13 write to the database, which is why a backup comes first. Steps 8 and 9 are order-dependent: Focus Bridge must be active before you import. Step 12 (files) takes the most clock time, though most of it is just waiting for files to copy.

The translator writes every link and file path from the root of your domain (for example /about/ and /user-content/uploads/...). So this guide assumes PageMotor is installed at the top of the domain, not in a subfolder such as example.com/site/.

Where to build it. Keep your WordPress site live while you work. Make a subdomain such as new.example.com in your hosting control panel, and install a fresh PageMotor there for the new site, not on top of one you already use. A subdomain counts as the top of its own domain. Stage 5 moves the finished site onto your main address.

Step 7 Back up your database

Where: In your hosting control panel. Skip on a fresh install

Skip check Fresh install with only PageMotor's starter content? There is nothing in it to lose yet, so you can skip this step and go on to Step 8.

Use phpMyAdmin, Adminer, or your hosting control panel to export a full SQL dump of your PageMotor database. Save it somewhere safe.

Importing into a site that already has content? The content script replaces your existing home page, and the text of any existing page with the same address (for example /about/). The design also changes the moment you activate Focus Bridge in Step 8. If the site is live, run the migration on a staging copy first.

Step 8 Install the Focus Bridge Theme

Where: In your PageMotor admin

  1. In PageMotor admin, go to Manage Themes
  2. Upload focus-bridge.zip
  3. Activate it

On a Mac? Upload focus-bridge.zip exactly as downloaded. If your Mac unpacked it and you zip the folder again, PageMotor says it is missing the required file theme.php, because the zip now starts with a hidden __MACOSX folder. The theme is one file, so you can skip the zip: in File Manager make a folder user-content/themes/focus-bridge, upload theme.php into it, and Focus Bridge appears in Manage Themes, ready to activate.

Focus Bridge is a minimal bridge theme. It adds the CSS class hooks (.focus and .mode-focus) your Focus skin expects, so most of your styles carry over unchanged. If your page map lists layout IDs not output by the bridge, those rules need adapting by hand.

Already migrated with Focus Bridge 1.2 or earlier? On PageMotor 0.11 and later, your blog posts still show on the site but cannot be edited: Content Types has no Post button. Replace user-content/themes/focus-bridge/theme.php with the one in the new zip to fix it. Nothing else changes.

Step 9 Import the theme data

Where: In your PageMotor admin

Focus Bridge must be the active theme before you import. The import file is tagged with the Focus Bridge theme class name. PageMotor will reject the file if a different theme is active. Make sure you completed Step 8 and Focus Bridge is your current active theme, not just installed, before continuing.

  1. Go to Admin › Theme Settings and click Manage Theme Data
  2. Click Import Theme Data
  3. Drop the .txt file from Step 5 into the box. Its name contains -pagemotor-import-

This imports your blocks, templates, menus, footer content, compiled CSS, and all your Focus design option values in one operation. PageMotor takes an automatic backup of your theme data first, then rebuilds your stylesheet.

Step 10 Install the Content Type plugins

Where: Over SFTP, then in your PageMotor admin. Only if generated

Skip check If the translator did not generate these folders, skip this step.

If the translator generated folders named *-content-type-<type>/ alongside the other output files, your WordPress site used custom post types (such as events or portfolio items) that need to be registered in PageMotor. There is one folder per type, because PageMotor registers exactly one content type per plugin. Focus Cards and Modular Content never need one, because the translator turns them into HTML in your pages.

  1. Using SFTP (you will be setting this up in Step 12 anyway), upload each *-content-type-<type>/ folder to user-content/plugins/ on your PageMotor server
  2. In PageMotor admin, go to Manage Plugins and activate each plugin whose name starts "Content Type:"
  3. Each type now has its own button under Content Types

Migrated with Translator v2.4.3 or earlier? You may have one combined *-content-types/ plugin. On PageMotor 0.11 and later it activates but registers nothing. Deactivate and delete it, re-run the translator with v2.4.4 or later, and install the per-type folders instead.

Step 11 Check the styles loaded

Where: On your new site, in your browser

Importing the theme data in Step 9 also rebuilt your stylesheet. Open the front end of your site and check it looks styled.

  1. If it looks right, move on to Step 12.
  2. If it looks unstyled, check the admin for a red notice saying the front-end theme stylesheet failed to compile, or could not be written to disk. See Troubleshooting for what each one means.
  3. To force a rebuild at any time, go to Admin › Theme Settings, click Set Design Options, then save without changing anything. Reload the front end with Shift held down so your browser does not show its cached copy.

Step 12 Transfer your files via SFTP

Where: In your SFTP client

The translator rewrites every /wp-content/uploads/ path in your content to point at the correct location on PageMotor. It does not move the actual files. That covers images, PDFs and any other uploaded files, so you need to copy all of them from your WordPress server to your PageMotor server yourself.

What you will need

  • SFTP credentials for your PageMotor server: hostname, username, and password or key. Find these in your hosting control panel (cPanel, Plesk) or your provider's welcome email. If you cannot find them, contact your hosting provider's support. Use SFTP, not plain FTP.
  • On a cPanel host (HostGator, Bluehost): SFTP takes your main cPanel username and password. An FTP account, named like you@yourdomain.com, cannot connect over SFTP.
  • An SFTP client: Cyberduck (free, Mac and Windows), FileZilla (free, all platforms), or Transmit (Mac).
  • Your WordPress uploads: either from your live WordPress server via a second SFTP connection, or from a local backup.

Where things live

On your WordPress server, your uploads are in wp-content/uploads/, organised in year/month subfolders like 2024/01/, 2024/02/.

On your PageMotor server, they go into user-content/uploads/wp-media/. You may need to create the wp-media subfolder if it does not exist yet.

Both sites in the same cPanel? You may not need an SFTP client. cPanel's File Manager can copy between folders on the server.

First create the wp-media folder inside your PageMotor site's user-content/uploads/.

Then open the WordPress site's wp-content/uploads folder and click Select All. Copy only lights up once items are selected.

Click Copy, enter your PageMotor folder followed by /user-content/uploads/wp-media, then click Copy File(s). Open wp-media to check the year folders are there.

How to transfer

  1. Connect to your PageMotor server in your SFTP client. Set the protocol to SFTP. The port is usually 22, but some shared hosts use another (HostGator shared hosting uses 2222, and SiteGround uses 18765 with an SSH key instead of a password). Your host's help pages give the right details.
  2. Navigate to user-content/uploads/ on the server. Create a wp-media folder here if one does not already exist.
  3. Upload everything in wp-content/uploads/ (images, PDFs and any other files) into user-content/uploads/wp-media/, keeping the same folder structure.

Keep the folder structure. A WordPress image at /wp-content/uploads/2024/01/photo.jpg should end up at /user-content/uploads/wp-media/2024/01/photo.jpg on PageMotor. Mirror the year/month subfolders exactly. If your WordPress site had all uploads in a flat folder (year/month organisation disabled), upload them directly into wp-media/ without subfolders. Links to files on other WordPress sites are rewritten to your server too, so check any you used.

Step 13 Run the content migration

Where: In your PageMotor admin, then over SFTP

  1. Install and activate EP Redirects 1.0.10 or later from Manage Plugins, then load any page of your site once so it creates its table. (In 1.0.9 and earlier, a redirect to an address with two ?query values lost the second one.) The script can then add your 301 redirects for you. If you skip this, the script lists the redirects instead and you add them later.
  2. Using the SFTP connection from Step 12, upload the *-content.php file to the PageMotor root directory: the top-level folder where you can see index.php and config.php.
  3. Log in to your PageMotor admin, then visit the file in the same browser, for example https://your-site.com/mysite-pagemotor-import-2026-10-23-141119-content.php. If you have SSH access, you can run php followed by the file name from that folder instead.
  4. The script runs through every page and post, printing Created or Updated for each one (or an ERROR line if one cannot be saved). It then adds your redirects to EP Redirects if that plugin is active. Otherwise it lists them, and you can paste the contents of the *-redirects.csv file into the Import box on the EP Redirects page. When it finishes, it shows a summary with totals.

Delete the script immediately after it finishes. The content migration script has direct database write access. It refuses anyone who is not logged in as an administrator, but it should still not sit on a live server. As soon as the summary screen appears, delete the file from your server via SFTP. Do not wait until later: do it now.

The script is safe to re-run. If you need to run it again after fixing something, re-upload and re-visit it. It finds existing pages by their address and refreshes their body text instead of creating duplicates, so any edits you made to that text since are overwritten. Apart from the home page, it does not change titles or status on a re-run, so fix those in the PageMotor editor. A page whose address has changed is created again as a new page. Remember to delete the script again afterwards.

The migration Stage 4 of 5

Stage 4: Configure and test

  • Where you work On your new PageMotor site
  • What you do Steps 14 to 16
  • You finish with Working forms and a site you have tested

Your content is in. This stage connects the working parts and checks that everything landed correctly.

Step 14 Set up contact forms

Where: In your PageMotor admin. Only if you have forms

Skip check If your site had no forms, skip this step.

If your WordPress site had forms, the translator has already converted the shortcodes to EP Email contact forms and placed them in the right pages. It writes [contact-form name="..."], an older name EP Email still accepts (the current one is [ep-contact-form]). To make them work:

  1. Install and activate EP Email on your PageMotor site
  2. Configure SMTP in Plugins › EP Email › Settings, under SMTP Connection. The Mailgun guide covers this in detail if you need it
  3. List the form names the translator used: search the translated *-content.php file for contact-form name= and note every name it finds
  4. Create each form. In EP Email's settings, open Contact Forms and add an entry to Form Definitions (JSON) for every name, with its fields and a recipient (or set a Default Recipient). Until a form is defined, its page shows "Contact form error: Form ... not found". The Download LLM Instructions button in the same section gives you a file an AI can use to write the JSON for you
  5. For forms with compound name or address fields, star ratings, confirm-email fields or section headings, also install EP Email Advanced Forms. Show-and-hide logic is built into EP Email itself, but you have to set it up again in the form definition, because your WordPress conditional rules are not carried over
  6. Many Gravity Forms? Their definitions, conditions and page breaks included, can be converted to EP Email's format by a script rather than by hand. It is not published yet, so ask in the forum (see Still stuck?)
  7. Multi-page forms arrive as one long form, because the page breaks are not carried over. EP Email Advanced Forms can split a form into steps again with its page field

Step 15 Add breadcrumbs

Where: In your PageMotor admin. Optional

Skip check If your site did not use breadcrumbs, skip this step.

If the Thesis breadcrumbs box was installed on your WordPress site, the translator has already placed an EP Breadcrumbs instance above the page title in the page content block. You just need the plugin itself.

EP Breadcrumbs (latest version) Used in this step. Outputs Schema.org BreadcrumbList JSON-LD. On PageMotor 0.11.5 you need version 1.3.6 or later, or breadcrumbs on nested pages show only Home and the page itself.

  1. Upload via Manage Plugins and activate
  2. Breadcrumbs appear automatically on every page and blog post that uses the imported page template. The home page, the blog index and the 404 page do not get them
  3. Optionally set the Default Home Text and Default Separator in Plugins › EP Breadcrumbs › Settings, under Defaults. A single instance can override both in the theme Editor

EP Breadcrumbs uses the same CSS class names as Focus breadcrumbs (.crumbs, .crumbs-crumb, .crumbs-sep), so your existing breadcrumb styles carry over unchanged.

Step 16 Review and test

Where: On your new site, in your browser

Open the page map (*-pagemap.md) and use it as your testing checklist. Walk through the site and verify:

  • All pages load and display correctly, with the right layout and styles
  • Navigation menus work and link to the right URLs
  • Internal links resolve correctly (check a few from deep pages back to shallow ones)
  • Old WordPress addresses redirect to their new pages
  • Featured images display at the top of content, and linked PDFs and downloads open
  • Footer matches your WordPress site, and its links point at the new site
  • Contact forms submit and you receive the emails
  • Blog index shows your posts and pagination works
  • Individual blog posts display correctly (title and content: post pages show no date, and dates appear only on the blog index if your Focus byline showed them)
  • Custom CSS overrides are working

Testing several forms in a row? EP Email accepts one form from the same visitor every five minutes, across all your forms, so a second test straight after the first says "Please wait a few minutes before submitting again." Wait five minutes between tests, or switch off Enable Rate Limiting in EP Email's Contact Forms settings while you test and switch it back on afterwards. If even the first form of the day is refused, see Troubleshooting.

What success looks like. Your PageMotor site should look like the WordPress version, with the same colours, fonts, layout and content. The exceptions are the items in the "What does not migrate automatically" list and anything your page map flags, which you rebuild by hand. The URLs will be hierarchical now (for example /parent/child/ instead of just /child/).

The migration Stage 5 of 5

Stage 5: Switch over

  • Where you work At your host
  • What you do Steps 17 and 18
  • You finish with The new site on your main address

Until now your WordPress site has carried on as normal on your main address, and the new site has lived on its subdomain. This stage puts the new site on your main address.

PageMotor works out its own address from each visit, and the translator wrote your links as paths such as /about/. So nothing inside the site needs rewriting: you change where your main address points, then tidy a few small things.

Members, courses, downloads or bookings? Move them before you switch, while nobody can reach the new site. See Members, courses, downloads and bookings below.

Step 17 Move the site onto your main address

Where: In your hosting control panel

Before you switch

  1. Back up both sites. Use your host's backup tool, or download the WordPress files and export both databases. On cPanel, read the note on disk space below first.
  2. Find any link that names the subdomain. Links the translator wrote, and images you uploaded in PageMotor, are paths from the root, so they move as they are. A link typed out in full while you built the site, such as https://new.example.com/about/, does not. In phpMyAdmin, open your PageMotor database, choose Search, enter your subdomain, select all tables and press Go. Change each link you find to the path alone, such as /about/.
  3. The search may also find PageMotor's two built-in "page not found" pages, which name the address the site was first opened at. On the Focus Bridge design that link never shows, so you can leave them.
  4. Stop hiding the new site. If you ticked Staging Mode in Site Settings, or set pages to noindex while you built it, undo that now.

Disk space A cPanel full backup is saved in your home folder first, so it counts against your disk space. Over the limit, a backup can fail and the server cannot save new files.

Old backup files in your home folder go inside the new one too, so it grows. Download any you want to keep, then delete them before you start.

Download the new backup and check its size on your computer. Safari shows a file ending in .download until it has finished.

Then delete the server copy in File Manager and click Empty Trash. Deleted files take up space until you do.

If both sites are with the same host

This is the usual case when you made the subdomain in the same control panel.

  1. Match the PHP version first. In cPanel's MultiPHP Manager, set your main domain to a definite version, 8.2 or newer, such as PHP 8.3. Avoid "inherit": it takes the server's default, which can be older. Your WordPress site may have used an older PHP, and on PHP 7 PageMotor shows only a blank page. See a blank page after the switch.
  2. In File Manager, turn on Show Hidden Files, so the .htaccess files are included.
  3. Move the WordPress files out of your main domain's folder (usually public_html) into a new folder outside it, such as old-wordpress in your home folder. If your subdomain's folder sits inside public_html, leave that one where it is.
  4. Copy everything from your subdomain's folder into the main folder, including PageMotor's .htaccess. Your config.php comes too, unchanged, because the site keeps the same database.
  5. Visit your main address. Sign in to the admin again there: a sign-in belongs to the address you used it on.

If the new site is with a different host

  1. At whoever runs your domain's DNS, point the domain's A record, and its www record, at the new host. Leave the email (MX) records as they are, and delete any AAAA record that still points at the old host.
  2. Make sure the new host serves your main domain from the PageMotor folder, on PHP 8.2 or newer, and issue its HTTPS certificate once the DNS change has reached it.
  3. DNS changes can take a few hours to reach everyone, so allow for that before you judge the result.

Step 18 Check it after the switch

Where: On your main address, in your browser

  1. Refresh two files PageMotor wrote for the old address. robots.txt and llms.txt in the site's folder still name the address it was first opened at, and PageMotor does not rewrite them on its own. Once your main address loads over HTTPS, delete both. The next visit writes fresh copies, so open /robots.txt and check its Sitemap line names your main domain.
  2. Send every visitor to HTTPS. In cPanel's Domains page, switch on Force HTTPS Redirect for your main domain. Then open its http:// address in a private window: it should change to https://.
  3. A normal browser window can jump to https from its history, which hides the result. That is why the test uses a private window.
  4. Switch greyed out? See the HTTPS switch is greyed out. It covers addon domains, and a four-line fix in .htaccess when cPanel's switch cannot be used.
  5. Try the old addresses. Open a few from your *-redirects.csv and a few old blog posts. Each should land on its new page.
  6. Walk through the Step 16 list once more, on your main address.
  7. Retire the subdomain. If you copied the files, the subdomain still runs the same site from the same database, at a second address. Delete the PageMotor files from the subdomain's folder, then remove the subdomain in your control panel, or redirect it to your main address.
  8. On cPanel, first note the subdomain's folder in Domains, and check it is not your main domain's folder. Then click Manage on the subdomain's row and Remove Domain.
  9. Removing it only takes away its settings and DNS: cPanel keeps the folder. Delete that folder in File Manager, check your main address still loads, and only then click Empty Trash.
  10. If your domain has a wildcard DNS record (*.yourdomain.com), the old subdomain name will then point wherever that record does.
  11. Reconnect Claude. A Claude connector belongs to the address you added it with, so the subdomain's one stops working. Remove it, then add your main address followed by /mcp/ and sign in with your admin login there.
  12. Check for a typed-in year. If your footer says something like "Copyright 2004-2025", replace the last year with [current-year]. That shortcode is built into PageMotor and shows the current year by itself.
  13. Keep the WordPress backup for a few weeks, until you are sure nothing is missing. An old-wordpress folder is the quickest place to copy back a missing file or image.
  14. Once you are sure, delete it. It counts against your disk space.
  15. Tidy the old hosting account. Old sites left on a shared host can hold malware that puts your new site at risk. See old sites and infected files.
  16. If you use Google Search Console, submit your main address's /sitemap.xml there.
If your site has more Only for MemberPress or Bookly sites

Members, courses, downloads and bookings

If your WordPress site ran MemberPress or Bookly, the translator brings their pages across as drafts, but not the data behind them. Your members, what each of them can open, your courses, your download files, what you sell and how people book all stay behind. This section moves each of them.

Each route here was worked through on a real site's move (MemberPress, MemberPress Courses, MemberPress Downloads and Bookly) before it went into this guide. Do it after Step 13, while nobody can reach the new site yet. Go in this order: members first, because courses, downloads and products all open by membership level. Skip any part your site did not use.

These are not one-click imports. Most steps read data out of your WordPress database and hand it to an action of a PageMotor plugin. That is easiest with an AI assistant that can see both: a copy of your WordPress database, and your PageMotor site (see Connecting Claude from this host). Every import action below is a dry run unless you say otherwise. It shows you row by row what it would do, and changes nothing until you run it again for real.

Read from a copy, test with made-up addresses. Take the data from a copy of your WordPress database, never the live one. Your PageMotor site sends real email, so make your test accounts with made-up addresses until you go live. LearnDash, WooCommerce Memberships and other membership or booking plugins are not covered here: ask before you start (see Still stuck?).

Part 1 Members and what they can open

Part 1 of 5

MemberPress members and their memberships move to EP Membership 0.8.0 or later, with its import-grants action. Full detail: Importing members.

  1. In EP Membership's settings, create one level for each kind of access your memberships gave, with a short slug such as toolkit or course-a. If a member can hold several at once (a course and a coaching group, say), set How Levels Work so each level stands on its own
  2. List one row per member for each membership still in force: email, name, level slug, and end date (blank when it never ends). MemberPress keeps these in its transactions table (wp_mepr_transactions): take the complete and confirmed ones, and match each MemberPress product to one of your levels
  3. Add each member's WordPress password hash (user_pass in wp_users) as legacy_hash. Members then sign in with the password they already know, and PageMotor swaps it for its own secure copy the first time they do
  4. Leave out your own account and any staff. The import refuses to touch staff accounts anyway
  5. Ask your assistant to run import-grants with the rows, or with a CSV. Read the dry-run report, then run it for real. It takes up to 1,000 rows a run, emails nobody, and changes nothing if you run it twice. A membership whose end date has passed is recorded but opens nothing
  6. Anyone without a password hash can be sent a "choose your password" email with send-set-password, when you are ready to tell them and not before
  7. Make a log-in page with [ep-login-form] at /login/ and an account page with [ep-member-dashboard], then set After Login Redirect to the account page
  8. Lock every members-only page that came across as a draft before you publish it: choose its level in the page's Membership box (with levels that stand on their own, use Or any of these levels)

To test, make one log-in per level with a made-up address. Sign in as each one, and check it reaches its own pages and is kept out of the others. Test over HTTPS: signing in does not work over plain http://, because the sign-in cookie is secure-only.

Part 2 Courses

Part 2 of 5

MemberPress Courses move to EP Courses 0.7.0 or later, one course at a time, with its import-course action. Each course can open to a membership level, so it needs EP Membership 0.8.0 too.

  1. For each course, list its sections in order (MemberPress keeps them in wp_mpcs_sections, sorted by section_order), then each section's lessons in order (each lesson's _mpcs_lesson_section_id and _mpcs_lesson_lesson_order)
  2. Take each lesson's text as visitors see it, run through WordPress's content filters, not the raw editor text. Strip MemberPress's own shortcodes. Swap any form shortcode for a placeholder before you run the filters, because WordPress curls the quotes inside it, then turn it into the matching EP Email form (Step 14)
  3. Keep words in square brackets as text by writing the opening bracket as &#91;, so nothing reads them as shortcodes
  4. Run import-course for each course. Give the course, every section and every lesson its WordPress id as legacy_id, so a second run updates the course instead of making a copy. Put the level or levels that open it in member_levels. Read the dry run, then run it for real. A new course stays a draft until you publish it
  5. Make the page courses open on: slug course-viewer, with [ep-course-viewer] as its content
  6. Add redirects in EP Redirects: each old /courses/<course>/ to /course-viewer/?course=<course>, and each /courses/<course>/lessons/<lesson>/ to /course-viewer/?course=<course>&lesson=<n>, where n is the lesson's place in the whole course, counting from 1. You need EP Redirects 1.0.10 or later: earlier versions mangled the &, so every old lesson link opened lesson 1

To carry over which lessons each member had finished, EP Courses has a separate import-progress action. Test by opening a lesson as a member who holds the course's level, and again as one who does not.

Part 3 Member downloads

Part 3 of 5

MemberPress Downloads has no matching plugin. PageMotor's own protected uploads do the job, with the Members Only documents in EP Membership.

  1. Copy the files from wp-content/uploads/mpdl/ on your old server
  2. Create a Members Only document for each group of files. It can stay a draft: it only owns the files
  3. Put each file in PageMotor's protected uploads, in the folder named after that document's id (user-content/uploads/protected/downloads/<document id>/), under a random name nobody can guess. There is no upload button for this yet, so it is a job on the server for your assistant or your developer
  4. Link each file as /?download= followed by its path, URL-encoded. PageMotor hands the file only to someone allowed to open the document that owns it, and answers "not found" to everyone else
  5. Every file opens for any member who meets the Members Only Document Level setting, which is one setting for the whole site. To keep each level's files apart, list them on separate pages, each locked to its level, the way MemberPress's file categories did
  6. Redirect every old /mp-files/<file>/ address to its new link, and each /file-category/<category>/ to its list page

To test, open a download link signed out (it should say not found), then signed in as a member (the real file should arrive).

Part 4 What you sell

Part 4 of 5

MemberPress products move to EP Ecommerce membership products, paid through EP Ecommerce Stripe.

  1. Switch on Purchase Grants in EP Membership, so a purchase gives the buyer the level
  2. Create one membership product for each MemberPress product, with the same name, price (_mepr_product_price) and currency. Set membership_level to the level it gives, and how long it lasts in days to match MemberPress's expiry setting
  3. Make a checkout page for each one: the product's sales words from WordPress, then [ep-checkout product="<slug>"]. Redirect the old /register/<product>/ address to it
  4. Set up your Stripe keys and webhook as the EP Ecommerce Stripe page describes, including the charge.refunded event. If your new site sits behind a sign-in screen while you test, Stripe cannot reach it: give the webhook a way in that lets through only a POST to /?ep_ecommerce_stripe_webhook=1
  5. In Stripe's test mode, buy each kind of product with Stripe's test card (4242 4242 4242 4242). Check the buyer gets the level, refund it, and check the level goes. Only then switch to your live keys

Recurring MemberPress subscriptions do not move this way. Decide how your current subscribers keep paying, or when their billing stops, before you switch WordPress off.

Part 5 Booking

Part 5 of 5

Bookly moves to EP Booking 2.10.0 or later. This moves your set-up, not your appointments: past bookings and Bookly's customer list stay behind, so finish or re-book upcoming appointments by hand. Set EP Booking's Business Timezone before anything else.

  1. Services: copy each one's name, length, price and the gap after it from Bookly's services (wp_bookly_services). Bookly's gap after is EP Booking's buffer after. A service people can only book from a package becomes package-only
  2. Packages: copy each package's number of sessions and how long it lasts, on the session it is for (Bookly links them in wp_bookly_sub_services). To bring across customers who still have sessions left, use import-packages
  3. Hours: set the weekly hours, leaving breaks free, and set Time slot interval to match Bookly's time slot length
  4. Where a Bookly service had its own times, questions or emails, give that service its own rules with set-service-rules. It replaces the service's rules, so read them from list-services first
  5. Own times: list the service's windows with the mode instead, so they replace the weekly hours for that service. Each window must hold the whole appointment. Set step for the minutes between its start times
  6. Questions: copy Bookly's custom fields and their conditions. A question can depend on just one answer, so a question Bookly showed for "A or B" goes in twice, once for each answer
  7. Emails: the service can have its own confirmation and reminder wording, and follow-up emails after the appointment. {customer_first_name} works in every booking email. Use {reschedule_url} only if customer rescheduling is switched on, because otherwise it is empty

To test, book as a visitor set to another time zone, and check the times offered, the questions and the confirmation screen. Then delete the test booking. Video links (EP Video, or EP Booking Zoom with your own Zoom app), your outside calendar's busy times and payment for paid sessions each need setting up on their own.

If your site has more

Beyond this guide

This guide is built around one specific path: Thesis/Focus WordPress → existing PageMotor installation, preserving the Focus design. If your situation is different, here is what to do in each case.

Divi or Gutenberg site There is no public converter for these yet. The translator reads a Divi export, but Divi Builder modules do not convert: images and buttons inside them are dropped, and the module tags themselves become hidden notes (from v2.4.5, closing tags such as [/et_pb_text] too). The translator is built and tested for Classic Editor content only. Expect to rebuild those pages, and ask before you start (see Still stuck? below).
No PageMotor install yet Set up PageMotor first. For a VPS, follow PageMotor on a VPS with CloudPanel. On shared hosting, follow the guide for your host, such as Installing PageMotor on Bluehost or Installing PageMotor on SiteGround. Then come back here.
Design refresh instead of preserving the Focus look Skip Steps 8, 9 and 11, because the theme import file only works with Focus Bridge active. Keep Attention, PageMotor's default theme, and run Steps 10, 12 and 13 to bring in your content and files. Your menus, footer and blog index layout come only with the import you skipped, so rebuild them in your new design, and give the /blog/ page a template there. To turn an HTML/CSS design into a theme, connect Claude to your site and ask it to follow PageMotor's own theme import guide (pagemotor://docs/theme-import).
WooCommerce shop Products, orders and customer accounts need a separate migration, and the translator does not handle them. The right approach depends on whether you will keep taking orders or only need to archive the data, so ask before you start (see Still stuck? below) and say how big your shop is.

Not installed yet? If you are setting up PageMotor for the first time before migrating to it, start with Installing PageMotor on Bluehost (or SiteGround), then come back here.

If your site has more

Connecting Claude from this host

PageMotor speaks MCP natively, so once the migration has settled you can connect Claude Code or Claude.ai to the new site and let Claude build pages, manage content and run plugins for you. The connection asks a little more of a host than serving pages does. The Authorization header must reach PHP intact. PageMotor must see the request as HTTPS, and must be allowed to answer its dynamic /.well-known/ routes itself. Nothing in front of PageMotor (a proxy, a password gate or a rewrite rule) may redirect Claude's POST to /mcp/, and no older MCP bridge plugin may intercept the requests. On PageMotor 0.10 only, browser sign-in also needs PHP's timezone at or behind UTC. On 0.11 and later, leave the timezone alone.

You do not need to test any of that by hand. Install EP Host Check and read its MCP / Claude connection rows. Since v1.3.0 its six checks cover all of this from your admin panel, with no working Claude connection needed, and each comes with a plain fix. If a row fails, or the connection misbehaves anyway, the MCP troubleshooting guide has the exact diagnostic and fix for every verified cause.

Help

Troubleshooting

Open these only if you hit them.

The translator and the content script

Terminal says "no such file or directory" when running translate.php

You need to be inside the unzipped pagemotor-migrator folder before running the command. Run ls translate.php. If the file is listed, you are in the right place. If not, find where you unzipped the file and cd there first.

Content migration script shows an error or a blank page

If it says "Place this file in your PageMotor root directory", move it to the folder where index.php and config.php live.

If it says "Forbidden", log in to PageMotor as an administrator in the same browser, then reload the script.

If the page is completely blank, PHP stopped before the script could print anything. Run it over SSH from the PageMotor folder (php followed by the file name) to see the error, or check your host's PHP error log.

Content migration script times out on a large site

Sites with hundreds of pages can hit PHP's time limit in a browser. The easiest fix is to run it over SSH from the PageMotor folder, where there is no time limit. In a browser, add set_time_limit(0); on the line after the opening <?php, or ask your host to raise max_execution_time.

It is safe to run again after a timeout. Pages that already exist have their body text updated from the export, so any edits you made to them since are overwritten. Missing pages are created.

Getting in and importing

Import says "does not apply to the current Theme"

The import file is tagged with a theme class name, and PageMotor only accepts it if the active theme matches exactly. Two things to check. (1) Is Focus Bridge the active theme, not just installed? Go to Manage Themes and confirm it is activated. (2) Does the class name match? Open your *-pagemotor-import-*.txt file in a text editor. Near the top you will see "theme": "Focus_Bridge". That value must match the Class: line in Focus Bridge's theme.php exactly, including capitals. If it does not, change the value in the import file to match.

Admin login keeps redirecting to the home page

PageMotor only lets a user into the admin if their user type is administrator. The type is stored in the user_options table, as one row named PM_Users that holds JSON. If that row is missing, login works but every /admin/ address sends you to the home page. If you created the user by hand, run this once in your hosting control panel's SQL tool:

INSERT INTO pm_user_options (user_id, name, value)
VALUES (<user-id>, 'PM_Users', '{"type":"administrator"}');

Replace <user-id> with the numeric ID of the user, and pm_ with your table prefix if you changed it. If a PM_Users row already exists for that user, edit its JSON to include "type":"administrator" instead of adding a second row. A plain row named type is ignored on PageMotor 0.10 and later.

The migrator never creates or changes users. Your admin account comes from the PageMotor installer, so this fix is only needed if you created a user by hand.

I do not know my SFTP credentials

Check your hosting provider's control panel: look for "FTP Accounts" or "SFTP Access". On IONOS it is under Hosting › SFTP & SSH. On Bluehost and HostGator, SFTP uses your main cPanel username and password, not an FTP account: an FTP account (named like you@yourdomain.com) only connects over plain FTP on port 21. HostGator shared plans use port 2222 for SFTP, not 22. SiteGround uses Site Tools, not cPanel: SFTP there needs an SSH key from Site Tools › Devs › SSH Keys Manager, and uses port 18765. If you cannot find them, ask your host's support team. They can reset or provide credentials in a few minutes.

The new site looks wrong

Every page is blank after moving to the main address

Your main domain is probably set to an older PHP than the subdomain was. PageMotor hides its errors from visitors, so all you see is a blank page.

Your host's error log will show a line like PHP Parse error: syntax error, unexpected ':', expecting ')' in .../lib/content.php. That is PHP 7, which cannot read PageMotor's code.

In cPanel's MultiPHP Manager, tick your main domain only, choose PHP 8.2 or newer, and click Apply. Leave every other domain as it is.

cPanel may warn that you cannot use that screen to change the domain back to its original version. That is expected, so click Apply in that box too.

Why 8.2: PageMotor 0.11.5 bundles code for its CSS editor that refuses anything older than PHP 8.2.

The Force HTTPS Redirect switch is greyed out

cPanel says addon domains take this setting from a subdomain it made for them. Click the gear icon, then Show Associated Domains, to see that row.

If that row's switch is off too, cPanel has no certificate for that subdomain. One cause is your main cPanel domain's DNS being with another company. Your own domain's certificate is unaffected, so add the redirect by hand.

In File Manager, open your site's folder, turn on Show Hidden Files, and edit .htaccess. Click just before # BEGIN PageMotor on line 1, press Return twice, then paste these four lines on line 1, with your own domain in the last one:

RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} ^www\. [NC]
RewriteRule ^ https://example.com%{REQUEST_URI} [R=301,L]

Keep them above PageMotor's block. PageMotor only edits what sits between # BEGIN PageMotor and # END PageMotor. Leave cPanel's PHP lines at the bottom as they are.

These lines also send www. to your bare domain. Test in a private window: the http:// and www. addresses should land on https:// and your bare domain. If you see "too many redirects", delete the four lines.

cPanel says you are over your disk quota

Over the quota, the server cannot save new files. Copying the new site in, or making a backup, can fail partway.

A full backup saved to your home folder can be the cause. Once it is on your computer, delete it in File Manager and click Empty Trash.

Old backups and zip files in your home folder count too. cPanel's Disk Usage page lists the biggest folders.

Pages look completely unstyled: no layout, no colours, just plain text

On PageMotor 0.11.5 the theme import already rebuilds your stylesheet, so first look for a red warning in the admin.

"The Front-end theme stylesheet failed to compile" means the CSS did not build. Check for empty fields in your Design Options (Admin › Theme Settings › Set Design Options) and for errors in your custom CSS, then save.

"Could not be written to disk" means PHP cannot write to the theme folder, so ask your host to fix the folder permissions.

If there is no warning, open your Design Options and save without changing anything, then reload the page with Shift held down so your browser does not show its cached copy.

One cause the translator now removes: a line in your WordPress custom CSS that sits outside any { }, such as a stray --accent-colour: #f16334;. Browsers skip it, but PageMotor refuses the whole stylesheet over it. Migrator v2.4.7 and later drop such lines, so translating again with the current version fixes it.

Every blog post is a blank (or all-black) page, while pages look fine

Your posts have no template. Sites migrated with Migrator v2.4.6 or earlier onto Focus Bridge 1.3 have this; v2.4.7 and later set the post template for you. To repair a site that is already migrated, give posts the same layout as your pages:

  1. Go to Admin › Theme Settings and click Launch Theme Editor.
  2. Click the yellow template name button at the top left (it says Home). A dark panel opens.
  3. Under Core Templates, click Post.
  4. Click the yellow button again (it now says Post).
  5. Under Copy from Template, choose Page, then click Copy Template.
  6. Click OK when it asks if you are sure.

There is nothing else to save. Reload one of your posts and it shows its title and content.

The site name in the header is small, plain or hard to see (Focus sites)

Focus styles the name as #site_title, but PageMotor prints it as #site-title, so the styling misses it. Migrator v2.4.7 and later style both. On a site migrated earlier, find the #site_title rules in your old Focus CSS, then go to Admin › Theme Settings › Edit Custom CSS, paste each rule at the bottom with the underscore changed to a hyphen, and click Save Custom CSS. For example:

#site-title {
  font-family: Georgia, "Times New Roman", Times, serif;
  font-size: 47px;
  font-weight: bold;
  color: white;
}
Navigation menu is missing

The menu is imported as an HTML Box called Navigation Links inside the Header block. Run the translator again with --verbose. If the line says "Built Header block" without "with navigation", your export had no menu with items, so assign a menu in WordPress and export again. Otherwise open the theme Editor under Admin › Theme Settings and check the Header block is still in your templates.

Your hosting account

Your host's scan finds infected files, or old sites are still on the account

A hosting account that ran WordPress for a while can still hold folders of old sites. Every folder on the account runs under the same login, so an infected old site puts your new one at risk too.

If your host has scanned the account, look in your home folder for a report such as scanreport.txt. It lists each infected file with its folder.

If every flagged file is in a folder your site no longer uses, you can remove those folders yourself:

  1. In cPanel, open Domains and note every folder in the Document Root column. Leave those, including your main site's folder.
  2. Leave your old-wordpress folder too, until you no longer need it.
  3. In File Manager, delete only the flagged folders that are not on that list. If you are not sure what a folder is, leave it.
  4. Check your main address still loads, then click View Trash and Empty Trash.
  5. Open Cron Jobs in cPanel. Ask your host about any job you did not set up.
  6. Ask your host to scan the account again.

If a flagged file is inside your main site's folder, delete nothing yourself. Send the report to your host first.

A backup made before the clean-up holds the infected files too. Never copy those folders back to the server.

A scan only checks files. Change your hosting, cPanel, FTP and email passwords, and turn on Two-Factor Authentication in cPanel. What it is and how to set it up.

Look through your DNS records in Zone Editor too. A record pointing at a service you no longer use is better removed. If you are not sure, ask your host.

Content, links and files

Images or downloads are broken

The translator rewrites upload paths to /user-content/uploads/wp-media/. Make sure your files are uploaded there, keeping the same folder structure they had in wp-content/uploads/. If your WordPress site used year/month subfolders, those must exist on the PageMotor server too: copy the entire folder tree, including PDFs and other files, not just the images. If something is still broken, compare one broken URL in your browser's dev tools against what is actually on the server via SFTP.

Shortcodes showing as raw text, or content missing

If you can see [contact-form name="…"] or [booking-form] as literal text rather than rendered forms, the plugin that handles that shortcode is not installed or not activated. Install and activate EP Email for [contact-form], or EP Booking for [booking-form] and [booking-services].

Only contact, booking and newsletter shortcodes are kept. Every other WordPress shortcode, such as a gallery or slider, is turned into a hidden note in the page, so what it used to display is simply missing. The page map lists them all under "Shortcodes hidden". To find one on a page, view the page source and search for shortcode:, then rebuild that content by hand. Migrated with v2.4.4 or older? A stray closing tag such as [/caption] is the leftover end of one of these, and words in square brackets may be missing from your text: see the "Words in square brackets" row in What does not migrate.

A page shows "not found", but it is there in the admin

PageMotor finds a top-level page by its slug alone, whatever its type. If another item has the same slug, such as a course, a product or a page you added later, one of them shows "not found". The translator renames custom-type items that clash with a page, and lists them in the page map under "Slugs renamed". For anything you add yourself, give it a slug nothing else uses.

Forms

Forms show "Contact form error: Form ... not found"

The name in the shortcode must match a form name in EP Email exactly, including capitals. Open the page in the content editor and note the name in the shortcode. Then open EP Email's Contact Forms settings and check Form Definitions (JSON) has a form with that name as its key. Add the form there, or change the shortcode to an existing name.

Every form says "Please wait a few minutes before submitting again"

EP Email limits how often one visitor address can send a form. If your site sits behind a proxy, such as Cloudflare or a tunnel, PageMotor may see the proxy's address instead of each visitor's, so many visitors share one limit and most of them are refused.

The fix belongs in the web server, not in PageMotor: it must pass the real visitor address through to PHP (on nginx, the real_ip module set to trust your proxy). Ask your host. Until then, switching off Enable Rate Limiting in EP Email's Contact Forms settings lets the forms through.

My order form (Stripe / payments / PDF generation) does not work after migration

The translator moves the form shortcode, not what happened after someone pressed Submit. Payment processing, PDF generation, file uploads, conditional logic and electronic signatures were handled by WordPress plugins (the Gravity Forms Stripe add-on, Gravity PDF and similar), and none of that comes across.

Some of it can be rebuilt by hand with EP plugins. EP Email has conditional fields built in, EP Email File Uploads adds upload fields, and EP Ecommerce with its Stripe add-on can sell products with card payment at checkout, and EP Email Signatures adds a signature pad to a form. PDF generation has no direct replacement today.

Two other practical options. (1) Replace the order form with a contact-to-order notice: the customer fills a simple form, and you reply with a Stripe Payment Link or bank transfer details. This works in days, not weeks. (2) Re-implement it as a custom PageMotor plugin: a multi-day developer job, worth it only for high-volume flows. Plain contact forms (name, email, message, optionally phone or subject) work fine after Step 14.

Still stuck? If you have a PageMotor account, post where you got to in the PageMotor forum (members only) and paste the last few lines from the translator or the migration script. That is usually enough to diagnose it.