How to convert a free WordPress.com site to self-hosted WordPress

WordPress.com to self-hosted

THE SHORT ANSWER

Export your content from WordPress.com (Tools → Export → All content), set up WordPress on a host, and import the XML file with the WordPress Importer while the old site is still public so images download. Then move subscribers with Jetpack, point or transfer the domain, redirect the old address, and check every URL before you make the old site private.

Moving off WordPress.com is mostly a content move, not a site move. Your posts, pages, comments, categories and tags come across in one XML file. Your theme settings, WordPress.com features, subscribers and the link between your old address and your rankings do not, unless you move them on purpose and in the right order.

This guide covers the whole job: what moves on each plan, the cutover order, the free plan route, the paid plan shortcuts, subscribers, domains and email, redirects, and the checks that tell you nothing was lost. It is written for site owners doing it once and for agencies that do it for clients.

Applies to: WordPress.com Free, Personal, Premium, Business and Commerce plans; self-hosted WordPress with the WordPress Importer 0.9.7 and Jetpack Last verified: November 2026.

01Quick reference

ErrorMost likely causeTry first
Images still load from the old siteResized or linked image URLs the importer did not rewriteSearch the database for wordpress.com
Posts imported without imagesOld site was private, or attachments box not tickedSet old site public and re-run import
Old post URLs return 404Permalink structure does not matchSet Day and name permalinks
Export file too large to importHost upload limit below the file sizeRaise upload limits or use WP-CLI
Subscriber migration option missingJetpack connected with a non-owner accountReconnect Jetpack as the site owner
Email stopped after the DNS switchMX records not copied to the new DNSAdd the MX and TXT records

02What moves, what stays behind

WordPress.com and self-hosted WordPress run the same core software. The difference is who controls the server. On WordPress.com, Automattic does. On a self-hosted site (the software from WordPress.org on a host you pick), you do. That is why the move is easy for content and fiddly for everything around it.

The standard export file is a WordPress eXtended RSS (WXR) file in XML format. According to the WordPress.com export guide, it holds posts, pages, comments, categories and tags, plus links to your media. It does not hold the media files themselves, your theme, your design customizations or plugins.

ItemIn the XML export?How to move it
Posts, pages, comments, categories, tagsYesWordPress Importer on the new site
AuthorsYes (as names)Map to new or existing users during import
Images and other mediaLinks onlyImporter downloads them from the old site, or upload the media export
MenusUsually, on block themes they live in the navigation blockCheck and rebuild by hand if they look wrong
Theme and design settingsNoInstall the same theme (if it is on WordPress.org) and redo the settings
Plugins you installed on WordPress.comNoReinstall on the new site, or use a full-site migration plugin
Email subscribers and followersNoJetpack subscriber migration or CSV export
Site statsNoConnect Jetpack to the same WordPress.com account
LikesNoThey reset to zero
Domain registrationNoChange name servers or transfer the domain
Rankings tied to the old addressNoKeep the same URLs, or redirect every old URL

The last row is the one that costs people traffic. If the domain stays the same and the URL paths stay the same, Google barely notices the move. If either changes, you need redirects, and on WordPress.com redirects have limits that we cover below.

Rather have it moved for you?

We migrate sites to WordPress without losing rankings, with redirects mapped and a fixed quote within 24 hours.

Get a migration quote

03Free vs paid WordPress.com plans: which route you can use

Your current plan decides which tools you can use on the way out. The free plan can always export content. Paid plans add plugin installs and, on the top tiers, full backups.

PlanPluginsBest export routeMedia route
FreeNoTools → Export → All contentTools → Export Media Files (a .tar archive)
Personal, PremiumYesXML export, or a migration plugin such as All-in-One WP MigrationExport Media Library plugin, or Tools → Export Media Files if no plugins are installed
Business, CommerceYes, plus SFTP, SSH and WP-CLIJetpack Backup download (files and database), or a migration pluginJetpack → Backup → View Files → uploads

Current WordPress.com prices, from the official pricing page, billed yearly: Personal US$4 a month, Premium US$8, Business US$25 and Commerce US$45. Monthly billing costs more (Personal US$9, Premium US$18, Business US$40, Commerce US$70). Plugin installs are available on all paid plans.

