Updated 8 min readBy The AI-Hosted team

How to Migrate Off an AI Website Builder

Signs it is time to leave an AI website builder, what Wix, Framer, Lovable, Bolt and Webnode let you take with you, and how to move without downtime.

Short answer

First find out what your builder lets you take with you. Lovable and Bolt hand over the source code, Wix and Webnode keep sites on their own servers, and Framer's help center currently gives two different answers. If you get code, build it and host it elsewhere. If you do not, have an AI rebuild the site from your live pages, check it on a temporary address and move the domain last.

Rebuild it, then move the domain

Upload the rebuilt or exported site, check it on a temporary address, and switch your domain only when it is right. 14 days free, no card.

Leaving a website builder is a bigger decision than joining one. The builder that got your site online in an afternoon also holds its pages, its forms and often its domain, and getting all of that out is rarely a single button. This guide helps you decide whether to move, shows what each popular AI website builder lets you take with you, and walks through a move that keeps the old site online until the new one is ready.

A disclosure first: AI-Hosted is a hosting platform, powered by VibeDeploy, so we are on one side of this choice. Builders are the right home for a real set of sites, and the section on staying says when. If you are not migrating but choosing a first home for a new site, the overview at AI hosting vs website builders compares builders, publish buttons, classic hosting and AI hosting side by side.

Signs it is time to move

One frustration is usually not enough. Two or more of these, and no feature release will fix them:

  • You already edit with an AI elsewhere. You draft every change in ChatGPT, Claude or Cursor and then retype it into the builder's editor. The builder has become a slow copy of work done somewhere else.
  • The template is the ceiling. The layout you want, a calculator, an interactive map: the builder's blocks cannot express it, and no prompt inside the builder gets past that.
  • You need parts the builder does not run. A real database, a small API or a background job that should live next to the site, under your control.
  • The price no longer matches the use. You pay for a suite of marketing, booking or shop features and use one of them.
  • The site has to outlive the vendor. Builders change plans, rename tiers and occasionally close. Hocoos is a recent example: its help center announced the builder was being discontinued, with an official shutdown date of 23 April 2026, and gave owners from 23 March to that date to export their sites.

What each builder lets you take with you

What you can take decides what kind of move you face. This is what each builder's own documentation says, checked on 13 October 2026:

Builder What you can take with you
Lovable The full source code: Download codebase saves the project as a ZIP on paid plans, and Git sync to GitHub, GitLab or Bitbucket works on all plans
Bolt The full source code: open the project, click its title, then Export > Download for a ZIP, or connect the project to GitHub
Wix No site to take: Wix says a Wix site has to be hosted and operated on Wix's servers, while the content you build there belongs to you
Webnode No source files: Webnode says it does not provide access to the source files or code, so the site cannot move to another hosting provider
Framer Two answers: one help article says Framer does not offer HTML export for self-hosting, while its data portability article says you can download the published HTML, CSS, JavaScript and assets at any time. CMS content exports to CSV or JSON through plugins
Durable No website export that we could find in its help center on 13 October 2026; customer contacts export as CSV
Hocoos Closed: during the 30 days before the shutdown, owners could download a full HTML copy of their site and their files and data

The builders split into two groups. Developer-facing tools such as Lovable and Bolt generate a real code project and hand it over. Builders aimed at people who never want to see code keep the site in their own format, and leaving them means a rebuild. Framer sits in between until its documentation settles on one answer, so open your own project and check what it offers before you plan.

Move 1: you have the code

If you could download the project or sync it to GitHub, the move is mostly mechanical.

  1. Build it. A code project from Lovable or Bolt usually contains a package.json. Run npm install and npm run build on your computer and look for the dist or build folder. That folder is the website; the rest is the recipe for making it. AI-Hosted refuses an unbuilt project, because a browser cannot open it.
  2. Upload the build, or connect the repository. Drop the dist folder into the dashboard, or connect the GitHub repository so every push builds and deploys again.
  3. Check what stays behind. The code moves; the builder's own backend does not. Lovable's built-in Cloud backend (database, authentication, storage and functions) and a Bolt database stay with those builders unless you move them. Your AI can rebuild those parts on AI-Hosted: static sites and single-page apps are served directly, and a site can also run containers next to it (your own server, Postgres, MySQL, Redis or workers; up to 6 services with 2 CPU and 2 GiB in total), deployed by your AI through the MCP tool deploy_app and isolated with gVisor. Container data is not yet included in snapshots.

Move 2: you rebuild with an AI

