How to migrate WordPress.com to WordPress.org (without losing SEO)

01Why people move from .com to .org

WordPress.com is a fine place to start a site: someone else runs the servers, handles updates, and keeps the lights on. But the same hands-off convenience is also a ceiling. The plan you're on decides what plugins you can install, whether you can run your own ads, and how much you can really customize.

WordPress.org — the self-hosted version — is the same software with the lid taken off. You install it on hosting you choose, add any plugin or theme, monetize however you like, and move the whole site elsewhere whenever you want. The trade is that the maintenance is now yours.

What actually changes when you self-host

• Full plugin and theme freedom. .org installs anything from the directory or a paid vendor; .com gates plugins behind higher plans.
• Ownership and portability. Your site lives on hosting you control, so you can move hosts later without asking permission. That's the opposite of platform lock-in.
• Monetization on your terms. Run your own ads, affiliate links, and checkout without revenue-share rules or plan gates.
• You own the maintenance too. Updates, backups, and security are now your job — which is exactly what a good managed host quietly handles for you.

None of this makes WordPress.com wrong. It means that once your site starts earning its keep or outgrowing the plan, owning the thing you depend on is worth a one-time afternoon of moving.

02What moves cleanly and what breaks

This migration is unusually friendly because both sides speak the same format. WordPress's built-in exporter produces a standard XML file, and the importer on the other end reads it natively. Most of your content simply transfers. But a few things still need a human eye.

The headline is that your words, images, and comments come across in one file, which is why this is a migration in the true sense rather than a rebuild. The theme and any .com-specific features do not travel, so plan to reinstall a theme and rewire the small stuff by hand.

The one quiet trap is URLs. If your .com site used a date-based permalink and your new .org install defaults to something else, every old link breaks. Decide your permalink structure on the new site before you import a single post.

03Pre-flight checklist before you touch anything

Five minutes of preparation here saves hours of cleanup later. Run this list before you export anything, so you start the move knowing exactly what you have and where it's going.

• Inventory your content. Note your post and page counts so you can confirm they all arrived after import.
• Record your current permalink structure. Whatever .com uses, you'll want to match it on .org to keep URLs identical.
• List your active plugins and key features. You'll reinstall .org equivalents; knowing the list up front avoids surprises.
• Choose your hosting and domain. Decide where the self-hosted site will live and whether you're keeping the same domain or moving off the .wordpress.com subdomain.
• Export a full backup of the .com site using Tools, Export, All content — this XML file is the heart of the move.

If your old site lived at a name.wordpress.com subdomain and you're moving to your own domain, note that now: that domain change is the single biggest SEO factor in this whole project, and it needs redirects we'll cover below.

04The step-by-step on a staging copy

Do the whole move on a staging site first — a private copy nobody can see — and only push live when it's right. Here's the sequence that keeps the import boring in the best way.

• Install WordPress.org on your host. Most hosts offer one-click installs; many will do it for you.
• Set your permalink structure first, under Settings, Permalinks, to match what your .com site used.
• Export from .com via Tools, Export, All content, and download the XML file.
• Import into .org via Tools, Import, WordPress — installing the importer plugin when prompted — and upload the XML.
• Let it pull media by ticking the option to import file attachments, then verify images actually came across.
• Reinstall a theme that matches your old look, and reinstall plugin equivalents for any features you relied on.

The importer offers to download and import your media files when it runs. Tick that box, but don't trust it blindly — large libraries sometimes drop a few images, so walk through your posts afterward and reupload any that show as broken.

Once the staging copy looks complete and the content counts match your inventory, you're ready to think about URLs and redirects before going live.

05Preserving your SEO: URLs, redirects, and canonicals

Because the software is identical, your SEO survives this move far more easily than a cross-platform migration — but only if you handle the URL change deliberately. There are two scenarios, and which one you're in decides how much work this is.

If you keep the exact same domain and the exact same permalink structure, your URLs don't change at all, and there's almost nothing to redirect. This is the ideal case, and it's why matching permalinks before importing matters so much.

Handling the domain or structure change

