Moving from Webflow: exported code and hosted services.
The pages you see are only part of a Webflow website. Its forms, CMS and other services may rely on Webflow hosting even when you can export the code. Before moving, work through what you use and decide what to keep, replace or simplify.
Platform guidance reviewed 27 September 2026. Check the current provider instructions and your own agreement before acting.
Check the export route before choosing a host
Webflow documents code export for paid Workspace plans; a Site plan alone does not provide that entitlement. Its HTML, CSS, JavaScript and asset export does not preserve working hosted CMS, ecommerce, form processing, site search, localization or password protection. Inventory the services separately from the files. Webflow's code-export documentation.
There are three reasonable starting decisions: keep the Webflow arrangement, host a suitable exported implementation elsewhere with its dependencies replaced, or commission a new website. The right choice depends on what the business needs to operate and edit, not just whether a ZIP can be downloaded.
Build a dependency record
For each function you use, write down where it will run after the move and who will look after it. Agree a test that shows it works, such as sending a form and checking that the message arrives. If you do not know the answer yet, leave it open for the provider to confirm.
The table scrolls sideways on smaller screens.
| Function in the current site | Decision for the replacement | Evidence to request |
|---|---|---|
| CMS or regular publishing | Retain records and choose the future editing workflow | Reconciled content plus a representative create, review and publish demonstration |
| Forms or file uploads | Agree processing, recipient and upload restrictions | An authorized submission reaches the intended recipient and supports a reply |
| Site search | Define what visitors may search and what stays excluded | Representative results, empty results and restricted-content checks |
| Language or regional pages | Inventory every required version and its approver | Correct content, navigation and version relationships on each retained route |
| Store or payments | Scope the transaction system and data separately | Checks agreed with the commerce and payment owners |
| Password-protected content | Agree access control before making it available | Unauthorized access is blocked and intended users can use the agreed journey |
Protected material deserves an explicit decision: never publish it as open static content simply because it appears in an export. Keep the replacement private until the agreed access rules have been demonstrated.
Test the result beyond the page
Webflow's exported forms require a separate processing integration. Choose that receiving service deliberately, including account ownership and continuing costs. Webflow's guidance for forms on exported sites.
For an enquiry journey, check the form labels and validation, submit an authorized labelled test, confirm receipt and reply details, and verify what the visitor sees if the service is unavailable. A thank-you screen is one part of the journey; it is not proof of delivery.
Apply the same approach to embeds and bookings: follow the visitor's action through to the system that actually processes it. Identify who can fix an issue after launch.
Bring the URL rules as well as the visual files
Webflow provides a separate CSV route for importing and exporting 301 redirects. Retain those rules and verify how the receiving host will implement them. Webflow's redirect import/export guidance.
Use the URL move worksheet to record useful addresses, the proposed destinations and intentionally retired material. Keeping a useful URL can be simpler than changing it. Where changes are necessary, agree relevant destinations and test them after launch.
Settle ownership and operation before cutover
Confirm the domain registrar, DNS administrator, email service and renewal owners. Decide who approves the release, who applies the authorized connection change and how the prior working version can be restored.
Ask to try the editing arrangement as well as the public pages. If your team publishes regularly, they need to know they can create, review and update content on the replacement, however good the preview looks. Use the RFP requirements and responsibility workbook to compare those commitments consistently.
We design, write and build new and replacement business websites. If you need a CMS, migration work, commerce, membership or complex integrations, we need to agree that scope with you. Bring the list of services your current site uses, so we can discuss the website you actually need to run.
Create your Webflow replacement plan · Discuss the replacement requirements