Is managed WordPress hosting vendor lock-in real?

Partly. WordPress itself is portable, your content, themes, and standard plugins move freely. The lock-in is softer: host-specific must-use (mu) plugins, drop-ins, and proprietary features (a host's own caching, CDN, or backup integrations) that don't come with you, plus migration friction like large databases timing out. You can always leave a WordPress host, but how painful it is depends on how much host-specific tooling your site relies on. Check that before you build around it.

How do I know if I can leave my WordPress host?

Confirm three things: (1) you can pull a full backup of files and database yourself, anytime, without asking support; (2) you know which mu-plugins, drop-ins, or host-specific features your site uses (these won't transfer); (3) your database is small enough, or your tooling capable enough, to export without hitting timeouts. If all three are yes, you're portable. If a host won't give you a full self-serve backup, that's the real lock-in red flag.

Can You Actually Leave Your Managed WordPress Host? The Vendor Lock-In Checklist

Q: What makes WordPress migration hard?

The mechanics, not WordPress itself. Common pain: large databases exceeding export timeouts on the source host, migration tools stalling mid-transfer, host-specific mu-plugins that break or do nothing on the new host, and the post-move chores (SSL, DNS propagation, email that stops working). Using the destination host's free managed migration, or a plugin like All-in-One WP Migration or Duplicator for simpler sites, avoids most of it.

By Daniel Brooks · Updated 2026 · WordPress developer tracking managed hosting

Affiliate disclosure: some links below are affiliate links. This is the portability advice I actually give clients before they commit to a host; it doesn't change based on monetization.

The WP Engine drama did something useful: it sent a lot of people to test whether they could actually leave their managed WordPress host, and plenty discovered it was harder than they assumed. Not because WordPress traps you, it doesn't, your content is portable, but because of the softer lock-in that builds up around a managed platform: host-specific plugins, proprietary features, and migration mechanics that fight you on the way out. The good news is portability is checkable in advance. This is how to tell if you're stuck before it matters, and how to get unstuck if you already are.

Short version: WordPress is portable, but managed hosts add soft lock-in: host-specific mu-plugins and drop-ins, proprietary caching/CDN/backup features that don't transfer, and migration friction (large databases timing out, tools stalling). You can always leave, but the cost depends on how much host-specific tooling you've built on. The one real red flag: a host that won't let you pull a full backup yourself. Check portability before you commit, not when you're trying to escape.

What lock-in actually looks like

Let's separate the myth from the real thing. WordPress core is open and portable: your posts, pages, media, themes, and standard plugins move to any host. No managed provider can trap that. The lock-in that actually catches people is softer and easier to miss:

Host-specific mu-plugins and drop-ins. Managed hosts install must-use plugins, wp-content drop-ins, and scripts that power their caching, security, or analytics. These don't transfer, and a site quietly built to depend on them can behave differently (or break features) on a new host.
Proprietary features. A host's own page caching, image CDN, edge logic, or backup system is convenient until you leave, at which point you need to replace each one. The more you lean on a host's bespoke tooling, the more you have to rebuild elsewhere.
Migration mechanics. This is where most of the pain actually lives, large databases that exceed export timeouts on the source host, migration tools that stall mid-transfer, and the post-move chores (SSL, DNS, email) that turn a "quick move" into a weekend.

None of this is sinister, it's the normal byproduct of a managed platform doing things for you. But it means "I'll just switch later" is only painless if you've stayed portable on purpose.

The portability checklist (run it before you commit)

You can confirm you're not locking yourself in with three checks, ideally before you pick a host, definitely before you build heavily on one:

Can you pull a full backup yourself, anytime? Files and database, self-serve, without opening a support ticket. If yes, your data is never hostage. If a host makes full backups hard or support-gated, treat that as the headline warning.
Do you know your host-specific dependencies? List the mu-plugins, drop-ins, and proprietary features your site uses. Anything host-specific is something you'll re-create elsewhere, so keep that list short if portability matters to you.
Will your database actually export? A large database can exceed timeouts on export. Know your size and whether your tooling (or the host's migration service) can handle it, before you're mid-move at 2am.

Three yeses means you're portable, leaving will be a project, not a trap. The point of running this early is that portability is a choice you make while building, not a feature you can bolt on when you're already trying to escape.

Getting out if you're already in

If you're committed to a host and want out, the friction is manageable with the right approach:

Use the destination host's free migration. Pressable, Kinsta, and Rocket.net (among others) offer managed migrations or plugins that handle most of the database, SSL, and DNS gotchas for you, far safer than a manual move.
For simpler sites, use a migration plugin. All-in-One WP Migration or Duplicator package the whole site into one file to upload elsewhere, lower-risk than hand-transferring.
Strip host-specific tooling first. Identify the mu-plugins and proprietary features that won't travel, and plan their replacements (a standard cache plugin or CDN, an independent backup) before cutover, not after.
Sequence the cutover safely. Lower DNS TTL ahead of time, keep the old site live until the new one is verified, and re-check email/SMTP, the step people forget. The full sequence is in how to leave without breaking the site.

The one real red flag

If you remember one thing: a host that won't give you a full, self-serve backup of your files and database is the only lock-in that should worry you. Everything else, mu-plugins, proprietary caching, migration friction, is work, and work has a known cost you can plan around. But if you can't get your own data out without depending on the host's goodwill, you don't fully own your site, and that's the situation to avoid from day one. Reputable managed hosts all provide self-serve backups; treat any that don't as disqualifying.

Bottom line: WordPress is portable; managed hosting adds soft lock-in (host-specific plugins, proprietary features, migration friction) that's real but plannable. Run the portability checklist before you commit, keep your host-specific dependencies short, and make sure you can always pull your own full backup, that last one is the only hard red flag. If you're choosing a host now, factor portability in; see the managed hosts compared. How to actually migrate →

FAQ

Is managed WordPress vendor lock-in real?

Partly. WordPress content is fully portable; the lock-in is soft, host-specific mu-plugins, drop-ins, and proprietary features that don't transfer, plus migration friction. You can always leave; how painful depends on how much host-specific tooling you rely on. Keep that minimal to stay portable.

How do I know if I can leave my host?

Three checks: you can pull a full files+database backup yourself anytime; you know your host-specific dependencies (mu-plugins, proprietary features); and your database will export without timing out. Three yeses means you're portable. A host that won't give self-serve backups is the real red flag.

What makes WordPress migration hard?

The mechanics, not WordPress: large databases exceeding export timeouts, tools stalling mid-transfer, host-specific mu-plugins that don't travel, and post-move chores (SSL, DNS, email). The destination host's free managed migration, or a plugin like All-in-One WP Migration for simpler sites, avoids most of it.

Which managed hosts are easiest to leave?

Any that give you full self-serve backups and don't bury your site in proprietary dependencies. Most reputable managed hosts (Pressable, Kinsta, Rocket.net) offer self-serve backups and free migrations in, the variable is how much host-specific tooling you build on while you're there.