How to Cancel Framer and Keep Your Site Online

1. Export while the site is still live

The exporter reads the published URL. That URL has to be up, which means this step happens before anything is cancelled.

Export in full-site mode so every page is captured, not just the homepage. Check the file list against your Framer page list before moving on.

2. Deploy to a staging URL first

Deploy the export to the host's own subdomain — the .pages.dev or .netlify.app address — and leave your real domain alone.

This is the step people skip, and it is the one that catches broken internal links, missing config, and 404s on every page but the homepage.

# every page returns 200?
for p in $(grep -ohE 'href="/[^"]*"' *.html | sed 's/href="//; s/"//' | sort -u); do
  printf "%-40s " "$p"
  curl -s -o /dev/null -w "%{http_code}\n" "https://your-site.pages.dev$p"
done

3. Verify the pages that are easy to forget

The 404 page itself. Visit a URL that does not exist and confirm you get your own page and a real 404 status, not the host's default and not a 200.

Forms. An exported form posts to whatever the markup says, which is usually nothing. Repoint it at a form service or your own endpoint before launch.

Anything behind a CMS. Confirm every CMS detail page exists as a real file, not just the index that listed them.

4. Move DNS, then wait

Point the domain at the new host and let the certificate issue. Confirm HTTPS works on both the apex and the www variant.

Leave the Framer plan active through this window. It costs one more cycle at most, and it is your rollback.

5. Cancel, once the new site has served real traffic

Give it a few days of live traffic and check the host's logs or analytics for 404s you did not anticipate.

Then cancel. Keep the export archived somewhere that is not the deploy target — the deploy target is not a backup.