- Up to 5 pages from 3 unique templates
- Designed in Figma, built on WordPress or Webflow
- SEO basics and GA4
- Forms connected
- CMS walkthrough video in your branding
WordPress to Webflow migration
Your client’s WordPress site rebuilt in Webflow, with every post and URL accounted for.
Each template is $250 to build, 5 business days for the first template, +2 for each extra. Posts move at $100 per 25.See hours by region
A WordPress to Webflow migration for agencies, delivered under your name. The whole move is quoted in writing after a call, added up from our price list. We rebuild each template in your Webflow Workspace, import posts and other repeating content into CMS collections and check them. Every old URL gets a 301, and you sign the checklist before the domain moves.
- Built in your Webflow Workspace
- Every old URL mapped to a 301
- Your sign-off before the domain moves
- 30-day bug warranty
No WordPress page imports into Webflow as a finished page.
There’s no importer that turns a WordPress theme into a Webflow site, so we rebuild the layouts by hand. Only repeating content (posts, for example) can be imported, and that goes through a CSV with limits of its own.
- Posts whose formatting broke on import
- Blog URLs that moved under /blog/ with no redirect
- A plugin feature with nothing in its place
- A form that stopped reaching the CRM
Each of these has a step in the list further down, and a line on the sheet you sign.
What moves from WordPress to Webflow, and how.
Pages are rebuilt and repeating content is imported. Whatever a plugin did has to be done some other way, and the scope says how.
ContentHow it movesThe limit
Page layouts
Rebuilt in the Webflow Designer, one template at a time, from your Figma or from a new design.
Theme and builder layouts don’t convert. That goes for Elementor, Divi and block themes alike.
Posts and other repeating content
Exported from WordPress as XML, converted to CSV and imported into a Webflow CMS collection, with each column mapped to a field.
Webflow takes a CSV of up to 4 MB per upload, so a large blog goes in as several files. The site plan sets how many CMS items the site can hold.
Post bodies
Imported as rich text and styled by the template, so every post looks the same without hand formatting.
Webflow may strip HTML elements, classes and attributes it doesn’t support. Shortcodes arrive as plain text, so we replace them before the import.
Images and files
Featured images import from their URL into an image field. Other media is uploaded to the Assets panel, renamed and compressed on the way in.
Webflow creates no responsive sizes for images imported by CSV, so we size and compress them first. File fields can’t be filled by CSV and are uploaded by hand.
Categories, tags and authors
Set up as collections of their own and linked to posts through reference fields.
A reference matches on the item’s name or slug, so categories and authors are imported before the posts that point at them.
SEO titles and descriptions
Carried over into CMS fields, which the template uses for each page’s title and description.
They sit in the SEO plugin’s custom fields in WordPress and have to be mapped to Webflow fields one by one.
Forms
Rebuilt as Webflow forms and tested with the same notifications. A CRM or email platform is connected as an integration.
Entries already stored by a WordPress form plugin stay in WordPress unless your client exports them.
Plugins
Each one is listed with what it does, then replaced by Webflow’s own tools or a connected service.
No WordPress plugin runs on Webflow. The replacements are listed in the quote.
Members and stores
Agreed with you before the build starts.
Logins don’t move between platforms. If the site has members, we agree how they sign up again. A WooCommerce store is scoped as its own project.
Webflow’s own guide describes the same route: export the XML, convert it to CSV, import it into a collection, then set the 301 redirects. Webflow Help Center: migrate your site from WordPress to Webflow
Most WordPress post URLs change. Each one gets a 301.
In Webflow each collection has its own URL folder, such as /blog/, and its items live inside it. A WordPress post at the root of the domain can’t keep its address, so the blog is where the redirect map does most of its work.
Example Webflow CMS collection, with the fields a WordPress post is mapped to.
How WordPress URLs map to Webflow
| Old URL | New URL |
|---|---|
| /planning-a-rebuild/ | /blog/planning-a-rebuild |
| /2024/08/planning-a-rebuild/ | /blog/planning-a-rebuild |
| /category/news/ | /blog-categories/news |
| /author/sam-lee/ | /team/sam-lee |
| /services/web-design/ | /services/web-design |
What Webflow’s redirects can and can’t do
- Where they’re set
- In Site settings, under Publishing. Webflow needs a paid site plan for redirects, and a rule takes effect when the site is published.
- Patterns
- One wildcard rule can move a whole folder, such as /category/(.*) to /blog-categories/%1. We use patterns where the old structure allows it and single rows where it doesn’t.
- How many
- Webflow sets no hard limit but recommends about 1,000 rules at most, because every rule adds to a file each visitor’s browser downloads. Patterns keep the count down.
- Bulk import
- The map is uploaded as a CSV of up to 16 MB. An import replaces every redirect already on the site, so existing ones are exported and merged in first.
- Live pages
- Webflow won’t redirect a path that still has a live page. The old page is removed, or its slug changed, before the rule is added.
- Order
- Rules run oldest first, so a specific rule has to be added before the wildcard that would catch it.
How a WordPress to Webflow migration runs.
Eight steps, in this order. The right-hand column is what reaches you at each one.
StepIn Webflow and WordPressOn your side
01Audit the WordPress site
A crawl of every URL with its title and description. Counts of pages, posts, categories, authors and media. Every active plugin listed with what it does, and every form with where it sends.
A written scope: the templates to rebuild, the collections to create, the Webflow site plan the content needs, and a fixed price.
02Plan the structure
Each template is mapped to components and classes, and each kind of repeating content to a CMS collection and its fields. You agree the new URL structure.
The structure map, and the redirect map as a spreadsheet.
03Build in Webflow
Built in the Designer, in your agency’s Workspace, and published to the staging domain, which is kept out of search.
A staging link, and a written update every week.
04Import the content
Categories and authors go in first, then posts, so the references match. Shortcodes are replaced before import. After each import we compare the item count in Webflow with WordPress, and someone opens the posts and checks them.
The counts on the migration sheet, old against new.
05Rebuild forms and tracking
We rebuild every form and submit it end to end, to the inbox and to the CRM. Analytics and conversion events are set up for the live domain.
A tested list of each form and each event, marked pass or fail.
06Load and test the redirects
The map goes into Webflow, specific rules before wildcards. We test every row: the old path has to answer 301 and land on a page that answers 200.
The tested map, with a status on every row.
07Sign off and launch
You sign the launch checklist. We connect the domain in Webflow and switch DNS in your client’s quiet hours. The WordPress site stays live until then.
The signed checklist. The domain doesn’t move without it.
08Check after launch
Three crawls of the published Webflow site, on day 1, day 7 and day 30. If you give us Search Console access we also read the coverage and 404 reports for that month, and add a redirect for any old WordPress path that still gets visits.
The report goes to you with your agency’s logo on it. The 30-day bug warranty covers the redirects, forms and pages we built.
Google’s guidance on site moves warns against sending many old URLs to one unrelated page, such as the homepage. That’s why each WordPress post gets its own target in Webflow. We don’t promise rankings or traffic. Google Search Central: site moves with URL changes
When moving from WordPress to Webflow is the right call.
We build on both, so we’ve no reason to push either. If the move looks wrong for your client, we’ll say so before you quote it.
Webflow development services- Webflow
- Design-led marketing sites with a modest CMS, where the client’s team wants to edit visually and not have to manage plugin updates. A small store fits too, on Webflow Ecommerce.
- WordPress
- Heavy content workflows, a large plugin ecosystem, or a store that has to live inside a content-heavy site.
- Where Webflow is the wrong fit
- Very large or heavily related content, complex user accounts, or a large catalogue or store logic beyond what Webflow Ecommerce does. Those stores go to Shopify or WooCommerce, and we’ll say so before you quote the client.
Agreed in writing before we start.
The order you sign carries these four points. One of them is a limit: no promise on rankings. See the trust page for the wording.
Inside your agency
We work from email accounts on your domain and never contact your client. The sheet and the report carry your logo.
How it worksOn time, or a full refund
Your signed order sets the delivery date. If we miss it for a reason on our side, the whole project fee comes back.
How the guarantee works30-day bug warranty
A redirect, form or page we built that breaks in the first 30 days after launch is fixed free, however small.
Read the Partner AgreementWhat we commit to on SEO
The checklist protects the search signals the site already has, as far as we reasonably can. We don’t promise rankings or traffic.
Read the full checklist
What a WordPress to Webflow migration costs.
Every part of the move has a fixed price on our list. We add them up in a written quote, which changes only if the scope does (and only after you’ve approved it).
- Up to 12 pages from 6 unique templates
- Designed in Figma, built on WordPress or Webflow
- A CMS collection (blog, news or team)
- One form integration
- Performance report at handover
Keeping the design?
A like-for-like rebuild is priced per template from the rows below. Send the URL and we’ll count the templates, pages and posts, then you get a written scope, a fixed price and a turnaround within 2 business days of the call.
In the quote:
- The templates to rebuild, counted
- The CMS collections, and the Webflow site plan they need
- The redirect map and launch checklist, included when we rebuild the site
Add-ons and single services
Every line a WordPress to Webflow quote is added up from.
Set-up and launch
Once per project built from your Figma.
$250 per projectIncluded in the build time
Build: WordPress, Webflow or Shopify
One template built in Webflow, from your Figma.
$250 per template5 business days for the first template, +2 for each extra
Additional page
Using an existing template, with QA.
$50 per page+1 business day per 5 pages
Content migration
WordPress posts or pages moved into Webflow CMS collections. We choose the method.
$100 per 25 pages or posts3 business days per 100 pages or posts
Integration
CRM, email platform or booking tool, through an existing plugin, app or connector.
$100 per integration2 business days
Try us on one small project first.
Pick any one item from our price list and treat it as a pilot, with no commitment beyond it.
- Your first project is paid through escrow, and the money is released as you approve the work.
- Not happy with it? We fix it within 5 business days. Still not happy? You don’t pay (once per agency).
- Like every fixed-price project: on time, or a full refund.
The full terms are in the First-Project Guarantee.
WordPress to Webflow questions.
What agencies ask before they move a client from WordPress to Webflow.
All questionsNot for the whole site. Webflow can import repeating content, such as blog posts, from a CSV into a CMS collection. It can’t import a WordPress theme or a page builder layout, so we rebuild each template in the Webflow Designer and move the content into it.
WordPress exports them as an XML file. We convert that to CSV, clean out shortcodes, and import it into a Webflow CMS collection with each column mapped to a field. Webflow takes up to 4 MB per CSV, so a large blog goes in as several files. Categories and authors go in first so the references match, and afterwards we compare the item count with WordPress.
Static pages can usually keep their paths. Blog posts usually can’t, because in Webflow each collection has its own URL folder, such as /blog/, and its items live inside it. We enter each changed address in Webflow’s 301 redirect settings (with a wildcard rule where a whole folder moves) and try it in a browser before the domain is switched. Google describes some movement in search results after a site move as normal, and we make no promise about rankings.
None of them runs on Webflow. We list each plugin and what it does, then replace it with Webflow’s own tools or a connected service; every replacement is in the quote. Forms are rebuilt as Webflow forms and tested with the same notifications.
It depends on how much content moves. Each Webflow site plan has limits on CMS items, collections and form submissions, and redirects need a paid site plan. We count your client’s content against those limits before we start, and the plan the site needs goes in the quote. Webflow bills the plan to you or to your client. We don’t resell it.
Building from your Figma takes 5 business days for the first template, +2 for each extra. Content migration takes 3 business days per 100 pages or posts. The dates are added up in your quote and the delivery date goes in your signed order. If we miss it for a reason on our side, the whole project fee comes back.
Only if the site suits it. Webflow is a good home for a design-led marketing site with a modest CMS, where your client’s team wants to edit visually and stop worrying about plugin updates. WordPress is the better fit for heavy content workflows, a site that leans on lots of plugins, or a store inside a content-heavy site. We build on both, and we’ll tell you which fits before you quote your client.
Yes. The new site is built on Webflow’s staging domain while WordPress stays live. DNS is switched in your client’s quiet hours, after you’ve signed the launch checklist.
No. The site is built inside your agency’s Webflow Workspace, by people using email addresses on your domain. We never contact your client, and the sheet you sign and the report after launch carry your logo.
Send us the WordPress site. You’ll sign the move off under your agency’s name before the domain changes.
Next, you send a short brief and we reply with a fixed price and a delivery date in writing. You pay nothing until you sign the order.