WordPress.org to WordPress.com: I Moved a Live Site to Managed Hosting (2026)
I moved a live self-hosted WordPress site to WordPress.com managed hosting. What transfers, what does not, what changed, the honest catch, and the 2026 pricing.
Moving from self-hosted WordPress.org to WordPress.com managed hosting hands the server work, updates, security patching, backups, SSL, CDN, to the platform, so you stop being a part-time sysadmin. A free guided migration (or a plugin like WPvivid) moves your content, media, theme, plugins and users, though not everything (subscribers, config edits and licenses need re-doing). You lose some low-level control and live inside WordPress.com's ecosystem, but for most site owners the trade is worth it. Paid plans start at $4/month, and plugins now work on all of them.
For years I ran my own WordPress servers. Updates, backups, security plugins, the 2 a.m. "why is the site down" panic. All of it.
Then I moved a live site to WordPress.com's managed hosting to see what I was actually holding onto.
Short version: the server work disappeared, and I did not miss it.
This is the honest account of that move, what transferred, what did not, what genuinely changed, the catch nobody mentions, and what it costs in 2026.
WordPress.org vs WordPress.com: what is the difference?
Same WordPress software. Completely different responsibility model.
| WordPress.org (self-hosted) | WordPress.com (managed) | |
|---|---|---|
| Who runs the server | You | The platform |
| Updates & patching | Your job | Automatic |
| Security & backups | Plugins you configure | Built in |
| SSL, CDN, firewall | You set up | Included |
| Control | Total | High, within guardrails |
| Best for | Full control, any host | Owners who want to just publish |
Self-hosted gives you total control, and total responsibility. Managed trades a little of that control for someone else doing the maintenance. That is the entire decision.
Why I finally left self-hosted
Not because self-hosting is bad. Because the maintenance never ends.
Every week: core updates, plugin updates, a caching plugin to babysit, a security plugin to configure, backups to verify. None of it is writing. All of it is the tax you pay to keep the lights on.
And the biggest risk is the boring one, falling behind. Patchstack's State of WordPress Security 2025 found that 96% of new WordPress vulnerabilities in 2024 were in plugins, not core. Sucuri's data tells the same story from the other side: a large share of hacked sites were running outdated software at the point of infection, and its scanners flag hundreds of thousands of infected sites a year.
Managed hosting does not make you invincible. But it takes the single most common failure, unpatched software, off your plate. That was enough for me to test the move. (If you want the deeper security picture, Kinsta's write-up on WordPress security is a solid read.)
How the migration actually works
I cloned one of my live sites to test this properly, rather than gamble with the real thing. There are two routes.
Option A: free guided migration (the easy way)
WordPress.com's team will move your self-hosted site for you, free. You request it, they handle it, usually within a few business days, and your live site stays up the whole time. You just need a paid plan on the destination. For most people, this is the right choice.
Option B: WPvivid plugin (the hands-on way)
This is the route I took to watch every step. Back up the old site into a single archive with WPvivid (files + database together), then import that archive into a fresh WordPress.com site. Note: WPvivid is a third-party plugin, not the WordPress.com service, so you are driving.
Let it transfer
Posts, pages, media, the theme, plugins, users and settings come across. Reconnect Jetpack if prompted. Then point your domain at the new host and you are live.
What does NOT transfer (plan for it)
The import moves content, not everything. Budget to redo: email subscribers, post likes, wp-config.php/functions.php edits, and plugin/theme licenses (re-confirm with each developer). Multisite is not supported. And the import overwrites the destination, so always import into a fresh site, never one with content you want to keep.
What changed after the move
The dashboard is where it clicks. The environment is simply handled.
No more version anxiety. WordPress core, PHP, SSL, the CDN and the firewall are all managed for you, currently WordPress 7.0 on PHP 8.4, patched without me touching a thing. Activity is logged automatically too, so I can see every login and setting change.
The plugins I could finally delete
This was the satisfying part. A pile of plugins I maintained for years, gone, because the platform does their job natively.
Stats, anti-spam (Akismet), newsletter and subscriptions, image optimisation and CDN, social sharing, and basic SEO controls all ship built in. My caching plugin (LiteSpeed) and security plugin (MalCare) became redundant overnight.
Fewer plugins is not just tidiness. Since 96% of vulnerabilities come through plugins, every one you remove is one less door to lock.
Speed and scale, without the tuning
On self-hosted, performance is your problem: caching, a CDN, a server sized for your worst day. Here it is the platform's problem.
WordPress.com advertises 99.999% uptime with automatic failover, a CDN across 28+ data centres on six continents, burst scaling to 100+ PHP workers, and unmetered bandwidth on every plan. Take the "five nines" and "unmetered" as vendor marketing (there is a fair-use policy), but the point stands: you stop sizing servers and start just publishing. For images specifically, the built-in CDN does what I used to wire up with an image CDN by hand.
It is not just for beginners
The biggest myth. Managed hosting is not training wheels, the Business plan hands you a full developer toolkit.
SSH, SFTP, WP-CLI, staging sites, GitHub deployments, phpMyAdmin and PHP version control are all there. I have even let Claude run my hosting through this kind of tooling. You keep the developer workflow; you just drop the server babysitting.
The AI features it added in 2026
WordPress.com leaned hard into AI this year, and both tools are genuinely useful post-migration:
- The AI website builder spins up new sites from a prompt.
- The AI Assistant edits your existing site from inside the editor.
- And Global Styles, fonts and CSS now come with every paid plan for hands-on design.
The honest catch
It is not all upside, and pretending otherwise would be the affiliate-brochure move I avoid.
What you give up
- Some low-level control. You work within the platform's guardrails, not root on your own box.
- A few things do not transfer (subscribers, config edits, licenses, multisite, see above).
- You are in an ecosystem. Convenient, but it is Automattic's environment, not your bare metal.
The saving grace: it is still WordPress. You can export and leave whenever you want, so this is a reversible choice, not a lock-in.
WordPress.com pricing in 2026
| Plan | Monthly | Billed yearly | Key features |
|---|---|---|---|
| Personal | $9 | $4/mo | Custom domain, publish, plugins |
| Premium | $18 | $8/mo | More storage, design tools |
| Business | $40 | $25/mo | SSH, staging, GitHub, backups |
| Commerce | $70 | $45/mo | Full WooCommerce store |
Annual plans include a free custom domain for the first year, and since April 2026 plugins work on all of them. For a site that just needs to run reliably, Personal or Premium is plenty; go Business only if you need the developer tools.
What else you get: domains, email and support
- Domains — a free custom domain for year one on annual paid plans.
- Professional email — Business and Commerce bundle a free Professional Email (Titan) mailbox for the first year. (On its own it is a 3-month trial, then paid, so the free year is the plan perk.)
- Support — real humans, which after years of forum-hunting for self-hosted fixes is its own kind of relief.
New to the platform entirely? Start with how to start a blog on WordPress.com.
Who should move?
- Bloggers and small businesses who want to publish, not maintain servers → yes, easily.
- Developers who want managed infrastructure but keep SSH/WP-CLI/staging → yes, on Business.
- People who need root access, custom server stacks, or multisite → stay self-hosted.
Final take
I went in expecting to feel boxed in. Instead I felt lighter.
The work I handed over, updates, patching, backups, caching, scaling, was never the work I actually cared about. It was the tax on doing the work I cared about. Managed hosting quietly removed the tax.
If you are spending more time keeping WordPress running than using it, that is your signal. Clone a site, try the free migration, and see how much of your week you get back. You can always leave, so the only real risk is finding out you like it.
Want your WordPress site fast, secure and ranking, wherever it's hosted?
Managed hosting handles the server. Making a site actually rank and convert is a different craft. If you want a WordPress site engineered for speed and search, send us your goals, the first reply comes from Sunny, not a sales team.
See WordPress developmentCommon questions
Will I lose my posts when I move to WordPress.com?
No. Your posts, pages, media, theme, plugins and users transfer. But not everything comes across: email subscribers, post likes, wp-config or functions.php edits, and plugin/theme licenses usually need re-doing, and multisite is not supported. Keep a full backup before you migrate, just in case.
Do I still need plugins on WordPress.com?
Fewer than you think. Stats, anti-spam, newsletter, image CDN, social sharing and basic SEO are built in, so you can delete those plugins. For anything else, plugins now work on every paid plan (from the $4 Personal plan) since April 2026, not just Business.
Which plan do I need to migrate?
Any paid plan works as the destination, and the guided migration itself is free. To publish on your own domain you need at least the Personal plan ($4/month annually). Developer tools like SSH and staging require the Business plan.
Is WordPress.com more secure than self-hosted?
For most people, yes, because the biggest risk is outdated software. Patchstack found 96% of 2024 WordPress vulnerabilities were in plugins, and managed hosting patches the stack for you. You still choose your plugins wisely, but the server-level maintenance risk is largely removed.
Can developers still use WordPress.com?
Yes. The Business plan includes SSH, SFTP, WP-CLI, staging sites, GitHub deployments, phpMyAdmin and PHP version control, the same tools you would expect from any managed host. It is not a walled garden for beginners; it just runs the server layer for you.
Can I move back off WordPress.com later?
Yes. It is still WordPress, so you can export your content and move to another host whenever you like. That portability is the safety net: you are choosing convenience, not locking yourself in, so trying managed hosting is low-risk.
SEO Specialist and product builder with 10+ years in search. The notes come from the work, not the theory.