Categories
Web Hosting WordPress WP Engine

How to Migrate a WordPress Site to WP Engine with the Site Migration Plugin

Some links on this page are affiliate links. If you sign up through them I may earn a commission at no extra cost to you.

I’ve moved a lot of client sites onto WP Engine over the years, and the Site Migration plugin does most of the heavy lifting. You install it on the old site, paste in a connection string, and it copies the database and files across. Here’s how it works in 2026, plus the snags that tend to stop a migration halfway.

Before you start

Both the old site and the new WP Engine environment need to meet these minimums:

  • WordPress 5.0 or newer
  • PHP 7.4 or newer
  • MySQL 8.0
  • The WordPress REST API turned on
  • A current browser (Chrome, Firefox, Safari, or Edge)

You also need a WP Engine plan with an empty environment to migrate into. If you’re still picking one, my WP Engine plans comparison covers the differences. Take a backup on your current host before you begin. The plugin doesn’t change the source site, but it’s cheap insurance.

Step 1: Prepare the WP Engine site

  1. Log in to the User Portal and open Sites.
  2. Click the environment you’re migrating into.
  3. Open Site migration in the left menu (it sits under Manage if the menu is collapsed).
  4. On the Automated migration tab, click Install plugin.
  5. When the success message shows, copy the connection information. You will paste it into the old site in a minute.

Step 2: Install the plugin on your old site

  1. Download the Site Migration plugin ZIP from the same screen in the User Portal.
  2. Log in to wp-admin on your current host (not WP Engine).
  3. Go to Plugins > Add New Plugin > Upload Plugin, choose the ZIP, then install and activate it.

Step 3: Run the migration

In the old site’s wp-admin, open Site Migration, click Start a new migration, paste the connection information, and click Connect. Then pick a migration type:

TypeWhat it copiesWhen to use it
Full site migrationAll database tables and wp-content files, and it updates your domain in the database (serialized data included)Most sites. Start here.
Customize the migrationOnly what you pick: tables, media, themes, plugins, must-use plugins, other wp-content files, and root filesWhen you need root files, want to skip large folders, or are re-syncing

Add an email address if you want status updates, click Start Migration, and keep the status page open. A full migration skips logs, backups, caches, and any plugins WP Engine doesn’t allow.

Step 4: Sync again right before you switch DNS

If the old site keeps getting new posts, orders, or comments while you test, run the plugin a second time just before go-live. You can reuse a saved profile, or build a custom one that only copies changed tables, media uploaded after a set date, and plugins or themes you added or updated.

Step 5: Test, add your domain, and go live

  1. Check the site on its WP Engine URL. If something breaks, compare the PHP and WordPress versions with your old host first.
  2. Add your domain in the User Portal.
  3. Point DNS to WP Engine. If you use the Advanced Network or Global Edge Security, SSL and the CDN are set up for you.
  4. Run a search and replace if any pages still reference the old domain.
  5. Review cache exclusions for things like login or checkout pages.

My WP Engine go live checklist post walks through the portal’s own checklist for this part.

Common problems and fixes

ProblemWhat to do
Redirects or access rules stopped workingWP Engine doesn’t read .htaccess. Recreate those rules in the Web Rules Engine.
Migration slows down or gets blockedSecurity plugins with a firewall, like Wordfence, can rate limit the plugin. Pause the firewall during the move.
Failed loopback request errorThe old server has to resolve its own hostname. Turn off Cloudflare Under Attack mode while you migrate.
Stalls on a LiteSpeed hostWP Engine’s support article has a short .htaccess snippet for the source site that usually fixes it.
Destination is password protectedEnter the Basic Auth username and password when the plugin asks.
Multisite networkConvert the WP Engine site to multisite first. You can move a whole network, not single subsites.

If it still fails, contact WP Engine support with the environment name, the error message, and the migration ID from the error page or failure email. Business plans also include managed migrations, so WP Engine will do it for you.

Need a home for the site first? Every WP Engine plan includes the migration plugin, staging, and daily backups.

FAQ

Is the WP Engine migration plugin free?

Yes. The Site Migration plugin is free to use for moving a site into a WP Engine environment.

