Will My CMS Pages Get Deleted When I Upgrade or Downgrade My Site Plan?

This is a question that causes a lot of anxiety for website owners. You have spent hours building out your content, your blog posts, your product listings, and your collection pages. The last thing you want is to lose everything because you changed your billing plan.

The short answer is no. Your CMS pages and your content will not be deleted when you upgrade or downgrade your Site plan. However, there are important limitations you need to understand depending on which direction you are moving. This guide covers every scenario so you know exactly what to expect

‍

Understanding the Two Types of Webflow Plans

Before we dive into what happens to your content, you need to understand the difference between Workspace plans and Site plans. This matters because they affect different things.

Workspace plans control your ability to design, export code, and use advanced design features like custom code and version backups. These plans are for you as the designer or agency.

Site plans control what happens when someone visits your website. They determine whether you can use a custom domain, how many visitors you can have, and crucially for this discussion, whether you can use CMS features at all.

When we talk about upgrading or downgrading, we are almost always talking about Site plans. And this is where your CMS content is affected.

Scenario 1: Upgrading Your Site Plan (Moving to a Higher Plan)

This is the happy scenario. You are growing. You need more features, more CMS items, or you want to add ecommerce functionality.

When you upgrade from a Starter plan to a paid CMS plan, or from a Basic plan to a CMS plan, your content is completely safe. In fact, upgrading only unlocks more capabilities. Any CMS collections you have already built will become fully editable and publishable. Any limits on static pages or collection items will increase.

The simple rule is that upgrading never deletes anything. It only gives you more access.

Scenario 2: Downgrading Your Site Plan (Moving to a Lower Plan)

This is where people get nervous. And rightfully so, because downgrading does come with restrictions. But here is the crucial truth. Your content is preserved. It is not deleted.

Webflow specifically designs their downgrade process to retain your data even when you move to a plan that no longer supports the features you were using. This is intentional. They want you to be able to come back and upgrade again without losing everything you built.

However, preservation is not the same as full access. Depending on what plan you downgrade to, you will face different limitations.

Downgrading from a CMS Plan to a Basic Plan

The Basic Site plan does not support CMS features at all. It is designed for simple static websites with up to two static pages and no dynamic content.

If you downgrade from a CMS plan to a Basic plan, here is what happens to your CMS content. All of your collection items and your CMS pages remain intact. They are not deleted from your project. However, you will not be able to add any new collection items. You will not be able to edit existing ones through the CMS interface. The collections are essentially frozen.

Your published site will still show your CMS content because the static generated pages are already published. But if you try to republish or make changes, you will run into limitations.

There is an important catch here. The Basic plan is not even available for purchase if your site currently has CMS collections or content editors. Webflow forces you to remove all CMS features before it will let you select the Basic plan. That means you cannot simply downgrade from a CMS plan to a Basic plan without first removing your CMS collections or converting them to static pages.

If you want to move to a Basic plan, you have two options. You can delete your CMS collections entirely and turn your dynamic content into static pages. Or you can clone your site first, keep the original as a backup with all CMS functionality, and use the clone for your Basic plan version.

Downgrading from a Higher CMS Plan to a Lower CMS Plan

If you are moving from a higher tier CMS plan to a lower tier CMS plan, the situation is more straightforward. Both plans support CMS features, but the lower plan has limits on how many collection items you can have.

For example, the basic CMS plan might allow 2,000 collection items while a higher plan allows 10,000. If you downgrade and you currently have 5,000 items, you will still have access to all 5,000 items. You can edit them, update them, and manage them. The only restriction is that you cannot add any new items until you reduce your count below the new plan limit or upgrade again.

Your existing content is completely safe. You just hit a ceiling on future growth until you either clean up old content or upgrade back to a higher plan.

Downgrading to the Free Starter Plan

The Starter plan is completely free but comes with severe limitations. You cannot use a custom domain. Your site is published on a webflow.io subdomain. And you are limited to two static pages.

If you downgrade from any paid plan to the Starter plan, here is exactly what happens to your content.

All of your static pages are retained, even if you have more than two. You will still see them in your project. However, you will only be able to edit the first two static pages. The rest become locked. You cannot edit them, and you cannot add any new static pages. But the content is not gone. If you upgrade again in the future, you will regain full access to edit all of those locked pages.

For CMS collections, the rules are similar. You will still have access to view and edit all of your existing collection items. You will not be able to add any new collection items. But everything you already created stays right where it is.

For custom code, any code you added through site settings, page settings, or embed elements remains intact on your published site. The embed elements still appear in your designer. But you lose the ability to view or edit that custom code until you upgrade again.