Should you upgrade just to move out? For a blog or a small brochure site, no. The free XML route moves everything that matters, and the theme has to be redone anyway. An upgrade is worth it when the site has a lot of plugin data (forms, shop orders, custom fields), or when it is large enough that a single backup file saves hours of checking. If you do upgrade, one month on monthly billing is often enough, and WordPress.com offers refunds on plans within a set window, so check the current terms before you buy.

One trap before you upgrade

The Site Redirect support page says the Site Redirect upgrade is not available on sites with plugins installed or hosting features activated. If your site lives on a .wordpress.com address and you plan to use Site Redirect later, installing a plugin to get a nicer export can block that option. Read the redirect section below before you install anything.

04The cutover order that avoids downtime and lost images

Most guides list the steps but not the order. The order matters for two reasons. The importer downloads images from the old site, so the old site must stay public until the import is done. And the domain switch should happen only after the new site has been checked, so visitors never land on a half-built site.

StepWhereWhy it goes here
1. Audit the old site: count posts, pages, media, list URLsWordPress.comYou need numbers to compare later
2. Set up hosting and install WordPress on a temporary addressNew hostBuild without touching the live site
3. Match permalinks before importingNew siteKeeps every old URL valid
4. Export content (and media archive as a backup)WordPress.comOld site still public, so images can download
5. Import with attachmentsNew sitePulls in content and images
6. Theme, menus, widgets, plugins, formsNew siteRebuild what the export does not carry
7. Search for leftover wordpress.com URLs and fix themNew siteStops images loading from the old host
8. Copy MX and other DNS records to the new DNSNew DNS providerEmail keeps working through the switch
9. Point the domain (name servers or A record)RegistrarThe actual go-live moment
10. SSL, final checks, Search ConsoleNew siteConfirms Google sees the same URLs
11. Move subscribersJetpack CloudAfter the new site is live and connected
12. Redirect or make the old site privateWordPress.comOnly after everything above checks out

On the hosting side, any host that runs current PHP and MySQL or MariaDB will do. For agencies, pick the host you already support so the site joins your normal update, backup and monitoring routine. If you work on the new site before the domain moves, use the host's temporary URL or a hosts file entry so you can see the site at its real address before DNS changes.

05Step by step: export from WordPress.com

Audit first

Write down the number of published posts, pages, comments and media items. Export a list of URLs too. A free crawler, or the sitemap at yoursite.wordpress.com/sitemap.xml, gives you the list. This takes ten minutes and it is the only way to prove later that nothing went missing.

Clean up before you export

WordPress.com suggests a few things before exporting: set the site to public, delete drafts you do not need, and clear spam and pending comments. Public visibility matters most, because the new site fetches images from the old one during import. If the site is private or set to Coming Soon, that download fails quietly and you get posts with broken images.

To check, go to Settings → Reading → Site Visibility and pick Public, then save. If the Private option is missing there, the site was never launched, per the privacy settings guide.

Export the content

  1. Open your site dashboard and go to Tools → Export.
  2. Choose All content, or pick specific content types if you only want part of the site.
  3. Click Download Export File. Most sites take one or two minutes and the file downloads in your browser.

Very large sites (roughly more than 1,000 posts or pages) get the export by email as a .zip containing several XML files. Import each XML file separately, in order.

Export the media as a backup

The importer should pull images on its own, but keep a copy anyway. On a site with no plugins, go to Tools → Export Media Files and click Download. You get a .tar archive organized by year and month, according to the media export guide. If you get an XML file instead, you picked the content export by mistake. On Business and Commerce, the same files are under Jetpack → Backup → View Files in wp-content/uploads.

Business and Commerce: the full backup route

On Business and Commerce you can download a full backup, including the database and plugins, from Jetpack → Backup. Pick a backup date, open the menu next to Restore to this point, choose Download backup, then Create downloadable file. You get a .tar.gz with the database as .sql and the wp-content folder. This is the right route for stores and plugin-heavy sites because it carries plugin data that the XML export does not. It is also more work: you import the SQL in phpMyAdmin and fix siteurl and home in the options table yourself.

