FREEFirst project with us? Your landing page design is on the house.See the offer
Booking for Q4'26

Strapi to Webflow, no server to babysit.

Strapi gives you an open source CMS you control. It also gives you a database, a server, upgrades and a front end to look after. If all of that only runs a marketing site, we can move your content into Webflow and turn the rest off when you are ready.

  • Collection types and relations mapped to Webflow collections
  • Dynamic zones and components rebuilt as Designer sections
  • Other API clients checked before anything is shut down
★★★★★5.0Trusted by ClanX, Petavue, Tata and more

Plan my Strapi move

Tell us a little. We reply within one working day with a price and timeline.

🔒 No spam. No sales calls unless you ask for one.

Got it. Thanks!

We will reply within one working day.

A Strapi to Webflow migration exports your entries and media, maps collection types and relations to Webflow collections, turns dynamic zones into Designer components and replaces the separate front end. Changed URLs get a 301. It fits teams running Strapi just for one website. If other apps use your Strapi API, or you need your own data hosting, keep it.

Why teams leave Strapi

You picked freedom.
Now you run a server.

Strapi is a good choice when you want full control of your content API, and your developers want to shape it. Then the site grows, and someone is patching Node, upgrading major versions and keeping a database backed up, all to publish blog posts.

Webflow handles hosting and upkeep for you, and your marketers can build pages. In exchange you lose an API you own and the option to host your data wherever you like. For some teams that is a deal breaker, and they should stay.

Servers to patch

After the move, hosting, SSL and platform updates sit with Webflow, not with your team.

API client listed

Before Strapi goes offline, we check what else calls it: apps, scripts and integrations.

Of daily checks

We read Search Console on each day of the first two weeks.

From API to Designer

What moves, and what
you can switch off.

Strapi is only the back half of your site. Here is the full picture.

Collection types

Each type with its own pages becomes a Webflow collection. Single types become pages or components.

Dynamic zones

Editors stack components on a page in Strapi. Those become Designer components that your team places and edits.

Relations

One-to-many and many-to-many links become reference and multi-reference fields, within plan limits. We check the deep ones first.

Rich text

Blocks fields are structured data and get converted to HTML. Older Markdown fields get converted as well.

Media library

Files come from your uploads folder, or S3 or similar. We move them to Webflow and rewrite the links.

Custom code

Controllers, lifecycle hooks, plugins and roles stay behind. Anything still needed gets a new home.

The export

An archive you
can open.

strapi export writes an encrypted, compressed archive by default. With encryption and compression turned off, we get readable files: entities and links as JSON lines, plus your uploads. Admin users and API tokens are not included, which is fine here.

That format is meant for loading into another Strapi, so we also read your content through the REST API when it is simpler. We write a short script to reshape it for Webflow, then import and compare counts per type.

Launch checklist

Checked before Strapi
goes offline.

Headless sites hide a lot in the front end, and other tools may call the API.

  • API logs are checked for clients other than the website.
  • Front end routes are read from code and matched to a crawl.
  • Each component in a dynamic zone has a Designer equivalent.
  • Relation fields land on the same linked entries as before.
  • Each locale if you use internationalisation, has its content and hreflang.
  • Media links no longer point at the old server or bucket.
  • Forms posting to Strapi now go to Webflow or your CRM.
  • A database backup is saved before the server is retired.

What moves

Your site,
moved layer by layer.

Moving from Strapi to Webflow is more than copying pages. These are the seven layers we move, in the order we move them.

  1. 01
    Audit

    Every URL, page, form and script on your Strapi site, listed in one sheet before anything moves.

  2. 02
    Content

    Pages, posts and collections moved into Webflow, field by field, so nothing is retyped by hand.

  3. 03
    Design and build

    Pages rebuilt in Webflow as reusable components, matching the look you have or a new design.

  4. 04
    Redirects

    Every old URL gets a 301 to its new address, so old links and search results still land on the right page.

  5. 05
    SEO carried over

    Titles, descriptions, schema and image alt text move with each page.

  6. 06
    Forms and tracking

    Forms, analytics and connected tools set up again and tested before launch.

  7. 07
    Launch and watch

    DNS switched and the sitemap submitted, then we watch Search Console for errors.

