Downgrading from Webflow Enterprise: what breaks, and how to leave before renewal

Stepping down from an Enterprise plan is rarely a billing toggle. If the site grew into the higher limits during the contract, a downgrade forces you to either cut parts of the site or move the codebase before the notice date.

Every year, about sixty days before a Webflow Enterprise contract renews, a finance lead or VP of Marketing asks the same question: Can we just drop back down to the self-serve Business plan?

Sometimes the answer is yes. If the Enterprise contract was signed two years ago for a security review or a traffic spike that no longer applies, and the site itself is still small, stepping down can work. More often, the site has quietly grown into the Enterprise ceilings while nobody was counting, and the downgrade screen refuses the change until the site is cut back.

The five things that block a downgrade

Before you tell procurement to cancel the renewal, check the live site against the five limits that separate an Enterprise workspace from a self-serve plan:

1. CMS item and collection counts. If your collections hold more total items or more distinct collections than the self-serve tier allows, you cannot step the site plan down until you delete items and collections below the lower cap. Archiving items does not free the slot; they have to be removed from the CMS.
2. Page branching. Active branches inside the Designer must be merged or discarded before the workspace loses branching. More importantly, if two or more people rely on branches to work on campaigns without publishing each other's drafts, dropping to a single shared canvas reintroduces publish collisions immediately.
3. Single sign-on and granular permissions. Enterprise role permissions and SAML SSO do not carry down to self-serve plans. Every editor and contractor drops back to standard workspace roles.
4. Reverse-proxy paths and custom routing. If your Webflow site is mounted on a subpath behind your main domain or relies on Enterprise-only SSL and proxy headers, stepping down requires re-architecting how DNS and Cloudflare route traffic to the site.
5. Publishing and API rate limits. Automated syncs from Greenhouse, Lever, HubSpot, or an internal database that run comfortably under Enterprise rate limits can hit 429 throttling once the plan steps down.

Downgrading in place vs migrating off

Downgrade to Webflow self-serve

• Delete CMS items and merge collections until the site fits under the self-serve ceiling.
• Give up page branching and return to a single shared Designer publish queue.
• Lose SAML SSO and custom role restrictions across the workspace.
• Stay on the platform, with the same ceiling waiting the next time content grows.

Fits when the site is genuinely small and never needed the higher caps.

Migrate to Astro or Next.js, with Sanity

• Keep every URL, collection item, and reference in Sanity with no per-plan template cap.
• Use real Git branches and isolated Cloudflare preview URLs on every code change.
• Enforce access control through GitHub, Sanity roles, and Cloudflare Zero Trust.
• Pay once for the migration, then run on direct utility billing with zero annual platform lock-in.

Fits when the site has outgrown self-serve limits and you want off the annual renewal escalator.

Watch the contract notice window, not the expiration date

The most common mistake in an Enterprise exit has nothing to do with code. Most annual software contracts carry a 30-day or 60-day non-renewal notice clause: if you do not give written notice before that window closes, the contract auto-renews for another twelve months long before the actual expiration date arrives.

A typical Webflow to Astro migration takes four to six weeks. That means the time to scope the move is 75 to 90 days before your renewal date, not the week the final invoice lands.

How to run a pre-renewal exit cleanly

When a team comes to me ahead of a Webflow renewal, we run the move in four stages designed to eliminate cutover risk before the old contract ends:

1. Inventory the live site in week one. Crawl every public URL, export the CMS collections via the Data API, and list every form, script, and third-party integration. See what decides the cost of moving off Webflow.
2. Keep the design, rebuild the foundation. A pre-renewal exit is the wrong moment for a brand redesign. Rebuilding the existing site as clean Astro components and a structured Sanity schema keeps the scope fixed and the timeline predictable.
3. Verify parity on a staging URL. Before touching DNS, the entire site runs on Cloudflare with your migrated Sanity content, tested forms, and a verified redirect map. Your team tests the real pages and the approval loop while the Webflow site is still live. See how to protect SEO during a website migration.
4. Cut over DNS with buffer to spare. Point DNS to Cloudflare at least two weeks before the Webflow contract terminates. The 30-day hypercare window included with every migration watches search indexing, traffic, and forms across the transition.

What happens after cutover

Once the site is live on Astro, Sanity, and Cloudflare, you own the repository, the CMS dataset, and the hosting account directly. Read what a handover actually includes.

From there, your team can edit content in Sanity Studio, drive post text edits from Slack and Sanity Studio with the Everbase Agent, or use Continuous development for ongoing engineering with human QA on every deploy.

If you have a Webflow renewal coming up in the next quarter, check the numbers on the cost page, run the migration cost calculator, or send me your site URL and your renewal date. I will tell you within one business day whether we can comfortably cut you over before your notice window closes.