A middle option on any plan with plugins is All-in-One WP Migration, which WordPress.com documents in its own support pages. It produces one .wpress file with content, plugins, themes and users. The free version handles sites under 2 GB.

06Step by step: import into self-hosted WordPress

WordPress.com posts use dated URLs by default, like /2025/03/14/post-name/. A fresh self-hosted install often defaults to a different structure. If they do not match, every old link and every ranking points to a 404.

On the new site go to Settings → Permalinks and choose Day and name if your old URLs had the date in them. Check three or four real posts on the old site to be sure. Guides disagree here (some say Post name, some say Day and name). The right answer is whatever your old URLs already are. Change the structure later, if you want, with proper 301 redirects (covered below).

Run the importer

  1. On the new site go to Tools → Import and click Install Now under WordPress.
  2. Click Run Importer, choose your XML file and upload it.
  3. Assign each old author to a new user, or create new users. For client sites, map everything to a real editor account rather than creating extra admins.
  4. Tick Download and import file attachments. Without it you get no media.
  5. Click Submit and wait. A large site can take several minutes. Do not refresh.

If the upload fails with a file size message, the host's upload limit is lower than your XML file. Raise upload_max_filesize and post_max_size, or split the file. The WordPress Importer plugin page notes that large files can also hit the PHP memory limit. Our hosting, PHP and cPanel errors guide covers both limits.

Faster on the command line

If the host gives you SSH and WP-CLI, the import skips browser timeouts entirely:

wp plugin install wordpress-importer --activate
wp import yoursite.wordpress.com.xml --authors=create

Compare the counts

Now compare the numbers from your audit with Posts, Pages, Comments and Media on the new site. If posts are missing, run the import again with the same file. The importer skips items that already exist, so a second run only fills the gaps.

07Theme, features and the gaps WordPress.com filled for you

WordPress.com runs many features in the background that a self-hosted site does not have out of the box. Plan for each one rather than finding the gap after launch.

On WordPress.comSelf-hosted replacement
Theme and Customizer settingsInstall the same theme if it exists in the WordPress.org directory, then redo colors, fonts and logo. Block themes keep templates in the database, so rebuild templates and template parts in the Site Editor.
Stats, related posts, sharing buttons, subscriptionsJetpack (free plugin, connected to your WordPress.com account)
Contact formsJetpack forms, or a form plugin. Test that email actually arrives.
Backups and securityYour host's backups plus a backup plugin and a security plugin, or a care plan
Caching and CDNHost caching or a caching plugin, plus Cloudflare if you want it
SEO settingsAn SEO plugin for titles, descriptions and the XML sitemap
UpdatesYour job now, or your agency's

That last row is the real cost of self-hosting. WordPress.com handles core updates, security and backups. Once you leave, someone has to. For agencies, this is usually where the recurring work comes in: a moved site goes straight into a care plan so updates and backups are not forgotten.

Keep the plugin list short. A blog that ran happily on WordPress.com rarely needs more than Jetpack, an SEO plugin, a backup plugin and a security plugin. If you use Cloudflare in front of the new site, our Cloudflare security and DNS guide covers the setup.

08Subscribers, followers and Jetpack

This is the step most guides skip, and it is the one bloggers care about most. WordPress.com has two kinds of audience, and they move differently.

  • Email subscribers get your posts by email. They move to the new site and keep getting emails.
  • WordPress.com followers read you in the WordPress.com Reader. After a migration they see posts in the Reader only, and must subscribe to the new site to get emails.

Connect Jetpack first

Install and activate Jetpack on the new site and connect it with the same WordPress.com account that owns the old site. The Jetpack subscriber migration guide says only the owner account can move subscribers; a non-owner administrator cannot. Connecting the same account also brings your old stats across.

Run the subscriber migration

  1. Open cloud.jetpack.com and select the new site.
  2. Click Subscribers, then the three dots next to Add subscribers.
  3. Choose Migrate subscribers from another WordPress.com site.
  4. Select the old site, click Migrate subscribers, then Confirm subscriber move.

You get an email when the move starts and another when it finishes. Follower counts can take up to a day to update. Likes do not move; they reset to zero.

