Skip to content
SOSEI
Moving guide · Webflow

Move your Webflow website
to SOSEI

Webflow's code export leaves the CMS behind. SOSEI reads your live Webflow site instead, CMS pages included, and rebuilds it on its own hosting. This page says what comes along, what does not, and what to check about your domain, your email and your old addresses before you switch.

Step one is the free audit of your current site: no account, no email, no card. One free audit per visitor.

Why the Webflow code export is not the way out

Webflow can export a site's code. Its own plan page describes the export as HTML and CSS files for a dev team, lists it as a paid Workspace plan feature, and says that dynamic content, meaning CMS items and pages, cannot be exported. SOSEI does not use the export. It reads the public pages of your live site, and a CMS page is a public page like any other, so it needs no access to your Webflow account. Your Webflow site stays online and unchanged while you check the result.

The move in four steps

Your Webflow site stays live until the last one.

  1. Run the free audit

    Paste your address. The first audit needs no account, no email and no card, and it scores the site on Google search and on AI search separately.

  2. Start the rebuild

    Create an account and build from the same address. The 14-day trial needs no card. The crawl, the image copy and the build run on their own, and the new site is published on a SOSEI address.

  3. Check what came over

    The dashboard shows how many of your old pages were brought over and lets you add the ones left out. Change anything by chat or by clicking the text on the page.

  4. Connect your domain

    Add the records the dashboard shows at the company that runs your domain's DNS. Until you do, your old site stays live and the new one stays on its SOSEI address.

What is carried over from Webflow

Read from the public pages of your site, with the limits stated.

  • Pages and text

    The crawl reads up to 50 pages of your public site, fewer when a site only renders in a browser. A build writes up to 7 content pages straight away, and the rest of your old pages are added from the dashboard, up to 30 on the plan.

  • Images

    The images the crawl keeps are copied to SOSEI hosting, so the new site loads nothing from the old one.

  • Blog posts

    Articles are read on a budget of their own and become posts in the new site's blog. A post keeps its publish date when the old page states one.

  • Logo and brand

    Your logo, colors and tone of voice. The colors are also read from the logo itself.

  • Analytics and ad tags

    Google Analytics, Google Tag Manager, Meta Pixel, Hotjar, LinkedIn Insight, TikTok Pixel, Plausible, Umami and Microsoft Clarity are detected and carried over with the same IDs. The ones that set cookies fire only after a visitor accepts the cookie banner.

What does not come along

Better read now than found out after the switch. If your site depends on one of these, it is not ready to move yet.

  • Your Webflow design and interactions

    The layout is designed again around your brand. Your logo, colors and wording come along; the Webflow layout, its classes and its interactions do not. After the move you edit in the SOSEI studio, by chat or by clicking the text.

  • The CMS behind your pages

    What a Collection page shows is read from the public page, within the crawl's limits. The Collections themselves, with their fields and references, are not copied, and the Webflow CMS your team edits in stays behind. After the move, content is edited in the SOSEI studio.

  • Ecommerce, site search and password-protected pages

    Webflow Ecommerce and site search run on Webflow and are not rebuilt. Pages behind a Webflow password are not read.

  • Form submissions

    Submissions already collected by your Webflow forms stay in Webflow. Its plan page says they can be downloaded as a CSV: do that before you close the site plan. When the rebuilt site includes a contact form, new messages arrive in your SOSEI dashboard.

  • Online stores

    Your cart and checkout run on your current platform and do not come along. You can sell single products with Buy buttons that open your own Stripe or PayPal payment links; a shared cart and customer accounts are not offered yet, so a large shop should stay where it is for now.

  • Logins and member areas

    Pages behind a login are not read, and SOSEI builds websites, not customer accounts or member areas.

  • Fonts outside our library

    Fonts are self-hosted from a fixed library. A font that is not in it is replaced by the closest match.

  • Tags outside the list above

    A tracker that is not on that list, a Pinterest tag for example, is not carried over. Check the list against what your site runs today.

Your domain and your email