Review before launch

Editors try it.
Developers relax.

On staging, your marketers change a page and publish a post without calling anyone. That is usually the first time they do it. We watch how it goes and fix the awkward spots.

Everyone reviews on desktop, tablet and phone, and leaves notes on the page. Your developer signs off on what can be retired.

staging.fieldandclay.comStaging
Field & ClayShop
STONEWAREMade slowly. Used daily.
1Field & Clay teamCan the photo be bigger?Resolved
DesktopSigned off
Field & ClayShop
STONEWAREMade slowly. Used daily.
2Field & Clay teamMenu feels crampedResolved
TabletSigned off
Field & ClayShop
STONEWAREMade slowly. Used daily.
3Field & Clay teamButton text too smallResolved
MobileSigned off
Waiting for sign-off on 3 screensAll screens signed off. Checklist green.Switch domain

Strapi vs Webflow

Control against
convenience.

Strapi gives developers more. Webflow gives everyone else more.

FeatureWebflowStrapi
Hosting and updatesHandled for youYours, or Strapi Cloud
Building pagesVisual, no developerFront end code, then fill in fields
Own your API and data locationWebflow APIs, Webflow hostingYes, self-hosted
Custom back-end logicWebflow Cloud or a separate serviceControllers, hooks, plugins
Content for many channelsWebsite firstAny client, by API
Open sourceNoYes
Best forOne website, a marketing teamDevelopers who want to own the stack

Our process

How a Strapi to
Webflow move runs.

A common plan for a Strapi back end with one marketing front end. Your quote has its own dates. Coloured bars are ours, striped bars are yours.

Strapi to Webflow · scope to launchYou

What you get

What comes with
every Strapi move.

No add-on surprises. These come with every project.

01

Stack audit

Content types, front end routes, API clients and hosting.

02

Redirect list

Routes from code and a crawl, each changed one a 301.

03

Designer build

Dynamic zone components become Webflow components.

04

Data import

Entries in reference order, text converted, media moved.

05

SEO fields

Meta values, from Strapi or the code, set per template.

06

Forms and hooks

Anything Strapi did on submit, redone and tested.

07

Domain move

DNS changed with you on a call. Mail stays out of it.

08

Launch watch

Two weeks of daily Search Console reads, then weekly.

Our work

Webflow sites
we have shipped.

Try us first · Try us first · Try us first ·

Does your Strapi only serve one website? Ask us first.

We send a free review of your content types, routes and what calls your API. If a move would cost you something you need, we will point it out and suggest staying.

Get my free reviewFree, no strings

The guide

The Strapi to Webflow migration guide

How to retire a self-run CMS and a custom front end, and still have every URL and entry where it should be.

What is a Strapi to Webflow migration?

You replace two things with one. Strapi stored the content and a separate front end showed it. Webflow does both, and runs the hosting. Entries become collection items, pages get built in the Designer, and old routes are redirected.

No importer exists for this, so the content is reshaped by a short script and the design is rebuilt by hand.

When staying on Strapi is the better call

  • A mobile app, product or other service uses the same API
  • You have rules on where your data is hosted
  • You rely on custom controllers, hooks or plugins
  • Developers like it, and upkeep is not a burden

Read Webflow vs Strapi for the longer version. If you only want a nicer editing experience with code still in your hands, look at Astro + Sanity.

Check who else uses the API

Before planning anything, look at what else reads from Strapi. Marketing sites tend to collect extras: a pricing widget in the app, a script that writes a feed, a form that posts entries. Server logs and your API tokens are good places to look.

If something else depends on it, you can move the site and leave a small Strapi running, or find that thing a new source.

Mapping the content model

