Skip to content
CloudWeld

01Move from Webflow

Move off Webflow onto a site you own outright.

Keep the content and design choices you have already made. We bring across your pages and CMS content, reconnect your forms and search, and set up how your team keeps publishing.

A Webflow move starts with two exports.

The code export gives us the static site, while Collection content comes out in separate CSV files. We bring the two together when we build your new site.

Code and design

Code export comes with eligible paid Workspace plans. It gives us the page structure and assets to work from while we recreate the design you approve.

Collections and files

Each Collection exports on its own. We map its fields and links, then download the images and files, because the CSV only points to copies hosted by Webflow.

Content and working features get their own checks.

A static export leaves out the functions Webflow hosts for you, so the preview has to show a working customer journey as well as the finished design.

Content and working features get their own checks.
Part of your siteWhat comes with youWhat we do
CMS collections Your entries and fields, with their published addresses. We map how entries relate and recreate the Collection pages and lists your visitors use.
Design and interactions Your brand, layouts and the interactions you want to keep. We rebuild them and check them on desktop and mobile.
Forms and search The information you collect and how visitors search your site. Webflow form handling and site search stop working once exported. We replace and test both.
Page addresses Your static and Collection URLs, with their page titles and descriptions. We keep addresses where we can and test a redirect wherever the structure changes.

What sits behind your Collections sets the price.

A set of articles with one layout is simpler than a directory with linked categories and filters, so we look at the content model alongside the pages it creates.

Relationships and archives

Show us how your Collection entries link to one another and which lists visitors use. That tells us which templates and checks the new site needs.

Languages and access

Tell us about translated or password-protected pages. Exported code drops password protection, so we settle how private content is handled before it reaches a preview.

Ongoing publishing

You will not have the Webflow Designer after the move. We set up the editor your team will use and write down which updates we handle.

Asked before leaving Webflow

Does the code export include my CMS content?

No. CMS content needs a separate Collection export. We match those entries to the pages on your live site, including content that links to another Collection.

Can you keep the animations?

Yes, the ones you want. We show them on the preview, and any custom interaction work is priced in the quote.

When can I end the Webflow subscription?

After launch. Keep the site and export access active during the build, and once your files and content are live on the new site, we tell you which subscriptions you can cancel.

Your proposal lists the website work, search setup and editing tools, with one fixed price. You keep the code, the content and your own accounts, and the monthly fee covers running it after launch.

How we scope the work

Moving from somewhere else?

Talk through your Webflow move.

Put in your Webflow address. We go through every page before we talk, then send a fixed price and a go-live date.

Or check your site first