What to do before you cancel your Framer plan

Before you cancel a Framer site plan, save your CMS, assets, URLs, redirects and custom code, convert the live site, move DNS, and cancel last.

Published
Updated
Reading time
5 min
Deframer cover: “Save it all, then cancel.” Beside it, a list of CMS export, Assets, Redirects, Custom code and Cancel last with Cancel last selected
On this page6 sections

Cancel your Framer plan last, after everything you need is saved and the replacement site is live. Framer says that after you cancel, "your plan benefits will remain active until the end of the current billing cycle" (Framer Help), so you have until then. Before that date, export your CMS content, keep your original assets, record every URL, redirect and custom code snippet, and, if you're moving to code, convert the site while it's still published. Then switch DNS, confirm the new site works, and cancel.

The order matters because some steps need the live Framer site. Once it's gone, they're harder or impossible.

What happens when you cancel

Framer's cancellation article says the plan's benefits stay active until the end of the billing period, and the cancellation shows in the project settings and the Plans tab of your workspace settings (Framer Help). After that, the site falls back to what the free plan includes. Framer's pricing page lists custom domains on paid site plans, and users on Reddit report that after cancelling, the custom domain stops working and the site is served on its Framer subdomain instead (r/framer). Check Framer's help center for the current details for your plan.

On refunds, Framer's refund policy says you're entitled to one "if you cancel your subscription within 7 days of the initial purchase" (Framer Help).

The checklist

1. Export your CMS content

Framer says CMS content "can be exported using plugins into structured formats such as CSV or JSON" (Framer Help). Export every collection, even ones you think you won't need, and keep the files with your project.

If you convert the site with Deframer, the collections come along anyway: each becomes src/cms/<collection>.json with a schema module beside it. An independent export is still a good backup.

2. Keep your original assets

Collect the original images, videos, logos and font files you uploaded. Check font licences: a licence that covers your Framer site may not cover self-hosting the files.

3. Record every URL

Save a list of every page your site publishes. The quickest source is your sitemap, at https://your-domain/sitemap.xml. You'll use this list to test the new site and to catch missing pages before search engines do.

4. Write down redirects

Copy the redirects from your Framer site settings into a document, with their status codes. A Deframer conversion carries over the redirects your published site answers with into next.config.ts, but a written list lets you check.

5. Copy custom code and integrations

List everything in Site Settings, then Custom Code, and in page-level custom code: analytics, chat widgets, pixels, verification tags. Note where each form sends its submissions, and download any submissions you still need from wherever they're delivered.

6. Note your SEO settings

For your most important pages, save the title, description, social image and any indexing settings. If you use Google Search Console, note how the property is verified: an HTML tag lives in the site, while DNS verification doesn't depend on your host.

7. Convert the site while it's still published

If you're moving to Next.js, this is the step that can't wait. Deframer reads the published site, and it checks for your verification tag on the live page before you download the code. Convert the site, then add the tag in Site Settings, then Custom Code, publish, and download the .zip. The download is kept for 7 days after the conversion finishes, so save it somewhere permanent.

Turn on Include assets locally if you're leaving for good. Images, fonts and videos are then downloaded into the project's public/ folder instead of loading from Framer's CDN. CDN or local assets explains the difference.

The cutover, in order

The cutover in five steps: deploy to a preview URL, lower the DNS TTL, point DNS at the new host, watch for a few days, and cancel the plan last
The old site stays live until the new one is tested and serving: cancel last.
  1. Deploy the new site to a preview URL. Test every URL from your list, every form and each breakpoint. Deploying a converted Framer site covers the major hosts.
  2. Lower your DNS TTL a day ahead, so the switch spreads quickly.
  3. Point DNS at the new host and check that HTTPS works for every hostname you use.
  4. Watch for a few days. Check analytics, form deliveries and Search Console for 404s.
  5. Disconnect the domain in Framer and cancel the plan. Consider keeping the Framer project itself as your design source, if your plan allows it.

Keeping your SEO when moving off Framer goes deeper on the DNS and Search Console steps.

What to keep after cancelling

Item

Where it lives after the move

CMS records

Your export, and src/cms/*.json in a converted project

Assets

Your originals, and public/ if you converted with local assets

Pages and components

The converted project's src/views/ and src/components/

Redirects

next.config.ts in the project, or your host's config

Forms

src/site/forms.ts and a route per form, delivering to your webhooks

Custom code

Carried into the project's layout and routes; check each snippet

The design

Your Framer project, which you can keep

If you're staying with a builder

The same checklist applies if you're moving to Webflow, WordPress or another platform, except for step 7: there you'll rebuild the design, using your Framer site as the reference. Keep the Framer site live while you rebuild. If you're still choosing, Framer alternatives when you want to own your code compares the options.

Deframer is an independent tool, not affiliated with Framer. Converting is free; downloading a converted project costs one credit, $10 for one or less in packs, on the pricing page.

FAQ

What happens to my Framer site if I stop paying?

Your plan's benefits stay active until the end of the billing cycle, according to Framer's help center. After that the site has only what the free plan includes; users report the custom domain stops working and the site is served on its Framer subdomain. Check Framer's current documentation.

Should I cancel Framer before or after moving my site?

After. Keep the Framer site published until the new site is live and tested, so you have a fallback. Converting with Deframer needs the published site; downloading also needs your verification tag on it.

Can I get a refund if I cancel my Framer plan?

Framer's refund policy says you're entitled to a refund if you cancel within 7 days of the initial purchase. For anything else, check the policy or contact Framer support.

How do I back up my Framer site before cancelling?

Export CMS collections with a plugin as CSV or JSON, keep your original assets, save your sitemap and redirects, and copy your custom code. To keep the site itself as working code, convert it to a Next.js project with Deframer while it's still published.

Do I lose my Framer project when I cancel?

Cancelling a site plan isn't the same as deleting the project. Keep the project as your design reference unless you're sure you won't need it. Check Framer's help center for what each plan includes.

Keep reading

All posts
  • Deframer cover: “No export? Four ways out.” Beside it, four tiles, Rebuild, Snapshot, Converter and Reverse proxy, with Converter selected

    Export6 min read

    Can you export code from Framer?

    Framer has no code export. Here are the four real routes to your site's code (rebuild, HTML snapshot, converter, reverse proxy) and how to pick one.

  • Deframer cover: “To Next.js, step by step.” Beside it, a list of Framer, Next.js, TypeScript and Deploy anywhere with Next.js selected

    Migration6 min read

    How to export a Framer site to Next.js

    Export a Framer site to Next.js step by step: convert, compare, verify ownership and download an App Router TypeScript project, then check it.

  • Deframer cover: “Your portfolio, case by case.” Beside it, four tiles, Projects, Case studies, Contact form and Animations, with Case studies selected

    Portfolio6 min read

    Migrating a Framer portfolio to Next.js

    Migrate a Framer portfolio to Next.js: projects CMS, case studies, contact form and animations, with a checklist in the order you'll work.