Will my site go down during the migration?

No. Your old site stays live the whole time. Visitors only reach the WP Engine copy after you point DNS to it.

Can I migrate a single site out of a multisite network?

No. The plugin can move a whole network into a WP Engine site that has already been converted to multisite, but not individual subsites.

Related

Categories
Reviews Web Hosting WordPress WP Engine

WP Engine Smart Plugin Manager: What It Does and Whether It’s Worth It

Some links on this page are affiliate links. If you sign up through them I may earn a commission at no extra cost to you.

Plugin updates are the most tedious part of looking after WordPress sites, and the part most likely to break something at 2 a.m. Smart Plugin Manager is WP Engine’s answer to that. It runs your updates on a schedule, checks that the site still looks right, and undoes anything that broke it.

What Smart Plugin Manager does

  • Takes a full backup before it changes anything.
  • Updates plugins and themes on the schedule you set.
  • Screenshots the pages you choose before and after, then compares them on desktop, mobile, or both.
  • Rolls the update back automatically if the visual check fails.
  • Clears the cache when it’s done and sends a report of what updated, what failed, and what it rolled back, with the screenshots.

WP Engine says it has rolled back roughly 15,000 updates this way before they reached a live site.

Scheduling and control

  • Run updates daily, weekly, or monthly, in 6-hour off-peak windows on the days you pick.
  • Kick off a one-time run whenever you want.
  • Include or exclude individual plugins and themes.
  • Turn on maintenance mode during runs if you like.
  • Premium, private, Git-based, and multisite plugins work too, as long as commercial ones have a valid license.
  • Optionally test on a staging copy first. That needs a license on the staging environment as well.

Smart Plugin Manager vs WordPress auto-updates

WordPress can update plugins on its own for free, so it’s fair to ask what you’re paying for.

WordPress auto-updatesSmart Plugin Manager
Backup before updatingNoYes
Checks the site still looks rightNoYes, visual comparison of pages you pick
RollbackOnly if the update causes a fatal PHP error (WordPress 6.6 and newer)Yes, when a visual test fails
Choose the time windowNoYes
ReportsEmail noticesDetailed reports with screenshots
CostFreeIncluded on some plans, paid add-on on others

What it won’t catch

  • It only checks the pages you tell it to. Pick your home page, a key landing page, and anything with a form or checkout.
  • A visual check sees layout, not logic. A contact form that looks fine but no longer sends will slip through, so keep testing the things that make you money.
  • It handles plugins and themes. WordPress core updates are part of WP Engine’s managed hosting.

What it costs

WP Engine includes Smart Plugin Manager on some plans and sells it as a low-cost add-on on others. Business plans come with licenses for a few add-ons, so check whether it’s one of yours before buying it separately. Agencies reselling it can get it for as little as $2 per site. Current prices are on the WP Engine plans page.

Is it worth it?

For sites you’re paid to maintain, yes. One update that takes down a client’s site costs more in time and goodwill than a year of the add-on. Same for WooCommerce stores, where a broken page means lost sales. For a personal blog, WordPress auto-updates plus a good backup are usually enough.

Managing client sites? WP Engine pairs Smart Plugin Manager with staging, daily backups, and support that actually knows WordPress.

FAQ

Does Smart Plugin Manager update WordPress core?

No. It updates plugins and themes. WordPress core updates are handled by WP Engine as part of its managed hosting.

Does Smart Plugin Manager work with premium plugins?

Yes. It supports commercial, private, Git-based, and multisite plugins, as long as commercial plugins have a valid license.

What happens when a visual test fails?

Smart Plugin Manager rolls that update back automatically and notes it in the report, with before and after screenshots so you can see what changed.

Related

Categories
Pressable Web Hosting WordPress WP Engine

Is Managed WordPress Hosting Worth It? When It Pays for Itself

Some links on this page are affiliate links. If you sign up through them I may earn a commission at no extra cost to you.

Clients ask me this all the time. The short answer: if the site makes money, or you bill for your time, managed WordPress hosting usually pays for itself. If it’s a hobby blog with a few hundred visitors a month, cheap shared hosting is fine. Here’s how I think about it.

