Mozilla is shutting down Solo, its AI website builder and hosting service. According to the Solo shutdown FAQ, every Solo site, account, and piece of data is deleted on November 30, 2026, with no recovery afterwards. The Register reported that around 54,000 people had used it to build pages, many of them sole traders running a custom domain on top.
Mozilla did give notice (October 1) and an export. But read what the export actually contains: a ZIP with an HTML version of the site, a CSV of links to your images, and your form and newsletter submissions. The image files themselves are not in the ZIP; you download each one individually. Domains bought through Solo Domains have to be moved to a partner registrar through a support email. On X, one web designer summed it up in a single line: own your domain and keep your own backup.
This is not a post about Mozilla. Products end, and sixty days of notice is better than most. It is a post about the thing almost nobody checks when they pick an AI website builder: what you can carry out the door on the worst day. The generation step is the part everyone demos. The exit is the part that decides whether a shutdown is a weekend of work or a lost business.
The four things that have to leave with you
When a builder closes, gets acquired, reprices, or just stops fitting, four assets matter. Everything else can be rebuilt.
- The domain. Your URLs, backlinks, email deliverability, and every search result pointing at you hang off it. If the builder is the registrar, or holds the DNS, you are asking permission to leave.
- The content in a form you can edit. Not a screenshot of a page, not a giant compiled bundle. Text and structure you can move into another system without retyping it.
- The media. Images, logos, PDFs, and videos at original resolution. The Solo case shows how easily these get left out of an "export".
- The leads and data. Contact form submissions, newsletter sign-ups, bookings. For a small business this is often the most valuable thing on the site, and the most likely to live only in the vendor's dashboard.
A fifth item is quieter but expensive: your URL map. If the new site does not answer at the same paths, or redirect them, you throw away whatever search visibility the old one earned.
Run a fire drill before you need one
You do not need to wait for a shutdown email to find out whether you can leave. Here is a drill you can run in under an hour against any site, including one built with an AI website builder last weekend.
1. Confirm who controls the domain and DNS
whois yourdomain.com | grep -iE "registrar:|registrant (organization|email)" dig +short NS yourdomain.com You want the registrar account to be one you log into, and the nameservers to be somewhere you can change. If the registrar line names your site builder, find out today how a transfer works and how long the unlock takes.
2. Mirror the live site yourself
Don't rely only on the vendor's export button. Take your own copy of what visitors actually see:
wget --mirror --convert-links --adjust-extension \ --page-requisites --no-parent \ -e robots=off https://yourdomain.com/ Open the mirror offline. If pages render empty because content loads client-side, that tells you something important: your "site" is not portable HTML, it is an app that needs the vendor's runtime.
3. Pull every image, not just the references
If an export gives you a CSV of image URLs (as Solo's does), fetch them before the links die:
mkdir -p media # assumes the CSV has a column of image URLs; adjust the column number cut -d, -f2 images.csv | tail -n +2 | tr -d '"' | \ xargs -n 1 -P 4 wget -q -P media/ ls media | wc -l # compare against the row count of the CSV Compare counts. A missing logo or hero image is the kind of gap you only notice after the old host is gone.
4. Save the URL inventory
curl -s https://yourdomain.com/sitemap.xml | \ grep -oE "<loc>[^<]+</loc>" | sed -E 's#</?loc>##g' > urls.txt wc -l urls.txt This list becomes your redirect map later. Keep it next to the mirror. If there is no sitemap, build the list from the mirror's directory tree.
5. Export the leads and check they are complete
Download form and newsletter submissions as CSV and spot-check the newest rows against your inbox. Then ask the uncomfortable question: if form notifications stopped tomorrow, would you know?
What to ask before you pick a builder
The drill tells you where you stand. These questions keep you from ending up there again. They apply to any tool, the one we are building at PolyDraft included:
- Can I bring my own domain, and does it stay registered to me? Buying a domain through the builder is convenient. Make sure it is still in an account with your name on it.
- What format is the export, and does it include media? "HTML export" and "full export" are not the same thing. Ask whether original images come out in the archive.
- Where does form data live, and can it go somewhere I own? A webhook to your CRM, or at least an email copy of each submission, means leads survive the vendor.
- Can I set redirects? Leaving cleanly requires 301s. So does every restructure you will do while you stay.
- Is there a clear path when the product changes? Pricing, plan limits, and policies move. The answer you want is an export you have tested, not a promise.
We wrote a longer website migration checklist for the move itself: inventory, staging, cutover day, and the monitoring windows afterwards. If you are already comparing tools, our roundup of Lovable alternatives also has a section on moving a project off a builder you have outgrown.
Keep the structure portable, not just the files
The most durable sites survive a move because their structure was intentional: a small set of stable URLs, one page per real intent, and internal links that make sense without the builder's navigation component. If your URL scheme came from whatever the generator happened to output, you will be reverse-engineering it during a migration under deadline. A little up-front thought about site architecture for SEO is also what makes a redirect map short.
The short version
AI website builders have made the first version of a site nearly free. That shifts the risk somewhere else: to ownership. Before you point a domain at anything generated, check that the domain is yours, the content and media come out whole, the leads are stored somewhere you control, and you have a list of every URL you would need to keep alive.
If you have a Solo site, the deadline is November 30. If you don't, run the drill anyway. It costs an hour now and could save a business later.