Without code, you rebuild, and an AI does most of the typing. What makes a rebuild go well is preparation, not prompting.

  1. Collect the content. Copy the text of every page into a document, page by page, and download every image you own the rights to. Note the address of each page, the menu structure and every form with its fields.
  2. Give the AI the whole picture. Paste the content and the structure into the AI you like to work with, describe the look in words or with screenshots, and ask for the site as plain web files: one HTML file per page, a stylesheet and a script.
  3. Keep the addresses. Ask for the same page addresses the builder used where you can, such as /about and /contact, so links and bookmarks that people saved keep working.
  4. Compare page by page. Open the old and the new site side by side and check every page, image and link. Rebuilds rarely lose the big things; they lose a footer link or a phone number.
  5. Replace the builder's features. For a contact form, the forms relay emails each submission to you; an AI connected over MCP switches it on. Bookings, shops and member areas need a dedicated service or a deliberate rebuild, so decide on those before launch day, not after.

Rebuild it, then move the domain

Upload the rebuilt or exported site, check it on a temporary address, and switch your domain only when it is right. 14 days free, no card.

Move without downtime

Whichever path you took, the switch follows the same order, and the old site stays online until the end.

  1. Publish the new site on a temporary address. On AI-Hosted it goes live at an ai-hosted.com address the moment you upload it, so you can test it on your phone and send it to a colleague while the builder still serves your domain.
  2. Free the domain if the builder sold it. A domain bought inside a builder may have to move to a registrar first. Bolt locks the domains it sells for 60 days after purchase, and Replit points to the same 60-day ICANN wait before a transfer to another registrar; check your builder's terms before launch week.
  3. Point the domain at the new host. Add the domain in the dashboard, create the TXT record that proves ownership and the routing record it shows, and click Verify. HTTPS is set up automatically. Custom domains for AI-built websites explains the records and lists what each builder expects.
  4. Cancel the builder last. Keep the old plan until the domain answers from the new host everywhere and you have every file and form entry you need.

When staying is smarter

A move is not automatically progress. Stay on the builder when:

  • Non-technical colleagues edit the site visually. A drag-and-drop editor that people already know is worth a lot, and there is no such editor on the other side: changes go through the AI or the files.
  • The site runs on suite features. Built-in booking, a product catalogue, member logins or email campaigns are real systems. Rebuilding them is a project, not an afternoon.
  • One vendor, one bill is the point. For a small business that wants a single support desk and never thinks about the site, the builder's convenience is the product.
  • Nothing is actually wrong. If the site does its job and the builder's limits never get in your way, keep it and spend the effort on content instead.

What the move costs

On AI-Hosted the 14-day trial needs no card and includes one site with your own domain, which is enough to rebuild a typical builder site and compare it with the original before the domain moves. After the trial, plans cost EUR 4, 15 or 39 a month; prices include VAT where it applies, and the pricing page lists what each includes. To see what a finished, properly live site looks like, read what is an AI-hosted website, and for the full path from a prompt to a running site, how AI-hosted websites work.

Sources

All vendor pages fetched on 13 October 2026.

From the AI-Hosted team

Put your AI-built site on a real domain

AI-Hosted, powered by VibeDeploy, runs your AI-built website on European infrastructure with a custom domain, automatic SSL, forms and analytics. The 14-day trial needs no card.

Questions people ask

Can I export my site from an AI website builder?

It depends on the builder. Lovable and Bolt let you download the source code or sync it to GitHub. Wix says its sites have to run on Wix's servers, and Webnode says it does not provide the source files, so leaving those means rebuilding. Framer's help center currently gives two different answers, so check inside your own project.

How do I move a Wix or Webnode site to another host?

By rebuilding it. Neither hands over a site you can host elsewhere, so give an AI your live pages, texts and images, ask for a new version as plain web files, check it on a temporary address, then point your domain at the new host. Wix states that the content you build there belongs to you, even though its format does not travel.

Will I lose my domain if I leave the builder?

No, as long as the domain is registered to you: you change its DNS records to point at the new host. If you bought it through the builder, you may need to transfer it to a registrar first. Bolt and Replit both mention a 60-day wait after purchase before a transfer to another registrar.

What happens to forms, bookings and shop features?

They stay with the builder. On AI-Hosted, a forms relay can email contact-form submissions to you, and your AI can run your own server or a database in a container next to the site. A booking system or a shop usually means a dedicated service or a deliberate rebuild.

When should I stay on my AI website builder?

When non-technical colleagues edit the site visually every week, when it leans on built-in booking, shop or membership features, or when the builder keeps the site in a format you cannot take with you and the site does its job. A migration costs real effort, so make sure it solves a real problem.

Related reading