Keep a CSV copy

Before you migrate, download a backup list from the same screen: three dots → Download subscribers as CSV. It contains email addresses, so store it as you would any personal data. If you later move to a different newsletter tool, this file is your starting point. Paid newsletter subscriptions are tied to the payment setup, so check Jetpack's paid newsletter docs before moving a site that charges subscribers.

09Domain, DNS and email

Three situations, three different jobs.

Your current addressWhat to doRedirect needed?
yoursite.wordpress.com onlyRegister a new domain for the new siteYes, from the old subdomain
Custom domain registered at WordPress.comChange name servers to the new host, then optionally transfer the registrationNo, if permalinks match
Custom domain registered elsewhereChange DNS at your registrar to the new hostNo, if permalinks match

Point the domain without transferring it

You do not have to transfer a domain to move a site. Pointing it is faster and has no waiting period. In the WordPress.com hosting dashboard go to Domains, click the domain, then Name servers under Settings. Turn off Use WordPress.com name servers, enter your host's name servers and save. If your host does not give you name servers, set A records instead. The name server guide says changes can take up to 72 hours to be fully active.

Protect email before the switch

If the domain sends or receives email (Google Workspace, Microsoft 365, Titan or any other provider), that email depends on MX and TXT records in the DNS zone. When the name servers change, the old zone stops answering. Copy every MX, SPF, DKIM, DMARC and verification record into the new DNS zone before you switch. WordPress.com's own guide warns that email may stop working otherwise. This is the single most common surprise after a move, and our email stopped after moving guide covers the fix.

Transfer the registration (optional)

If you want the domain billed by another registrar, follow the domain transfer guide:

  1. Change name servers first, so the site works on the new host before the transfer starts. During a transfer, name servers, DNS records and contact details are frozen.
  2. In Domains, click the domain, then Transfer. Under Transfer to another registrar, switch the toggle to Transfer lock off and click Get authorization code.
  3. The code goes to the domain contact email, which may not be your WordPress.com login email. It usually arrives within 15 minutes.
  4. Start the transfer at the new registrar with that code, then approve the outgoing transfer from the email WordPress.com sends.

Most transfers take five to seven days. A domain registered or transferred in the last 60 days cannot move yet. You can still change its name servers in the meantime.

10Redirects and the old WordPress.com site

If you used a custom domain and kept the same permalinks, you do not need a redirect. The domain now points at the new host and every URL still works. You only need the next part if the old site lived on a .wordpress.com address or your URL structure changed.

Site Redirect for .wordpress.com addresses

Site Redirect is a paid yearly upgrade on WordPress.com that sends visitors from yoursite.wordpress.com, including each post URL, to the new domain. The support page does not list a price, so check it at checkout. Third-party guides quote different figures, which suggests it has changed over time. Set it up from the hosting dashboard: click the site, then Settings → Site redirect, enter the new address and click Redirect.

Read the limits before you pay. According to the Site Redirect guide:

  • It redirects paths, so your new site must use the same permalink structure as the old one. Otherwise visitors land on errors.
  • The destination must be entered as http://. Your new site then forwards to HTTPS on its own, which is one extra hop and is fine.
  • It is not available on sites with plugins installed or hosting features activated.
  • It becomes the site's primary address and cannot be paused.

Keep it running for at least a year so Google and old backlinks catch up. Do not delete the WordPress.com site while the redirect runs; the redirect lives on that site.

The free alternative: make it private

If you cannot or will not pay for the redirect, set the old site to Private under Settings → Reading → Site Visibility once the new site is live. That stops duplicate content, but it throws away the link value of the old address. For a site with real traffic, the redirect is worth paying for. Note also that if a paid plan expires, WordPress.com sets the site back to Coming Soon automatically.

Changing the URL structure with 301s

If you want shorter URLs on the new site, set the new permalinks after launch and add one 301 rule that maps the dated paths to the new ones. On Apache or LiteSpeed, in .htaccess above the WordPress block:

RedirectMatch 301 ^/[0-9]{4}/[0-9]{2}/[0-9]{2}/([^/]+)/?$ /$1/

