Bring your own site · 5 min read
How do I move my blog posts off WordPress without losing them?
The short answer
Export your posts first. In WordPress, Tools → Export → Posts gives you one file with every post, its category, tags, author and the address of its featured image. Then import that file, or the live site's address, into the new blog, check the preview, and keep each post's old address so links and Google rankings carry over.
On this page
What actually needs to move
When people say they lost posts in a move, they rarely mean the text vanished. They mean something around it did:
- The words, with their headings, lists and links.
- The images, both the featured image at the top and the ones inside the post.
- The dates. A post from 2021 that suddenly says it was written today misleads readers about how current it is.
- Categories, tags and authors, which is how readers find related posts.
- Each post's address. The one people forget, and the one that costs the most. A post that has earned Google visits for three years earns them at its address. Change it and those visits stop.
Keep all five in mind and the rest of the move is a checklist.
Get a copy first
Before you touch anything on the new site, take a copy of what you have. In your WordPress dashboard, go to Tools → Export, choose Posts, and download the file. It's an .xml file holding every post with its category, tags, author and dates, plus the addresses of the featured images.
Keep that file safe after the move, too. It's your record of the blog as it was, and if anything goes wrong you can start again from it. How to back up your website covers what else a usable copy contains.
One thing the file doesn't hold is the images themselves. It lists where each one lives on your old site. That matters for what you do next.
Two ways in: the file or the live site
Upload the export file. You hand over the .xml from the last step, and the new blog reads the posts out of it.
Point it at the live WordPress site. You give the new blog your blog's address, and it reads the posts straight from the site. This suits you if you can't get into WordPress's Tools menu, or if the person who set it up has gone quiet.
On Helm, plans with the Blog can do both, and an owner or editor runs the import from the dashboard's Blog. Reading a live site, it stays on that site's own address, asks for twenty posts at a time and waits a second between pages. It brings in up to 500 posts in one import.
Each post comes in with its tags, its author and its category (the first one, if it had several). You choose whether the posts arrive as drafts or published with their original dates, and a draft you publish later keeps its original dates too.
Check before anything is written
A good import shows you what it found before it changes anything. Look at the count, the titles, the dates, and whether each post has its cover.
Pay attention to posts flagged with no title or no text. These are often unfinished drafts, or posts whose content didn't come through the way it was laid out. Decide about each one now, while the old post is still there to compare against.
Helm reads everything into a preview first, and nothing is written until you say go. It flags posts with no title or no body and leaves them out of the import. So give each one its title or its text on the old site first, or add it by hand once the rest are in.
Keep the addresses
If a post lives at yoursite.com/blog/how-to-choose-a-cake, the move should keep it at exactly that address. Google ranks the address, other sites link to it, and people bookmark it. Keep it the same and all of that carries over.
When an address really can't stay the same, the fix is a redirect: a rule that sends anyone asking for the old address to the new one, and tells Google the post moved. Without one, the old address shows an error page, and the visits it earned are gone.
Helm keeps each post's slug, the last part of the address. When your old posts all sat under one path, such as /blog/ followed by the post's name, it reads that pattern so the new blog can keep it too. If your WordPress addresses carry a date, like /2021/03/15/how-to-choose-a-cake/, the new address keeps the name but not the date. Those are the addresses that need the redirect above, so check them before you switch the domain. WordPress's Settings → Permalinks shows which pattern your blog uses.
The address only matters if the domain comes with you, so make sure it does. What a domain name is, and why it should be registered to you, is worth reading first.
Images: copied, not borrowed
If your posts' images keep loading from your old WordPress server, they disappear the day you switch it off. They need to be copied into the new site.
Helm copies each image it can reach on the old site into your site's own media library, once, so the posts stop depending on the old server. It fetches them during the import, so keep the old site online until the import is done.
After the move: switch last
The order matters more than any single step:
- Leave the old WordPress site up and untouched.
- Import the posts, and check the new blog: open a handful of posts, old and new, and look at the images, the dates and the addresses.
- Only then point your domain at the new site.
- Keep the old site for a while after the switch, in case you need something you missed.
It's the same rule as any website move: build and check on the new side first, switch second, cancel the old one last. Can I move my website to a new host? walks through that order for a whole site.
A move is also a good moment to ask which posts are earning their place. Should my small business have a blog? has a short way to tell.
If your blog isn't on WordPress
The same steps apply, just with a different starting file. Helm's Blog can also take a Ghost export, an RSS or Atom feed, a set of Markdown files, with Arabic versions named like post.ar.md, or, for a site with no export or feed at all, the post pages listed in its sitemap.