For ecommerce products, the same principle applies. All of your products remain. You can still edit existing products. But you cannot add new products.

The one major change when downgrading to Starter is that your site becomes unpublished. Your custom domains are removed immediately. Your site will no longer be accessible at your professional domain until you add a paid plan again.

Scenario 3: What Happens When You Export Your Code and Host Elsewhere

This is a completely different scenario. Instead of changing your Webflow plan, you are taking your website code and moving it to a different hosting provider like GoDaddy, Netlify, or your own server.

Webflow allows you to export your code at any time. You simply go to the Designer, click Export Code, and download a zip file containing your HTML, CSS, JavaScript, and images.

Here is the critical limitation you must understand. The export feature only includes static content. It does not include your CMS collections. It does not include your dynamic content. It does not include your ecommerce products. The export gives you the templates and the structure, but not the data that lives inside your CMS.

This makes sense when you think about it. Your CMS content is stored in Webflow databases. When you export static code, you are getting a snapshot of your templates, but the dynamic content that would normally be pulled from those databases is not included in the export.

If you want to move your CMS content to another platform, you need a migration strategy. You can use third party migration tools that connect to Webflow and your new platform, pulling your collection items and products across. Or you can manually recreate your content on the new platform. But simply exporting code from Webflow will not bring your dynamic content with you.

Scenario 4: Moving Your Site to Another Platform Like WordPress

This is a full migration scenario. You are leaving Webflow entirely and rebuilding or transferring your site to another content management system.

When you move to WordPress, for example, your Webflow CMS content does not automatically come with you. You need to use a migration service or plugin that can connect to your Webflow site, read your collection items, and create corresponding posts, pages, or custom post types in WordPress.

The good news is that migration tools can transfer your titles, your creation dates, your descriptions, your categories, your thumbnail images, and in some cases your product data if you are moving an ecommerce store. Some services also offer 301 redirects so that your old Webflow URLs automatically forward to your new WordPress URLs, preserving your search engine rankings.

Your Webflow CMS content is not deleted when you migrate. It remains in your Webflow project unless you manually delete it. But once you have fully moved to a new platform, you will likely want to cancel your Webflow hosting plan to stop paying for it.

Scenario 5: When CMS Content Actually Gets Deleted

Now for the honest truth. There are situations where CMS content can be lost. But they are not caused by upgrading or downgrading your plan.

The most common way to lose CMS content is accidental deletion by a user. If someone on your team deletes a CMS collection, that action is permanent unless you have a backup to restore from. Webflow does not have an undo button for collection deletion. Your only recovery option is to use the Backups feature in Project Settings to roll back to a previous version of your site before the deletion happened.

Another situation is when a plan is downgraded and then someone manually deletes collections thinking they are no longer needed. The downgrade itself does not delete anything. But a person can. Always keep backups or cloned versions of your site before making major plan changes.

Finally, if your subscription completely lapses or your account is closed, your data may eventually be purged. Webflow retains data for a period after cancellation, but you should not rely on this. If you cancel your paid plan, export your important content first or keep a cloned version of your site in another workspace.

Practical Tips to Protect Your CMS Content

Before you make any plan change, take these simple precautions.

Clone your site. Webflow allows you to create a complete copy of your project in your dashboard. This clone will have all of your CMS collections, all of your static pages, and all of your design work. If something goes wrong during your downgrade or upgrade, you have a perfect backup.

Export your collection data. While the code export does not include dynamic content, you can manually export your collection items as CSV files from the CMS panel. This gives you a spreadsheet of all your content that you can reimport later if needed.

Check your new plan limits before downgrading. Know exactly how many collection items your new plan allows. If you are currently over that limit, decide whether you want to delete old content to get under the limit or keep the overage and simply stop adding new items until you upgrade again.

Read the downgrade confirmation carefully. Webflow will warn you about what you are losing access to before you confirm the change. Do not click through without reading.

The Bottom Line

Your CMS pages and your collection items will not be deleted when you upgrade or downgrade your Site plan. Webflow preserves your data specifically so you can move between plans without losing your work.

However, downgrading does impose restrictions. You may lose the ability to add new items. You may lose the ability to edit custom code. You may lose the ability to use a custom domain. But your existing content stays intact.

The only time your CMS content is at risk is through accidental deletion by a user, failure to maintain backups, or complete account closure. Plan changes alone are safe.

If you are planning to downgrade to a Basic plan, remember that you must remove your CMS features first. If you are planning to export your code and host elsewhere, understand that your dynamic content does not come with the export. And if you are ever unsure, clone your site before making any changes. That one click could save you hours of rebuilding.

‍