01 | Separate content export, page export, and complete migration
CMS export often contains fields and text. Page export may include HTML, CSS, or static assets. Complete migration also restores hosting, forms, search, redirects, permissions, analytics, localization, and dynamic logic. Buying discussions must name the portability layer instead of asking only whether export exists.
Webflow documents CMS Collection CSV export while image and file URLs may remain tied to the source site. Framer explicitly states that complete published sites cannot be exported as HTML or static bundles for self-hosting. These are platform boundaries, not simple product-quality scores.
02 | Build a seven-part migration inventory
Inventory URLs and canonicals, CMS fields and relations, images and files, forms and submissions, site search, redirect rules, and third-party scripts and analytics. For each, record export format, owner, restoration method, and maximum acceptable downtime.
Evaluate commerce, memberships, accounts, and backend logic separately. A visual builder's page capabilities do not mean business state migrates with the page.
- Is there a complete public-URL list and redirect destination map?
- Do images, files, and fonts have independent backups and rights records?
- What replaces form submissions, search, and dynamic behavior?
03 | Put an exit drill inside the seven-day pilot
Do not wait two years to test export. During the pilot, build a homepage, one CMS template, and 30 real items, then export immediately. Sample five items and verify fields, links, rich text, and images can be restored elsewhere.
Record rebuild time as well. If migration requires design, engineering, and content teams, include those hours in renewal comparisons. Switching cost can exceed a year of subscription fees.
04 | Maintain portability after launch instead of taking one backup
Export CMS monthly or quarterly, retain original images and files independently, maintain the URL inventory, and update the exit plan when new third-party functionality is added. For high-traffic or revenue sites, test restoration at least twice a year.
Before cancellation, verify custom domains, publication state, retention, refunds, account deletion, and remaining term. Exit capability is not for constant migration; it preserves choice at renewal.