What you’re actually paying for

Managed hosts like WP Engine and Pressable cost more than a $5 shared plan because they take jobs off your plate:

  • Server-level caching and a CDN, so you’re not tuning a caching plugin.
  • Automatic backups you can restore in a click.
  • One-click staging sites for testing updates.
  • Security handled at the server, plus automatic WordPress core updates.
  • Support people who know WordPress, not just the server.

Doing the math

JobOn cheap shared hostingOn managed hosting
BackupsInstall a plugin, set up off-site storage, test restoresIncluded
SpeedConfigure a caching plugin and a CDNBuilt in
StagingPlugin or a manual copyOne click
SecuritySecurity plugin and firewall to manageHandled by the host
When it breaksGeneral hosting supportWordPress specialists

Here’s a simple example. Say your time is worth $50 an hour and you spend one hour a month on hosting chores. That’s $600 a year. Pressable starts at $250 a year and WP Engine Essential at $28 a month billed yearly, about $336 a year. Even before you count a single avoided outage, the managed plan comes out ahead.

When cheap hosting is fine

  • A personal blog or portfolio with low traffic.
  • You enjoy tinkering with servers and don’t mind fixing things yourself.
  • The site doesn’t make money, so an afternoon of downtime doesn’t cost anything.

WP Engine or Pressable?

They’re the two managed hosts I’ve spent the most time with, and they suit different people.

PressableWP Engine
Entry price$250 a year (about $20.83/mo)From $28/mo billed yearly
Entry visits30,000 a month25,000 a month
Entry storage20 GB10 GB
BackupsHourly database, daily fullDaily
Support24/7 chat24/7 chat, phone on Business and up
Best forSeveral small sites, tight budgetsBusy sites and demanding clients

I go deeper in Pressable vs WP Engine.

Ready to stop babysitting your hosting? Pressable is the budget-friendly pick for several small sites. WP Engine is the one I use for busy client sites.

FAQ

What is managed WordPress hosting?

Hosting built only for WordPress, where the host handles caching, backups, security, staging, and core updates for you, and support knows WordPress well.

Is managed WordPress hosting faster?

Usually, because of server-level caching and a built-in CDN. A heavy theme or too many plugins will still be slow anywhere, though.

Can I switch to managed hosting later?

Yes. WP Engine has a free migration plugin and includes managed migrations on Business plans, and Pressable offers free migrations.

Related

Categories
Pressable Web Hosting WordPress WP Engine

Pressable vs WP Engine: Which Managed WordPress Host Is Right for You?

Last updated: October 15, 2026

Some links on this page are affiliate links. If you sign up through them I may earn a commission at no extra cost to you.

Recent contentiousness between the two companies aside, I figured it would be helpful to compare Pressable and WP Engine. I’ve hosted client sites on WP Engine for years, and this site now runs on Pressable. Both are premium managed WordPress hosts, so this focuses on where they differ.

Quick comparison

PressableWP Engine
OwnerAutomatticWP Engine (Silver Lake)
Entry price$250/yr (about $20.83/mo)From $28/mo billed yearly
Entry visits30,00025,000
Entry storage20 GB10 GB
BackupsHourly database, daily fullDaily
CDNEdge CacheCloudflare-powered Advanced Network
EmailYes, Titan add-onNo
Git deploysYesYes (GitPush)
Support24/7 chat24/7 chat, phone on Business+

Pricing

At the entry level, Pressable is cheaper and includes more storage and visits. As you add sites, Pressable’s plans are counted by sites and visits, while WP Engine scales by traffic and storage and moves to isolated resources at the Business tier. Agencies with lots of small sites will usually find Pressable easier to budget. See Pressable Pricing and WP Engine Pricing.

Performance

Both are fast. Pressable uses Edge Cache to serve full pages and static files from the edge. WP Engine uses its own caching plus Cloudflare’s network. For most sites, you won’t feel a difference in load time between them.