Test it on five old URLs before trusting it. If you use the Redirection plugin instead, the same pattern works as a regex rule. Do not use this with Site Redirect, which expects the old structure on the new site.

When to delete the old site

Usually never. Deleting it kills any redirect, and you can never reuse the .wordpress.com address. WordPress.com keeps deleted sites restorable for 30 days, then the content and address are gone. Private costs nothing and keeps a backup copy where it is.

11Errors and fixes after the move

Images still load from wordpress.com or files.wordpress.com

Quick fix: Search the database for the old address and replace it with the new one, with a dry run first.

Why it happens: The importer downloads attachments and rewrites the main URLs, but sized versions, links to full images and CDN addresses such as i0.wp.com often stay behind. They keep working until the old site goes private, then they break.

  1. Take a backup of the new site database.
  2. Search for wordpress.com and wp.com across all tables.
  3. Run search-replace with a dry run, check the count, then run it for real.
  4. For images that never downloaded, upload them from the media archive and use a plugin that imports external images into the media library.
wp db search 'wordpress.com' --all-tables
wp search-replace 'https://yoursite.wordpress.com' 'https://example.com' --skip-columns=guid --dry-run
wp search-replace 'https://yoursite.files.wordpress.com' 'https://example.com/wp-content/uploads' --skip-columns=guid --dry-run

Posts imported but images are missing

Quick fix: Set the old site to Public, then run the importer again with Download and import file attachments ticked.

Why it happens: The importer fetches each image from the old site over the web. If the site is private, Coming Soon or the request times out, the post imports without its image.

  1. On WordPress.com set Settings → Reading → Site Visibility to Public.
  2. Re-run the import with the same XML file and the attachments box ticked. Existing posts are skipped.
  3. Compare the Media count with your audit.
  4. Upload anything still missing from the .tar media archive.

Old post links return 404 on the new site

Quick fix: Set Settings → Permalinks to match the old URLs (usually Day and name) and save.

Why it happens: WordPress.com uses dated URLs. A new install may use a different structure, so the same post lives at a different path.

  1. Open three old URLs and note the pattern.
  2. Set the matching permalink structure and click Save Changes, which also rewrites .htaccess.
  3. If you want a new structure, add the 301 rule from the redirects section.
  4. If every inner page 404s, the host may not read .htaccess; see our 404 fix.

The XML file is too large to upload

Quick fix: Raise upload_max_filesize and post_max_size, or run the import with WP-CLI.

Why it happens: Many hosts default to a small upload limit, and large blogs produce XML files well above it.

  1. Check the limit under Media → Add New.
  2. Raise it in the host panel or php.ini.
  3. Or split the export by date range on WordPress.com and import each file.
  4. Or upload the file by SFTP and use wp import.

Subscribers will not migrate

Quick fix: Connect Jetpack on the new site with the WordPress.com account that owns the old site.

Why it happens: Only the owner account can move subscribers. Agencies often connect Jetpack with their own account, which hides the old site from the list.

  1. In Jetpack, check which WordPress.com user the site is connected to.
  2. Have the client connect with the owning account, or transfer ownership of the old site first.
  3. Run the migration from cloud.jetpack.com on the new site.
  4. Allow up to a day for counts to update.

Email stopped after changing name servers

Quick fix: Add the MX, SPF, DKIM and DMARC records from your email provider to the new DNS zone.

Why it happens: Email routing lives in DNS. When the name servers changed, the old records went with the old zone.

  1. Get the required records from your email provider's setup page.
  2. Add them at the new DNS provider.
  3. Wait for the records to propagate and send a test both ways.
  4. Check SPF and DKIM pass with a mail tester.

12SEO checks after launch

None of the top guides covers this well, yet it is where rankings are kept or lost. Do these in the first week.

CheckHowPass when
Old URLsRun your audit URL list through a crawler or a bulk status checkerEvery URL returns 200, or one 301 to the right page
Search visibilitySettings → Reading on the new siteThe discourage search engines box is not ticked
SitemapOpen /wp-sitemap.xml or your SEO plugin sitemapLists all posts and pages
Search ConsoleVerify the new property, submit the sitemap, inspect a few key URLsPages get indexed with the new host
Titles and descriptionsCompare five top pages old vs newMatch, or are better
HTTPSLoad the site over http and httpsOne redirect to https, no mixed content
SpeedTest a post and the home pageNo worse than on WordPress.com