The domain is pointed, not transferred, and the records that route email are not part of the change.

  • Your domain is not transferred

    It stays registered in your name at your current provider. You add the A and CNAME records your dashboard shows, and the https certificate is set up automatically once they take effect.

  • Email is routed by other records

    Email follows separate records called MX. Connecting a domain to SOSEI changes only the A and CNAME records of the website, and SOSEI does not host mailboxes. Mail keeps arriving as long as your MX records name a mail server that stays in service, so look at where they point before the switch.

  • The dashboard says where to log in

    The domain step names the company that runs your domain's DNS when it recognizes it, and links to its login page. Rather not touch DNS yourself? Send a message from the dashboard and we connect it together.

  • The records you added for Webflow

    Webflow's plan page describes a custom domain as a domain you own, connected to the site. The records that connect it sit at the company that runs your domain's DNS, and that is where you replace them with the ones your SOSEI dashboard shows. Delete the old A, AAAA and CNAME records on the root before you add the new ones, and replace the www record instead of adding a second: a leftover record keeps some visitors on the old site.

  • Find out where your email runs

    Nothing in the move tells SOSEI where your mailboxes are. Before the switch, look at the MX records at your DNS provider. If they name a mail provider, replacing the website records does not affect them. If they name your bare domain or www, mail is delivered to wherever the website records point: change the MX to your mail server's own name first.

Your old addresses

Links and search results point at the addresses your Webflow site has today. This is what each of them does once the domain serves the new site.

  • An address that still exists is kept

    A page built at the same address answers at the same address. Nothing to redirect.

  • A changed address gets a 301

    When a page's address changes in the rebuild, the old one answers with a permanent (301) redirect to the new one. Imported blog posts get the same.

  • A page left out goes to its closest match

    An old page the build did not carry redirects to the closest built page above it, and an old privacy or terms page to the new one. Pages are never sent to the home page in bulk; one with no close match is left as not found.

  • You see what each known address will do

    The domain step lists your known old addresses: kept, redirected, or not found. You can rebuild a missing page or ask the editor chat for a redirect of your own.

Redirects you set up in Webflow's own redirect settings live in Webflow, and the crawl cannot see them. Ask the editor chat to add the ones you still need.

Nobody can promise rankings. That is Google's decision. What a move controls is whether each old address still answers.

Moving from Webflow: questions

Can I export my Webflow site and import it into SOSEI?
No export is needed. Webflow's plan page describes its code export as HTML and CSS files and says that dynamic content, meaning CMS items and pages, cannot be exported. SOSEI reads the public pages of your live site instead, so all you give is the address.
Will my Webflow CMS content come along?
What your Collection pages show is read from the public pages and comes along within the crawl's limits. A Collection page the crawl recognizes as an article, by an address such as /blog/ or /post/ or by the page's own article markup, becomes a post in the new site's blog; the others are treated as ordinary pages. The Collections themselves, with their fields and references, are not copied, and content is edited in the SOSEI studio after the move.
Will my Webflow site go offline during the move?
No. The crawl only reads your public pages. Your Webflow site stays as it is until you point your domain at the new one, and you decide when that happens.
What do I change at my domain provider?
Only the website records. Your domain stays registered where it is; you replace the records that connect it to Webflow with the A and CNAME records your SOSEI dashboard shows, and leave the rest alone.
Will my email keep working after I leave Webflow?
That depends on your MX records, not on Webflow or SOSEI. Connecting your domain changes the website records only. If your MX records name a mail provider, nothing changes for your mail. If they name your bare domain or www, change them to your mail server's own name before the switch.
Can SOSEI rebuild my Webflow Ecommerce store?
Not today. Cart, checkout and payments are not rebuilt, so a site that depends on them should stay on Webflow for now. The free audit still works on it.
Will I lose my Google rankings when I move from Webflow?
Nobody can promise rankings. That is Google's decision. What SOSEI does: an old address stays, or redirects with a 301 to the matching new page, and the domain step lists the ones that would break so you can fix them. Redirects you set up in Webflow have to be added again.

Start with the audit.

The first audit is free and reads your Webflow site as it is today. The move itself starts only when you decide to rebuild, and your domain moves only when you connect it.

Run the free audit