A website on WordPress.com can be migrated to self-hosted WordPress hosting. In the process, the existing content is exported from WordPress.com and then imported into a self-hosted WordPress installation.
The switch gives you more control over the technical environment of your website. With a self-hosted WordPress installation, you can manage WordPress yourself within the limits of your hosting package, use themes and plugins, and have much more freedom in deciding the structure and functions of your website.
Briefly explained: While WordPress.com and a self-hosted WordPress website both use WordPress, they are not the same hosting model. When switching, therefore, a user account is not simply transferred. The new WordPress installation is set up with the hosting provider, and the existing content is subsequently migrated.
Difference between WordPress.com and self-hosted WordPress #
The designations often lead to confusion.
WordPress.com is a hosted service where the technical platform is provided and managed by WordPress.com or Automattic, respectively. Which features are available depends, among other things, on the plan used there.
At a self-hosted WordPress installation WordPress software is installed with a web hosting provider instead. This gives you significantly more control over the WordPress installation and the associated hosting environment.
CURIAWEB provides the hosting infrastructure, while you can manage your WordPress website yourself within the limits of your hosting package.
Why switch from WordPress.com to self-hosting? #
There can be various reasons for a change.
Typical reasons include, for example:
- more control over the WordPress installation
- free selection of suitable WordPress plugins
- more freedom with themes and customizations
- own hosting access
- direct access to files and database
- custom email addresses under the domain
- more options for custom functions
- WooCommerce or other extensive extensions
- more control over backups, PHP and technical settings
Whether a switch makes sense depends on your requirements. For a very simple website, WordPress.com may be sufficient. However, if more technical and design freedom is needed, a self-hosted WordPress installation can be the more appropriate solution.
What is actually transferred during the switch? #
In a classic WordPress.com export, primarily the website's content is exported.
Depending on the available content, this may include, among other things:
- Posts
- Pages
- Categories
- Keywords
- Comments
- Author information
- References to media files
- additional content data supported by WordPress
However, the export is not equivalent to a complete copy of the entire WordPress.com system.
Important: A WordPress export is not a complete server backup. Hosting settings, platform features, certain design settings, or features available exclusively on WordPress.com do not automatically transfer to an identical self-hosted website as a result.
Take inventory before moving #
Before you begin the migration, you should take a close look at the existing website.
Note or check in particular:
- which pages are available
- which posts have been published
- which categories and tags are used
- which domain the website uses
- which theme is being used
- which functions are required
- whether forms are available
- whether external services are integrated
- whether the website is already indexed by search engines
- which important URLs are currently used
This inventory will help you recognize later if anything is missing on the new website.
Custom domain or WordPress.com address? #
For planning the migration, it is crucial to know the address where your previous website can be accessed.
For example, a WordPress.com website can use an address in the following format:
meinewebsite.wordpress.com
However, an existing domain can also be used:
www.meinewebsite.ch
These two initial situations differ significantly in later domain and redirection planning.
If you are already using your own domain #
If you are already using your own domain on WordPress.com, it can generally also be used for the new self-hosted website.
To achieve this, the domain will later need to technically point to the new hosting or be managed accordingly.
How exactly the transfer takes place depends on where the domain is registered and how its DNS settings are currently configured.
Attention: Do not change the DNS settings of a live domain too early. Set up the new WordPress website first and check it as much as possible. Only after that should the domain be switched to the new environment.
If a wordpress.com address is used #
Does your website currently use exclusively an address like
meinewebsite.wordpress.com
Normally, do you need your own domain for the new self-hosted website if it is to be operated independently of WordPress.com?.
For example:
www.meinewebsite.ch
The old WordPress.com address doesn't simply belong to the new hosting and therefore cannot be transferred like a custom domain.
Prepare new WordPress installation #
Before the existing content can be imported, you need a new WordPress installation on your hosting.
This should basically work before you begin the actual content migration.
Check in particular:
- Domain or temporary accessibility
- WordPress installation
- HTTPS or SSL
- Admin access
- basic WordPress settings
Afterwards, the migration of the existing content can be prepared.
Export content from WordPress.com #
WordPress.com provides an export function for website content.
The exact user interface may change over time. Look for the website content export feature in your WordPress.com site administration.
Depending on the scope and available selection, you can export the desired content or the complete supported content.
WordPress generates an export file in WordPress's own exchange format.
You should save this file on your computer and keep it until the move is successfully completed.
What is a WXR file? #
For the export and import of WordPress content, the WordPress eXtended RSS-format, short WXR, used.
The corresponding export file usually has the file extension:
.xml
It contains structured information about the exported WordPress content.
However, the XML file is not a complete copy of the web server and should not be confused with a full website backup.
Do not edit the export file manually #
For a normal move, you should not unnecessarily modify the generated XML file with a text editor.
Incorrect modifications can cause subsequent imports to no longer function correctly.
Therefore, keep an unmodified copy of the original export file.
Import content into the new WordPress website #
Then log in to the admin area of the new WordPress installation.
Open:
Tools → Import data
There, WordPress provides various import options.
For a WordPress export, you use the corresponding WordPress importer. If this is not yet installed, WordPress can offer to install the importer.
Afterwards, you can select the previously exported XML file and start the import.
Assign authors during import #
During the import, WordPress may ask for the assignment of existing authors.
Depending on the import process, you can, for example:
- assign an existing user
- create a new user
- assign imported content to another user
Check the assignment carefully, especially if multiple authors have worked on the previous website.
Include media files on import #
During the WordPress import, the option can be offered to download and import attachments or media files belonging to the content.
This option is usually important for a full content migration.
However, the import of media only works if the corresponding files are still accessible on the previous website and retrieval is technically possible.
Practical Tip: Do not delete or deactivate the old WordPress.com website immediately after exporting. Leave it accessible at first until you have checked whether content and media have arrived completely on the new website.
Why might images be missing after import? #
A common difference between text content and media is that the XML file does not simply contain all original images as embedded files.
During the import, WordPress may attempt to retrieve the associated files from the previous website.
Problems can occur, for example, when:
- the old website is no longer reachable
- Files are not publicly accessible
- the import is interrupted
- a very large media library is available
- technical time or size limits are reached
- external image sources were used
Therefore, carefully check the media library and important pages after the import.
Is the WordPress.com theme automatically present on the new website? #
No, not necessarily.
A content import does not automatically transfer the complete technical and design environment of the previous WordPress.com website.
Whether the same theme is also available for self-hosted WordPress installations depends on the respective theme.
In some cases, the same or a similar theme can be installed. In other cases, the design must be newly implemented or adapted using a different theme.
Why does the new website look different after the import? #
This is not unusual.
Content and design are not the same in WordPress.
The appearance of a website is influenced, among other things, by:
- Theme
- Templates
- Fonts
- Colors
- Navigation
- Widgets or blocks
- additional CSS
- Plugins
- WordPress.com-specific features
A successful content import therefore does not automatically mean that the new website will look pixel-perfect like the previous website.
Plugins are not simply exported as well #
The WordPress export file is not a plugin backup.
Required plugins must be installed and configured separately on the new self-hosted WordPress installation.
Check which functions are actually still needed.
It does not make sense to equip the new website with numerous plugins just to replicate the old environment as closely as possible.
Check WordPress.com-specific features #
Certain features may have been provided directly by the platform on WordPress.com.
For a self-hosted installation, you must check whether:
- WordPress itself already offers a feature
- the used theme takes over the function
- a suitable plugin is needed
- the function is still needed at all
Therefore, use the move as an opportunity to clean up the existing website technically.
Test contact forms after the move #
If the previous website used contact or other forms, you should not take it for granted that they will work on the new website.
Check:
- whether the form is available
- whether all fields work
- to which email address messages are sent
- which technical sender address is used
- whether test messages actually arrive
- whether spam protection and data privacy requirements still fit
Control navigation and menus #
After an import, you should check the navigation of the new website.
Check in particular:
- Main navigation
- Footer Navigation
- Submenus
- Internal links
- Links to external websites
Depending on the theme and the WordPress structure used, it may be necessary to reassign or adjust menus or navigation blocks.
Check the permalink structure of the new website #
An important point with an existing website is the URLs of the individual contents.
Check the permalink settings of the new WordPress installation and compare important old and new URLs.
An unnecessary change of existing URLs can lead to:
- old links no longer work
- leading to external error pages
- internal links need to be adjusted
- search engines have to process new URLs
Important: If an existing custom domain and already indexed URLs are being migrated, you should retain the previous URL structure if possible. If URLs must be changed, appropriate redirects should be planned.
What should be considered when switching to a new domain? #
If not only the hosting but also the domain changes, the website URLs usually change as well.
For example, from:
www.alte-domain.ch/ueber-uns/
become a new address:
www.neue-domain.ch/about-us/
In this case, the migration should be planned not only technically, but also in terms of redirects, internal links, and search engines.
A domain change is therefore more extensive than a pure hosting change under the same domain.
Check internal links after import #
Posts and pages may contain links that still point to the previous website or old WordPress.com addresses.
Therefore, check particularly important internal links.
Links should point to the correct new destination addresses after the migration.
Don't forget downloads and documents #
Existing websites often contain other files besides images, such as:
- PDF documents
- Price lists
- Instructions
- Forms
- ZIP files
- other downloads
Also check these files after the migration and test important download links.
Check SEO data after the migration #
For an already established website, you should not only look at pages and posts.
Check among other things:
- Page title
- Meta descriptions, if used
- Headlines
- Permalinks
- internal links
- Image descriptions and alt texts
- Redirects
- Indexing settings
- XML Sitemap
A content import does not necessarily transfer all SEO settings from a previously used system or plugin.
Do not accidentally block search engines #
While preparing a new website, it can be useful to prevent its premature indexing.
Before the final launch, however, you should check that the finished website is not accidentally left blocked for search engines with a corresponding setting.
To do this, check particularly in WordPress:
Settings → Reading
and the search engine visibility setting available there.
Attention: A search engine block set during development is easily forgotten upon going live. It should therefore be part of your final migration checklist.
Control SSL and HTTPS #
The new website should be accessible via HTTPS.
Check after the domain switch, for example:
- whether the SSL certificate is valid
- whether the website is loaded via HTTPS
- whether internal resources are also loaded via HTTPS
- whether to show browser security warnings
Especially after a domain change, old HTTP or domain references can remain in content.
Only change the domain when the new website is ready #
If you want to continue using an existing custom domain, the actual switchover should happen as late as possible in the migration process.
Before that, at least the essential functions of the new website should be tested.
This includes, for example:
- Pages and Posts
- Images and Downloads
- Navigation
- Forms
- Plugins
- Theme and Depiction
- HTTPS
- internal links
Only after that should the domain point to the new hosting environment.
DNS changes take time #
Changes to DNS records are not necessarily visible everywhere on the internet at the exact same moment.
During a DNS change, it can therefore temporarily happen that different users or systems still reach different target servers.
This effect depends, among other things, on DNS caches and the TTL values used.
Therefore, plan a controlled switchover for a production website.
Don't forget your email during a domain transfer #
If email addresses are also used with your own domain, the mail configuration must be considered separately when changing hosts or DNS.
A website and a domain's email traffic are technically different services.
Changes to DNS settings should therefore not be made without first checking which entries are required for email.
Important: Do not blindly change all DNS records during a website migration. An incorrect change to MX, SPF, DKIM, or other mail records can disrupt email traffic.
Do not delete the old website immediately #
After the successful migration, you should not hastily delete the previous website or your previous access.
First, check whether everything is really there on the new website.
Check in particular:
- Contents
- Media
- Downloads
- Navigation
- Forms
- Redirects
- SEO-relevant settings
- Mobile view
Only when the migration has been verified and completed should it be decided which old services are no longer needed.
What happens to the old wordpress.com address? #
If you previously had an address like
meinewebsite.wordpress.com
you used, technically remains part of WordPress.com and will not be transferred to your new hosting.
If the old website is already receiving visitors or search engine traffic, you should check which redirection or migration options WordPress.com offers for your specific plan and situation.
Do not rely on a content import to automatically set up a redirection from the old WordPress.com address to your new domain.
Cancel WordPress.com only after the migration is complete #
If you use a paid plan or additional services on WordPress.com, you should not cancel them hastily.
First, make sure that:
- the export has been completed successfully
- the new website works
- the required media are available
- the domain is correctly set up
- necessary redirects have been clarified
- no data stored there is needed anymore
Then check the existing contracts and services at WordPress.com separately.
Can CURIAWEB handle the move? #
Depending on the starting point, a website relocation can range from a simple content transfer to a more extensive migration. Especially with an existing domain, a large amount of content, media, forms, or a website already established on Google, the transition should be carried out in a planned manner.
CURIAWEB offers a website migration service for Website migration service In the process, it can be checked which components of the existing website can be retained and how the transition to the new hosting environment can be carried out sensibly.
For a WordPress.com website, it is particularly important to know in advance which WordPress.com plan you are using, whether you have your own domain, and which features the previous website uses.
Checklist before leaving WordPress.com #
- Complete control over existing website.
- Clarify the domain used and domain management.
- Document important existing URLs.
- Capture required functions and forms.
- Export WordPress.com content.
- Store export file safely.
- Prepare new WordPress installation.
- Import content.
- Assign authors correctly.
- Check media files.
- Check theme and representation.
- Set up required plugins.
- Check navigation.
- Test forms completely.
- Check downloads.
- Check permalink structure.
- Check internal links.
- Check SEO settings.
- Check search engine visibility.
- Test SSL and HTTPS.
- Consider the e-mail configuration of the domain.
- Only switch the domain after the essential tests.
- Check the website again after the DNS switch.
- Do not prematurely delete or cancel the old website.
Fully test website after migration #
Do not access the new website only via the homepage after the switchover.
Test several important areas:
- Home
- important subpages
- Blog posts
- Navigation
- Contact page
- Forms
- Pictures
- Downloads
- internal and external links
- Mobile view
Additionally, check the WordPress admin area and look out for error messages or unusual notices.
Typical mistakes when migrating from WordPress.com #
- Treat WordPress.com and self-hosted WordPress as an identical hosting environment
- assume that the content export contains a complete website copy
- deactivating old website too early
- Do not check media files after import
- expecting the previous design to be automatically and completely adopted
- Overlooking WordPress.com-specific features
- Do not reconfigure plugins and forms
- Change permalinks without checking
- overlooked old internal links
- Do not check SEO settings
- Accidentally blocking search engines after launch
- Changing DNS settings too early
- Missed email DNS during domain transfer
- cancel old WordPress.com services before the migration is complete
When should you contact CURIAWEB support? #
If you are planning a switch from WordPress.com and are not sure which components can be transferred, the initial situation should be checked before the actual migration.
Particularly helpful in this regard are:
- Address of the existing WordPress.com website
- used own domain, if available
- current WordPress.com plan
- approximate number of pages and posts
- special features of the website
- used forms
- Information on whether the domain should also be transferred
- Information on whether e-mail addresses exist under the domain
You should not send passwords unsolicited via support message.
Summary #
Moving from WordPress.com to a self-hosted WordPress website is not a simple copy of a hosting account. First, the existing content is exported from WordPress.com and then imported into a new WordPress installation.
Posts, pages, categories, tags, comments, and other WordPress content can be migrated in the process. However, themes, plugins, platform features, and technical settings must be addressed separately and reconfigured if necessary.
Special attention is required for media files, forms, permalinks, internal links, SEO settings, SSL, domain, and email. If you are already using your own domain, the switch should only take place once the new website has been largely prepared and tested.
Do not immediately delete or cancel the previous WordPress.com website after exporting. First, fully check the new website and ensure that all required content and functions have been successfully transferred.