If the address changed (from .wordpress.com to a new domain), follow Google's site move guidance: keep the redirects in place, update internal links to the new domain, and update the links you control, like social profiles. Expect some movement in rankings for a few weeks while Google processes the redirects.

The same checks apply to any platform move. We use them in our Wix to WordPress and Squarespace to WordPress guides too.

13What it costs, and when to hand it off

The move itself can cost nothing beyond hosting if you are on the free plan and do it yourself. The running costs change shape rather than vanish.

ItemCost
HostingVaries widely by host and plan; pay for what the site needs, not the cheapest intro price
DomainYearly renewal at your registrar; a transfer usually includes one year of renewal
Site Redirect (only for .wordpress.com addresses)Yearly fee, shown at WordPress.com checkout
WordPress.com plan upgrade for export (optional)From US$9 for one month of Personal on monthly billing
JetpackFree plugin; paid add-ons only if you want them
Updates, backups, securityYour time, or a care plan

A small blog takes an afternoon if nothing goes wrong. A site with a custom domain, business email, subscribers and a few years of posts is a different job: the risky parts are the DNS switch, the email records and the URL checks, not the import.

If you would rather not run it, we do these moves on a fixed price. Our WordPress migration service is $500 for sites up to 10 pages and $750 for up to 20 pages, with larger blogs and stores quoted within 24 hours. Agencies get it under their own brand, and the site can go straight into a white label care plan from $25 a site a month. See all rates on our pricing page.

Need the full list? See our WordPress errors fix guide and the hosting, PHP and cPanel errors guide.

14FAQ

Can I convert a free WordPress.com site to self-hosted WordPress?

Yes. The free plan can export all content from Tools → Export, and the media library from Tools → Export Media Files. You import the XML file into a self-hosted WordPress site with the WordPress Importer. You do not need to upgrade unless you want plugin data or a full backup.

Will I lose my Google rankings moving from WordPress.com to WordPress.org?

Not if every old URL still works. With a custom domain and matching permalinks, URLs stay identical. With a .wordpress.com address you need the paid Site Redirect upgrade to send each old URL to the new domain.

How do I move my WordPress.com subscribers?

Install Jetpack on the new site, connect it with the WordPress.com account that owns the old site, then in cloud.jetpack.com open Subscribers on the new site and choose Migrate subscribers from another WordPress.com site. Download a CSV copy first.

Does my theme transfer from WordPress.com?

No. The export holds content only. If the theme is in the WordPress.org directory, install it on the new site and redo the colors, fonts, logo and templates. Some WordPress.com themes are not available elsewhere, so you may need a close match.

Do I have to transfer my domain away from WordPress.com?

No. You can keep it registered at WordPress.com and change its name servers to your new host. Transferring is optional, takes five to seven days, and is blocked for 60 days after a registration or transfer.

Why are images missing after I imported my WordPress.com site?

The importer downloads each image from the old site, so the old site must be public during the import and the Download and import file attachments box must be ticked. Re-run the import with the same file to fill the gaps.

Should I delete my old WordPress.com site?

Usually not. A Site Redirect only works while the old site exists, and a deleted .wordpress.com address can never be reused. Set it to Private instead if you are not using a redirect.

What is the difference between WordPress.com and WordPress.org?

WordPress.org is the free software you install on any host and control fully. WordPress.com is a hosted service that runs the same software for you, with limits on plugins and themes depending on the plan.

Md Abu Jubaer Piash

Founder and lead WordPress developer, Finest Web Geek

Piash has built WordPress sites for agencies since 2013. He and his small team have shipped 800+ projects, most of them in Divi and Elementor, all under someone else’s brand.

  • MSc, Computer Science and Engineering
  • Top Rated Plus on Upwork
  • 800+ projects since 2013

How we write: every post comes from our own client work and is checked against the official docs. We update posts when the tools change.

Got a build on your desk right now?

Send the brief today and get a fixed quote by tomorrow.