Skip to content
Wixy

What happens to your website if you leave

Before you buy a website, ask what you take with you if you leave: code, content, domain and history. The questions to ask, and how Wixy answers each one.

Wixy 4 min read

Almost nobody asks this before signing. They ask what it costs, how long it takes and whether it will look good. And the question that decides the most money three years later is a different one: what do I take with me if I leave?

On most platforms the answer is uncomfortable. That’s why nobody asks.

The hostage has four parts

A website isn’t one thing: it’s four. And each one can be held hostage separately.

1. The code. In a visual builder your website isn’t code: it’s canvas data, in a format only that builder understands. The “export,” when there is one, is a pile of generated HTML nobody can edit in any meaningful way. It’s a photograph of your site, not your site.

2. The content. The copy, the blog posts, the products with their prices and photos. If they live inside the canvas, they leave with it. If they live in a database with an API, they come out as a file and go into somewhere else.

3. The domain. The part people forget most, and the one that hurts most. If the agency registered yourbusiness.com in its own name, the domain is theirs, and with it your rankings, your business cards and your email. No export fixes that.

4. The history. Everything that changed, when and by whom. Almost no builder has it: they have an undo button that lasts one session.

The questions to ask before you sign

Copy them as they are:

  • Is the domain registered in my name, at a registrar I have access to?
  • Can I export the code in a format another team can keep editing?
  • Can I export the content (pages, posts, products, images) as JSON or CSV?
  • Are my images in a folder of my own, or mixed with other clients’?
  • What happens to the published site while I move?
  • Is the change history kept, or only the latest version?

If any answer starts with “well, actually…”, you already know.

How Wixy answers

We put it this way: managed, not locked in. And every part has its answer in the code, not in the contract.

Your website is real code. Astro files (the hero, the footer, the blog template) that any developer can open, read and change. When a client leaves, they take all their files with the full history: their team opens them with the platform’s command line, at any version, and if they want it all in one package, we put it together. It isn’t a photograph: it’s the website.

Your content lives in a database with an API. Pages, posts, products, categories, forms and their submissions come out through the API as JSON, and form submissions as CSV too. Images live in a folder that belongs to your account, separate from every other client, with their sizes already generated.

The domain is yours. You register it, in your name and at whichever registrar you prefer, and point it at Wixy. If you leave, you change where it points and that’s it.

Every change is a version. Who made it, when, with what instruction, which files it touched and what it cost. That history can be browsed, compared and restored, and the published version and the one before it are never deleted, whatever your plan’s retention says.

And meanwhile, your site stays up. Out of credits, plan paused or halfway through a move, what’s published stays published. On the free plan, your site lives at yourname.wixy.app forever, no card required.

Why we do it this way

Because it’s the only thing consistent with selling that your website is code. If the code were ours, “real code” would be a slogan. Since it’s yours, it’s a guarantee: the team maintaining it can be ours, yours or another agency’s, and the website is the same one.

And because a customer who stays because they can’t leave isn’t a customer: they’re a hostage. We’d rather have the ones who stay because the site works, because changes don’t break it, and because when something goes wrong, it goes back to how it was in seconds.

Before you leave anywhere, one piece of advice

Whatever the platform, do this today, calmly, and not on the day you leave in a hurry:

  1. Check at the registrar who is listed as the domain’s owner.
  2. Ask for a full export and open it. See whether what’s inside can be edited.
  3. Keep a copy of the content as JSON or CSV.

If those three things are in order, moving is paperwork. If not, don’t do it in a hurry: the one in a hurry is the one who pays. And if you’re comparing options, the pricing page answers this same question for every plan, and the security page explains how what’s yours is kept apart from everyone else’s.

← All posts

A website you can take with you, any day

Real code, content with an API and a domain in your name. Start free, no card.