• Moving off a .wordpress.com subdomain? Every old name.wordpress.com URL must 301-redirect to its match on your new domain. WordPress.com's paid Site Redirect upgrade can do this at the source.
• Changing permalink structure? Map each old URL to its new one and set a 301 for each — a redirect plugin like Redirection makes this code-free.
• Rebuild your sitemap with an SEO plugin (Yoast or Rank Math) and submit it in Google Search Console after launch.
• Set canonical tags so search engines treat the new URLs as authoritative; your SEO plugin handles this automatically per page.

The .com subdomain case is the one to respect. Once you stop paying for that site, those URLs eventually disappear, so the Site Redirect upgrade or a clean DNS-level redirect is what carries your existing rankings to the new home. Skip it and you start from scratch.

06The tools that help

You don't need a toolbox for this one — the core move uses WordPress's own native features. But a few extras smooth the edges, and it's worth knowing what each actually does so you don't overbuy.

• WordPress native Export/Import is the whole engine of the move. It's free, built in, and the only mover you truly need for content.
• A redirect plugin (Redirection, or your SEO plugin's redirect manager) turns any URL changes into live 301s without editing server files.
• An SEO plugin (Yoast or Rank Math) rebuilds your sitemap, canonicals, and meta fields on the new install.
• A site crawler (Screaming Frog's free tier) lists every old URL so nothing slips through if your structure changed.
• Managed WordPress hosting with a one-click install and free staging removes the only genuinely technical part — standing up the new site.

On hosting: Cloudways is the managed cloud host we point readers to here, mainly because every app comes with a free staging environment. That lets you run the entire export-import-test cycle on a private copy and push live in one move, instead of importing straight onto a site visitors can see. Several hosts offer staging; this is just the one we lean on.

Staging is the quiet hero of any migration. It turns a nerve-wracking switchover into a dress rehearsal you can repeat until it's right, then promote in a single click.

07Common pitfalls and a hosting note

Most of what goes wrong in this move is predictable, which means it's avoidable. Here are the snags that trip people up most often, and how to sidestep each one.

• Importing before setting permalinks. Set your URL structure first, or you'll be redirecting links you never needed to change.
• Trusting the media import blindly. Large libraries drop images quietly — walk every post and reupload broken ones.
• Forgetting the subdomain redirect. A name.wordpress.com site that just stops existing takes its rankings with it; redirect it.
• Cancelling the .com plan too soon. Keep it active briefly so it can serve redirects and act as a reference copy.
• Assuming plugins transfer. They don't — reinstall .org equivalents for every feature you relied on.

On the hosting side, the one decision that shapes the rest is where the self-hosted site lives. A managed host that does the WordPress install for you, keeps backups, and offers staging turns the most technical part of going self-hosted into a non-event — which is the whole point of moving to ownership without taking on a second job.

08FAQ

Is moving from WordPress.com to WordPress.org hard?

It's one of the easier migrations, because both use the same software and the same native export-import tools. Your posts, pages, comments, and most media come across in a single XML file. The work is mostly hosting setup, reinstalling a theme, and matching URLs — not rebuilding anything.

Will I lose my SEO when I switch?

Not if you keep the same domain and permalink structure, in which case your URLs don't even change. The only real risk is moving off a .wordpress.com subdomain or changing your URL structure — both of which are solved by mapping old URLs and setting 301 redirects before launch.

Can I keep my domain name?

Yes. If you registered a custom domain through WordPress.com you can transfer it out or repoint its DNS at your new host. If you were on a free name.wordpress.com subdomain, you'll move to your own domain and redirect the old subdomain URLs across to preserve any existing rankings.

Do my plugins and theme come with me?

No — themes and plugins don't transfer in the export file. You reinstall your theme (or pick a close match) and reinstall equivalent plugins for any features you used on .com. The upside is that on .org you can install anything, including tools .com never allowed.

This is general, experience-based guidance from running a theme shop, not financial or professional advice for your specific site. Plans, tools, and host features change, so verify the current details with WordPress.com, your chosen host, and the plugins before you rely on them — and if your site carries real revenue, consider professional help.