You hit Export, and find out the word never meant what you thought.
On most hosted builders your five years of content comes out as a single XML file of blog text. The images point back at the host you're trying to leave, the design is gone, the contact forms and the store don't come, and every SEO setting you tuned resets to nothing. Meanwhile the subscription you're canceling keeps billing until it lapses, and the site itself disappears the moment it does. That's when most people learn what lock-in actually costs, and it's the worst possible time to learn it. This guide covers how to get your whole site out cleanly, how to check the export works before you need it, and what real portability, the kind a managed CMS like Devani builds in by default, actually looks like.
Three questions that tell you before you try to leave.
You don't need a technical audit to know where you stand. Answer these honestly and the situation is clear.
- Can you download the whole site as files and host it somewhere else? Not an XML dump of your blog posts, the actual site: pages, layout, images, in a form another host or developer could serve. On Wix the answer is a flat no, because the site relies on Wix's own infrastructure to run at all and can't be exported to another host. On Squarespace it's a qualified no: you get an XML file of page and post text, and nothing of your design, templates, store, or forms.
- Could you hand it to any developer tomorrow? If the only people who can change your site are the platform's own tools or the one agency that built it inside a proprietary page builder, that's lock-in wearing a friendly face. Real ownership means the files are standard enough that anyone competent can pick them up.
- If you stop paying, do you walk away with a working copy? This is the one that stings. On a proprietary builder, canceling doesn't leave you with a site you can move to a cheaper host. It leaves you with a partial dump at best, because the site was never a thing you had, it was access you rented. The safeguard you actually want is a platform that hands you a complete, open-format export any time you ask, so leaving means moving a working copy of the real site, not starting from zero.
The button exists on almost every platform. What comes out is the part they don't advertise.
Nearly every builder has an export function, which makes it easy to assume portability is handled. It usually isn't. Here's what each of the big platforms actually hands you, so you can plan around the gaps instead of discovering them mid-migration.
- Squarespace. Settings, Advanced, Import/Export gives you a WordPress-format XML file. It carries basic pages and blog posts with their text and image blocks. It does not carry your design or templates, your product SKUs and variants, form blocks, code blocks, calendar or map blocks, audio, or any custom styling. It's a content transfer to WordPress, not a copy of your site.
- Wix. There's no full-site export at all. You can copy your text out by hand and download your images one by one, but the site itself can't be moved to another host because it's built on Wix's proprietary stack. Leaving Wix means rebuilding, not moving.
- Shopify. Product, customer, and order data export cleanly as CSV, which is genuinely useful. The storefront theme, its Liquid templates, and your apps do not come with you. You keep your commercial data and rebuild the shop around it.
- WordPress. The best of the bunch on paper: it's your database and your files, and a self-hosted install is portable to any host. The catch is what's woven through it. A site built on a proprietary page builder like Divi or Elementor stores its layout in shortcodes that mean nothing outside that builder, so "your content" arrives at the next place as a wall of bracketed codes. Portable content, locked-in presentation.
A site you can't leave is a site you don't fully own, no matter whose name is on the domain.
How to get your whole site out, in the order that actually protects you.
Do it in this sequence. The single biggest mistake is canceling the old plan first, before everything is safely out and the new site is live.
- Confirm the domain is yours, at an independent registrar. If you registered your domain through the builder, move it to a standalone registrar you control before anything else. The domain is the one asset that carries your brand and your backlinks, and you never want it held hostage inside the platform you're leaving.
- Export the content in open formats. Pull everything the platform will give you: pages, posts, product data. Prefer open, portable formats you can read anywhere, HTML for full pages, Markdown for writing, JSON or CSV for structured data like products and form entries. If the only option is a proprietary format, that's a signal about how portable the platform ever intended you to be.
- Save the media separately. Exports routinely leave images pointing back at the old host's URLs, which break the day your account closes. Download the full media library to a folder of your own, at full resolution, so nothing depends on the platform staying online.
- Write down every URL and its redirect. List your live pages and where each should point on the new site. This becomes your 301-redirect map, and it's what preserves the search rankings you spent years earning. Skip it and every ranked page returns a 404 the day you switch.
- Rebuild and launch before you cancel. Stand the new site up, wire the redirects, point the domain, and confirm it's serving correctly. Only then cancel the old subscription. Overlap the two for a billing cycle if you can afford it; a few dollars of overlap is cheap insurance against a gap where your site is simply gone.
- Test the export before you trust it. An export you've never opened is a backup you don't have. Actually load the files, check the images resolve, read a few pages. The time to find out the export is broken is now, not the afternoon you're trying to close the account.
The four things you want out the door before you cancel anything.
Your content, in open formats
Text, pages, and posts as HTML, Markdown, or JSON, not trapped in a format only one platform reads. Structured data like products and form submissions as CSV. Anything you can open in a plain editor is anything you can move.
Your full media library
Every image at full resolution, in a folder you hold, with no link pointing back at a host that's about to shut your account. Media is the part exports quietly drop the most.
Your domain, registered in your name
Held at an independent registrar, not inside the builder. It carries your brand, your email, and your backlink history, and it should never be something a platform can hold to make leaving harder.
Your redirect map
Every old URL matched to its new home, ready to become 301 redirects. This is what carries your search rankings across the move instead of resetting them to zero.
The cleanest export is the one you never have to fight for because it was designed in.
Everything above is damage control after the fact. The better move is to not sign up for the trap in the first place. Devani, the CMS running this blog, is built so the exit is always open, and it's worth naming plainly against the platform you'd otherwise be leaving.
A proprietary builder
Convenient to start, expensive to leave.
- ✓ Fast to launch and genuinely easy for a first site
- × Export is partial at best: content only, no design, sometimes nothing
- × Cancel the plan and the live site is gone with it
- × Price rises land with no real room to say no
Devani
Managed, portable, and yours to walk away with.
- ✓ Export the whole site as HTML, Markdown, or JSON any time you want
- ✓ Plain-file architecture means that export is a working copy of the real site, not a lossy dump, no design or content left behind
- ✓ Fully managed with a genuinely free tier, then simple flat plans; your domain stays registered in your name the whole time
- × No one-click importer to pull a complex existing site in for you; you export from the old platform and rebuild, with the connected AI doing most of the reassembly
The reason the export is clean isn't a feature bolted on late; it's the architecture. Devani is database-free, so the whole site is already plain files, server-rendered semantic HTML rather than pages assembled on the fly from a database and a stack of plugins. Getting your site out isn't a lossy conversion from a proprietary store into some other format, because there was never a proprietary store to convert from. What you export is a working copy of the real site, which is why the exit stays genuinely open even though the hosting, SSL, and backups are all handled for you.
The one honest cost is the way in. There's no one-click migrator that ingests an arbitrary WordPress install, by design. You export your content from wherever it lives and rebuild on Devani, and the connected AI, your own ChatGPT or Claude account working inside the builder, handles most of the reassembly from the exported pages, posts, and metadata. It's more setup than flipping a switch, and it's the price of the pages being plain HTML the assistant can actually write, which is the same property that makes leaving easy later. If your current pain is specifically getting out of WordPress, what actually happens when you leave WordPress walks through that migration in detail, and the wider field of WordPress alternatives covers where else your content can land.
Can I export my website from Squarespace or Wix?
Partially, and it's worth knowing the limits before you rely on it. Squarespace exports a WordPress-format XML file with your page and post text and image blocks, but not your design, templates, store, forms, or custom styling. Wix has no full-site export at all: the site runs on Wix's own infrastructure and can't be moved to another host, so leaving means copying your text and images out by hand and rebuilding elsewhere.
What does "no lock-in" actually mean for a website?
Three things, concretely. You can download the entire site as files and host it somewhere else. Any competent developer, not just the platform's own tools, can work on it. And if you leave, you walk away with a complete, working copy rather than a partial dump. A platform that guarantees a full open-format export clears all three; most proprietary builders clear none of them.
Will my Google rankings survive moving to a new platform?
They will if you set up 301 redirects. Before you switch, list every live URL and map it to its new address, then implement those as permanent redirects on the new site. That passes the ranking signals from the old pages to the new ones. Skip the redirect map and every previously ranked page returns a 404 the day you cut over, and the rankings go with them.
What file formats should my website export to?
Open, portable ones you can open in a plain text editor: HTML for full pages, Markdown for written content, and JSON or CSV for structured data like products, orders, and form submissions. If a platform only exports to a format that one specific tool can read, treat that as a warning about how portable it ever intended you to be.
Do I really own my site if I built it on a website builder?
You own your content and your domain if you registered it independently. You usually don't own the site as a thing you can take with you: the design, layout, and functionality live inside the platform and stay there when you leave. That's the practical meaning of lock-in, and it's why the honest test isn't whether you paid for it, it's whether you can walk out with a working copy.
Own the exit before you ever need it.
The best time to check your site is portable is the day you build it, not the day you're trying to leave. Go look at what a site that exports itself in plain files actually feels like.