Features

  • Staging: both include it. WP Engine gives each site production, staging, and development environments.
  • Email: Pressable offers Titan email for $3.50 per inbox. WP Engine doesn’t offer email, so you’ll need Google Workspace or Microsoft 365.
  • Plugin updates: both sell automatic plugin updates as an add-on on entry plans.
  • Security: Pressable includes Jetpack Security. WP Engine’s Global Edge Security is a paid upgrade.
  • Redirects: WP Engine has a redirect tool in the User Portal. Pressable uses a custom-redirects.php file or a plugin.

Support

This is where I’d put the most weight. WP Engine’s support has been excellent for me over many years (more here). Pressable’s support is the thing reviewers praise most, with a 4.8 on G2.

Which should you choose?

  • Choose Pressable for strong value, generous entry limits, built-in email, and Automattic’s backing. Great for individuals, small businesses, and agencies with many small sites.
  • Choose WP Engine for mature developer tools, isolated resources on higher tiers, and phone support. Great for busy sites and agencies with demanding clients.

Neither is a bad choice. Pick based on price and simplicity, or on developer features and scale.

Still deciding? Both are solid. Pick Pressable for several small sites on a budget, and WP Engine for busy sites that need isolated resources or phone support.

FAQ

Is Pressable cheaper than WP Engine?

At the entry level, yes. Pressable starts at $250 a year for one site with 30,000 visits. WP Engine starts at $28 a month billed yearly with 25,000 visits.

Does WP Engine or Pressable offer email?

Pressable offers Titan email as an add-on. WP Engine doesn’t offer email hosting.

Who owns Pressable and WP Engine?

Pressable is owned by Automattic. WP Engine is a separate company backed by Silver Lake.

Related

Categories
WP Engine

WP Engine SSH: Keys, Connection Command, and Gotchas

Last updated: October 12, 2026

Some links on this page are affiliate links. If you sign up through them I may earn a commission at no extra cost to you.

WP Engine gives you SSH access through what it calls the SSH Gateway. It’s the fastest way to run WP-CLI, export a database, or move a lot of files. Setup takes about five minutes.

Step 1: Add your SSH key

WP Engine only accepts ed25519 keys. If you don’t have one, create it on your computer:

ssh-keygen -t ed25519 -f ~/.ssh/wpengine_ed25519
  1. Log in to the User Portal and click your profile icon at the top right.
  2. Choose SSH Keys, or go straight to my.wpengine.com/profile/ssh_keys.
  3. Click New SSH Key, paste the contents of your .pub file on one line, and save.

The key is tied to your user, so it works on every environment you have access to. Give each computer its own key rather than copying one around.

Step 2: Connect

Replace environment with your environment name, in both places:

ssh environment@environment.ssh.wpengine.net

If you have several keys, tell SSH which one to use. The gateway disconnects you after six failed keys, so this matters:

ssh -i ~/.ssh/wpengine_ed25519 -o IdentitiesOnly=yes environment@environment.ssh.wpengine.net

Or add this to ~/.ssh/config once and forget about it:

Host *.ssh.wpengine.net
    IdentityFile ~/.ssh/wpengine_ed25519
    IdentitiesOnly yes

Step 3: Go to your site

You don’t land in your WordPress folder. Move there first:

cd sites/environment

From there you can run WP-CLI, the MySQL client, Composer, rsync, and editors like Vim.

Gotchas

  • Only your site folder persists. Anything outside /sites/environment/, including your home folder and /tmp, is wiped when the session ends.
  • Use _wpeprivate for scratch files. It’s inside the site folder, persists, and isn’t reachable from the web. Good for database exports.
  • 10-minute timeout. Sessions time out, so batch long jobs.
  • No root or sudo, and no server logs. Logs are in the User Portal.
  • No portal tasks. You can’t purge the cache or add users over SSH.
  • Five connections per user at a time.

Shopping for a host with real SSH and Git access? WP Engine includes both, plus staging, on every plan.

FAQ

What is the WP Engine SSH command?

ssh environment@environment.ssh.wpengine.net, replacing environment with your environment name in both places.

What kind of SSH key does WP Engine need?

An ed25519 key. Add the public key in the User Portal under your profile, then SSH Keys.

Why are my files gone after I disconnect from WP Engine SSH?

Only files inside /sites/environment/ persist. Save anything you need to keep there, ideally in the _wpeprivate folder.

Related