Can you export a site from a website builder? Mostly not

The export landscape

Read each builder's own documentation, because this is exactly the claim that changes. The recurring shapes: an export that produces templates without content; an export that produces content in a proprietary structure needing an importer on the other side; an export gated behind a higher plan; and no export, on the grounds that the site is the product.

Mirroring works on all of them

Whatever the builder offers, the rendered site is public HTML, and public HTML can be fetched. One command gets you a browsable copy with rewritten links:

wget --mirror --convert-links --adjust-extension \
     --page-requisites --no-parent https://your-site.example
cd your-site.example && zip -qr ../site.zip .

What this preserves is what visitors see. What it cannot preserve is anything server-side — forms, member areas, checkout, scheduled content, or a CMS somebody edits.

Verify privately before anything changes

The step people skip, and the one that turns a migration from a gamble into a check. Publish the mirror to a private link and walk it before you touch DNS:

curl -X POST https://read.botook.ai/sites \
  -H "Authorization: Bearer otr_live_YOUR_KEY" \
  -F file=@site.zip

Now you can click every page, on a real URL over HTTPS, with the live site still serving. If the mirror is broken you have found out before your customers did.

What no migration path fixes

• Server-side behaviour. Forms, logins, carts and scheduling have to be rebuilt.
• The editing workflow. Whoever updated the site through a visual editor now needs a different way to update it.
• Analytics history. That stays behind unless the builder exports it.
• Redirects. Mirroring copies pages, not the rules that got people to them.

Then decide where it lives

A mirror is a snapshot, so it suits an archive, a hand-off, or a site that has stopped changing. Something you will keep editing wants a static-site generator and a real project. The private link is useful either way: it is where the decision gets made with the evidence in front of you.

Is mirroring a site allowed?

Your own site, yes. Check the builder's terms about automated access first — some rate-limit crawlers, and being polite about request rates is the difference between a mirror and an incident.

Will the mirror look identical?

Usually close. Expect breakage where the builder loaded content dynamically or served device-specific markup. Walking the private copy is how you find those.

Can I host the mirror here permanently?

You can — a zip becomes a multi-file site and expiry can be set to never. For something you will keep editing, a real project is the better home.

What about my custom domain?

Point it here after you have verified the mirror privately. Register the hostname, add the CNAME and TXT records, verify, and switch DNS last.

Keep reading