How to Move from WordPress.com to WordPress.org (Self-Hosted)

The two platforms share a name and a dashboard, but they are fundamentally different products. WordPress.com is a hosted, managed service run by Automattic, where your site lives on their servers and your plan dictates what you can do. WordPress.org is the free, open-source software that you install on hosting you control, giving you the full plugin ecosystem, custom code access, and complete ownership of your data.

Businesses usually reach this crossroads when WordPress.com's guardrails start blocking growth: you cannot install the plugin you need, you cannot add custom tracking or a real CRM integration, or you are paying a premium plan for features a $5 host and free software would give you outright. The move is well-trodden and safe, but it is not a single button. Done carelessly, you can lose image files, break internal links, and watch hard-won rankings slide.

This guide walks through exactly what transfers, what breaks, and the migration sequence that preserves your SEO and your sanity. If you would rather hand the whole thing off, eSEOspace runs this exact playbook as part of our website migration services.

Why businesses move from WordPress.com to WordPress.org

The self-hosted version removes ceilings you may not notice until you hit them. The most common triggers we see:

• Plugins and themes: WordPress.com only allows third-party plugins on its Business plan or higher (roughly $25/month billed annually and up). WordPress.org lets you install any of the 60,000+ plugins and any theme, free or premium, on day one.
• Real monetization and integrations: You can run your own ad code, connect a proper CRM, add Google Tag Manager, or wire up marketing automation without a plan gate.
• Custom code and CRM: Self-hosting gives you FTP, database, and PHP access, so a developer can build genuine custom website and CRM functionality that WordPress.com's sandbox simply will not permit.
• Cost control and ownership: Instead of an escalating subscription, you pay for hosting you choose and own every file and row of your database.
• No forced upsells or branding: Lower WordPress.com plans show ads and platform branding you cannot remove; self-hosting is entirely yours.

What transfers, what breaks, and what needs rebuilding

Setting expectations up front prevents nasty surprises on launch day. Here is the honest breakdown:

• Transfers cleanly: Posts, pages, comments, categories, tags, and most media are captured by the native export tool and land intact via the import.
• Often breaks: Media library images sometimes fail to copy because the importer references WordPress.com's CDN URLs (files.wordpress.com). You must confirm images physically downloaded into your new media library, not just hotlinked.
• Does not transfer: Your theme and its customizations, widgets, menus, and any Jetpack-powered features (contact forms, related posts, stats, subscriptions, social sharing) do not come across. WordPress.com's built-in features are proprietary and must be recreated with self-hosted equivalents.
• Plugins: There are none to export from WordPress.com; you rebuild functionality by installing self-hosted plugins (e.g., a forms plugin to replace Jetpack forms, an SEO plugin like Yoast or Rank Math, a caching plugin your host may bundle).
• URLs: If you used a free yoursite.wordpress.com address, every URL changes. If you had a custom domain mapped to WordPress.com, your paths usually stay the same, which dramatically simplifies SEO preservation.

Step 1: Export your content from WordPress.com

Log into your WordPress.com dashboard and go to Tools > Export. Choose Export all to generate a WXR file (an XML download containing all posts, pages, comments, custom fields, categories, and tags). If you have the Business plan, you also get an Export media library option and even a full-site archive, which is worth grabbing so you have the raw image files as a backup.

Download the WXR file and store it safely. Do not cancel your WordPress.com plan yet, and do not change your domain settings. Everything must stay live and reachable until the new site is fully built and tested, because you will need the old site online to pull media and verify content.

Step 2: Set up your self-hosted WordPress.org site

Choose a host (SiteGround, WP Engine, Cloudways, Kinsta, and Bluehost are common choices) and install WordPress. Nearly every host offers a one-click WordPress installer, and many will install it for you free. Once WordPress is running, do this before importing anything:

• Set your permalink structure under Settings > Permalinks to match WordPress.com's format (Post name, e.g., /post-title/). Matching the structure is the single biggest factor in avoiding broken URLs.
• Install a fresh theme. Because WordPress.com themes do not transfer, plan to reapply your design here, either by choosing a similar theme or having it rebuilt.
• Install an SEO plugin and a forms plugin so you are ready to recreate lost functionality.
• Keep the new site on a temporary host URL or staging subdomain while you build, so you are not touching live DNS yet.

If design fidelity matters, this is the stage where professional WordPress development pays off, because recreating a WordPress.com theme pixel-for-pixel on self-hosted software takes real front-end work.

Step 3: Import content and pull in your media

In your new WordPress dashboard, go to Tools > Import and choose the WordPress importer (install it when prompted). Upload your WXR file. During the import, WordPress asks you to assign authors and, critically, offers a checkbox to "Download and import file attachments." Always check it. This tells the importer to fetch your images from WordPress.com and store them locally.

After the import finishes, verify carefully:

• Open several posts and confirm images load from your new domain, not from files.wordpress.com. If they still point to WordPress.com, use a media-import plugin (such as Auto Upload Images or Import External Images) to force-download every remote file.
• Spot-check that categories, tags, and post dates came through and that page content is complete.
• Recreate your menus (Appearance > Menus) and widgets, since these were not in the export.
• Rebuild forms, related posts, and any Jetpack feature you relied on using self-hosted plugins.

Step 4: Map and implement 301 redirects to protect SEO

This is where rankings are won or lost. If your URLs are changing, every old address needs a permanent 301 redirect to its new counterpart so that search engines and existing backlinks pass their authority forward instead of hitting a 404.

Two scenarios:

• You had a custom domain on WordPress.com: Keep your permalink structure identical and your paths stay the same, so you may need few or no redirects. Still audit every URL.
• You used a yoursite.wordpress.com address: Every URL changes to your new domain. WordPress.com offers a paid Site Redirect upgrade that 301-redirects your old subdomain to the new domain for a period, which is the cleanest way to catch traffic while search engines re-index.

Build a full redirect map: crawl your old site (Screaming Frog works well), list every live URL, and pair each with its destination. Implement redirects with a plugin like Redirection or at the server level in .htaccess. Our 301 redirect map guide shows the exact spreadsheet workflow, and our broader website migration SEO checklist covers the metadata, sitemap, and Search Console steps that go alongside redirects.

Step 5: Point DNS, launch, and test everything

Once the new site is verified on staging, it is launch time. Update your domain's DNS records (A record or nameservers) at your registrar to point to the new host. If your domain was registered through WordPress.com, either transfer it out or update its records to the new host. DNS propagation can take anywhere from a few minutes to 48 hours, so schedule the cutover during a low-traffic window.

After launch, run through this checklist:

• Submit a fresh XML sitemap to Google Search Console and use the URL Inspection tool to confirm new pages are indexable.
• Test a sample of old URLs to confirm each 301-redirects correctly with no chains or loops.
• Verify forms submit, images load, internal links work, and the site is served over HTTPS with a valid SSL certificate (most hosts provide free Let's Encrypt SSL).
• Reinstall analytics and reconnect any tracking, since WordPress.com's built-in stats do not follow you.
• Only after everything checks out should you cancel your WordPress.com plan.

Realistic timeline and cost

A small blog or brochure site with a handful of pages can be migrated in a single focused day, sometimes an afternoon. A content-heavy site with hundreds of posts, custom design, and integrations is more realistically a one-to-three-week project once you account for theme rebuilding, media verification, redirect mapping, and QA.

On cost, the DIY path is cheap in dollars but expensive in time: hosting runs roughly $5 to $40 per month, plus optional premium plugins or a theme. A professionally managed migration is priced by scope and complexity; at eSEOspace our work is billed at $80/hour, and a typical small-business WordPress.com-to-WordPress.org move lands in a predictable, quotable range because the process is well-defined. Whichever route you take, budget deliberately for the redirect and testing phases, because that is precisely where cutting corners costs you traffic. If you want the migration handled end to end alongside ongoing web development, that is exactly the kind of project we scope every week.