Help for owners
I want to move my website's content to a different headless CMS and I am afraid of breaking it
Short answer
Moving to another headless CMS is a content-and-links job, not only a technical one. Content models differ, images and references have to be re-linked, and every page address should stay the same or redirect to its new one. Export everything first, list your page addresses, and keep the old system running until the new site is checked.
Does this sound like your situation?
- My CMS is getting too expensive or limiting and I want to leave, but I do not know what moves.
- My developer says the export will not fit the new system without rework.
- I am afraid my page addresses will change and Google traffic will drop.
- My team has built habits and templates in the old editor and worries about the new one.
- I do not know whether I can still get my content out if I stop paying.
Why does this happen?
Each system structures content in its own way
A headless CMS stores content as fields and entries that you define. The same article can be one long text field in one system and a set of blocks in another, so an export rarely imports cleanly and needs a mapping and a script, followed by a manual check.
Links between entries and images are easy to lose
Entries point at other entries, authors, categories and image files. If the files and the references are moved separately, pages can end up with missing images or empty sections.
Page addresses change if nobody plans for it
Google advises mapping each old URL to its new one, using permanent server-side redirects, avoiding chains of redirects, and keeping them for as long as possible, generally at least a year. It also says to expect ranking changes for weeks or longer while pages are recrawled.
Confirmed by developers.google.com
The site that reads the content has to change too
A website built on a headless CMS reads content through that system's API. Swapping the system means rewriting those reads, and any preview, search or webhook that was set up for the old one.
Editors, roles and workflows are not exported
Content can be exported, but who may publish, draft states, approval steps and scheduled posts usually have to be set up again in the new system.
What can I do about it today?
- Download your content while you still canUse the export feature of your current system and save the files, including every image, somewhere your company owns. Do not delete anything yet.
- List your page addressesAsk your developer or open your sitemap and save the full list of live addresses. This list is what protects your traffic later.
- Write down what editors do every weekPublishing, scheduling, translations, approvals. The new system has to cover each of them.
- Do not cancel the old subscription yetKeep it running until the new site has been checked page by page. Cancelling early removes your fallback.
- Check who owns the accountsMake sure the account for the old and the new system is in your company's name, not your developer's.
When should I bring someone in?
- The site earns leads or sales through organic search and you cannot afford a drop.
- You have several languages, many content types or thousands of entries.
- You cannot tell which parts of the site read from the CMS.
How do I handle it?
- Inventory the content modelI list every content type, field, relation, media file and address, and mark what has no equivalent in the new system.
- Script the move and repeat itContent is moved with a repeatable script, so it can be re-run on the latest data just before launch, not copied once by hand.
- Keep addresses stablePage addresses stay the same where possible. Where they must change, each old address gets a permanent redirect to its direct new one.
- Compare old against newI compare page counts, images, links and metadata between both versions before anything goes live.
- Switch with a way backThe old system stays untouched until the new site has run correctly, so the switch can be undone.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Will I lose my Google rankings?
Not necessarily, but Google itself says rankings can fluctuate for weeks or longer during a move. Keeping addresses stable or redirecting each old address to its new one is what Google recommends.
Can I move without my developer?
The export is yours to take. Rebuilding the site that reads the new system needs development work, and I cannot promise how a given export will map to a given system before I have seen it.
Should I move at all?
Only if a specific limit hurts. Write down what the current system cannot do, and check whether it can be solved where you are first.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.