Components can be repeatable, and dynamic zones let editors combine them freely. In Webflow, repeating content usually becomes a collection, while page sections become components you place on a page. Many-to-many relations become multi-reference fields.

Webflow has plan limits on fields and references, so we compare your model with your plan early. See Webflow CMS for what is possible.

Moving media and rich text

Files live in the uploads folder or a provider like S3, and your front end probably links to them directly. We move them, swap the links and resize the big ones. Images added through a CSV link do not get responsive versions, so we upload through Webflow where it matters.

Blocks fields are converted to HTML, as are older Markdown fields. Then we read a sample by eye, since Webflow may strip what it does not support.

Redirects, launch and shutdown

URLs were decided by your front end, so we read its routes and compare them with a crawl and Search Console. Each changed path gets a 301, and folder moves get one rule with a capture group.

  1. The domain moves on a call with you.
  2. We test redirects, forms and tags on the live site.
  3. We send the sitemap and read Search Console daily for two weeks.
  4. You back up the database and retire the Strapi server and old front end when you are ready, not on launch day.

Each old URL is mapped to protect your rankings. Some movement is normal after a change of front end, and we will not tell you otherwise.

Wall of love

Don't take
our word for it.

Hear it from the founders and teams we have built for.

Bailey McElligott, Design Director
Bailey on working with Kookies.
Bailey McElligott · Design Director0:17
Verified review
5.0
★★★★★
"They are very professional and the best at what they do."

Juned Khatri, Chief, BubbleWrap
Web development · Dec 2022 to Jan 2023 · Quality, schedule, cost and willing to refer: 5.0

Read it on Clutch
"Fast, efficient and beautifully designed! Kookies nailed our website with pixel-perfect execution and smooth interactions."
Juned KhatriFounder, ClanX
"They are very professional and the best at what they do. Kookies surpassed expectations with Webflow. Thrilled with the results!"
Juned KhatriChief, BubbleWrap
"Kookies' professionalism, dedication and exceptional design skills exceeded our expectations. Highly recommended for high-quality work and timely delivery."
AA
Ali Al MuttawaCo-founder, Artal Invest
"A thorough job, with high-quality work in a short timeframe. Abdul and his team were prompt, professional and patient with all our inputs. Happy to recommend them."
Sejal SinghiManaging Consultant, Baraka Impact Finance

FAQs

Strapi to Webflow
questions.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

Not directly. The export is meant for loading into Strapi. We use it, or the REST API, as the source and reshape the data for Webflow collections.

They become reusable Designer components placed on pages, or collection items where the content repeats. Editors work differently, so we show your team before launch.

Yes. Move the site and leave Strapi serving the app. It saves you the front end but not the server, so we go through whether the split is still worth it.

They stay with Strapi. If one does something you still need, like syncing to a CRM, we rebuild it with a Webflow integration, automation tool or small service.

Every old route is mapped, and meta fields and schema are matched to the live pages. We check Search Console daily for two weeks. Rankings may shift for a while, which is normal, and they cannot be guaranteed.

You get a fixed quote after a 20 minute call. Content types, dynamic zone components and page count set the price. First-time clients get $500 off projects of $2,000 or more.

After launch, once you have checked nothing else calls it and have saved a backup. We suggest leaving it running for a few weeks to be safe.

For 30 days after launch we make safe changes for free: copy edits, image swaps, colour tweaks and link updates, and we fix anything we built that does not work. New sections, page redesigns and new features are not part of it. We quote those separately, or they are covered by a care plan.

Ready when you are

Let's retire
the Strapi server.

Send the form and get a price and timeline within one working day. Or book a quick call with our team.

WebflowPremium PartnerProud to build the Webflow way★★★★★5.0 on Clutch
Abdul Quadir
Talk to our teamA senior lead runs your call. Abdul, our founder, often joins.

Book a free 20 minute call

Pick a day that works for you.

See open timesOpen calendaror email hello@kookies.io
Book a callGet a quote