Migration guide · Updated July 2026

Move from Webflow without losing the parts that make your site work.

Eligible paid Workspace plans can export HTML, CSS, JavaScript, and assets. CMS content can be exported separately, but hosted functions do not keep working off Webflow.

Migration method
Partial export + rebuild
Planning level
Detailed planning
Old site stays live
Until final checks pass

What the export really gives us

A website export is rarely the whole website.

Webflow code export is a useful starting point for static pages. Forms, search, CMS behavior, user accounts, ecommerce, localization, password protection, and code components require replacement or a rebuild.

What we can carry over

  • Static HTML, CSS, JavaScript, and assets from eligible code export
  • CMS and ecommerce records exported as CSV
  • Page content and most static visual details
  • Domain and DNS configuration

What we recreate or reconnect

  • WordPress editing experience
  • CMS templates and dynamic queries
  • Forms, search, memberships, ecommerce, and password protection
  • Localization, redirects, analytics, and integrations

The replacement does not have to be WordPress

A Webflow site whose job is explaining services can be rebuilt as a custom static site instead.

How we choose between WordPress and static

Prepare the handoff

Gather this before we start.

You do not need to understand all of it. Tell us what you can access and where you get stuck.

  • Webflow Workspace and site access
  • The code export ZIP if the Workspace plan supports it
  • A CSV export for every CMS and ecommerce Collection
  • Form submission exports and a list of notification recipients
  • Custom code, integrations, redirects, localization, and domain settings

Instructions for Webflow

What to do in your current account.

  1. In the Webflow Designer, open the main menu and choose Code export, or press Shift + E.

  2. Choose Prepare ZIP and download the resulting file. Code export requires an eligible paid Workspace plan, not only a Site plan.

  3. Open each CMS Collection and export its items as CSV. Export ecommerce Collections and user account data separately if applicable.

  4. Export form submissions, then record form notification addresses, success messages, redirects, spam controls, and file-upload behavior.

  5. Copy custom code from site settings and page settings. Record third-party scripts, analytics IDs, cookies, and consent tools.

  6. Export the redirect list and inventory every localized or password-protected page before changing DNS.

Platform instructions: We checked this guide against Webflow: How do I export my site code? (opens in a new tab) on July 21, 2026. Builder menus and plan rules can change, so use the linked provider article if a label in your account looks different.

How 330 Hosting handles the move

We rebuild first. We point the domain last.

  1. 01

    Inventory first

    We crawl the public site, list its URLs, record forms and integrations, and separate the domain, DNS, website, and email services.

  2. 02

    Build away from the live domain

    We create the replacement without changing the website visitors currently see. Your old site stays available during the work.

  3. 03

    Review the jobs that matter

    You check the words, photos, navigation, forms, calls, bookings, store behavior, and mobile layout. We correct issues before launch.

  4. 04

    Copy DNS and launch

    We preserve mail and verification records, point only the needed website records, enable SSL, and test both the old and new paths.

  5. 05

    Watch and verify

    We check forms, analytics, redirects, indexing controls, error pages, and email delivery after the change. Only then should the old website plan be canceled.

Three things to check twice.

  • A Webflow Site plan alone does not include code export.
  • Exported forms and site search do not function without replacement services.
  • Collection pages in the code export do not include live CMS-bound content.

Migration help

Tell us what the site needs to do for your business.

The live pages are only part of the job. We need to know where leads go, what customers can do, what advertising depends on the site, and what cannot break.

Hosting is $15 per month.

There is no migration fee.

Do not send passwords. We’ll arrange secure access after we review the request. Fields marked required are required.
Website migration request details
Does the current website produce leads or sales?

This tells us which forms, phone numbers, tracking, and high-traffic pages must be protected.

For example: contact form to two email addresses, phone calls tracked by Google Ads, Calendly bookings, or Shopify orders.

What must the new site do?

Select everything you currently use or want to add.

Include important page names, current problems, advertising, deadlines, and what you want the rebuilt site to do better.

By sending this form, you agree that 330 Hosting may contact you about this request. See our privacy policy.

Questions that are the same for every builder

Whether the site goes offline, what happens to email and the domain, and how the $0 migration fee works are answered once, on the migration overview.

Read the migration questions