Move your site from WordPress to Webflow
A plan for moving a content-led marketing site off WordPress and onto Webflow. Your posts come across, and every URL that changes gets a 301 redirect.
When the move makes sense, and when it doesn’t
Move to Webflow if:
•
Your marketing team wants to change pages without a developer, inside a structure that keeps the site consistent.
•
Plugin updates, conflicts and hosting issues take up time that should go into content.
•
You publish structured content, such as posts, case studies, integrations or a resource library, and want it in a hosted CMS.
•
Your content fits Webflow’s CMS. Premium includes 40 collections and 20,000 items.
Stay on WordPress if:
•
You have a very large archive or an editorial workflow with detailed roles and approvals.
•
WooCommerce, memberships, courses or another plugin-based feature is central to the business.
•
You must self-host the site.
•
The real problem is the design or the message. A redesign on WordPress may fix it for less.
What moves over and what gets rebuilt
Pages
Rebuilt in Webflow. Themes, page-builder layouts and shortcodes don’t import.
CMS content
WordPress exports posts, pages, custom post types, comments, custom fields, categories, tags and users as an XML file. We convert it to CSV and import it into Webflow collections, mapping each field. Categories, tags and authors become their own collections, linked by reference.
SEO and redirects
Titles, meta descriptions and Open Graph data are exported from your SEO plugin, so nothing is retyped by hand. Every URL that changes gets a 301 redirect in Webflow, including date-based permalinks, archives and paginated pages.
Forms
Rebuilt with Webflow forms, or with the form tool you prefer, and connected to the same inbox, CRM or webhook.
Integrations
Every plugin goes on a list. Each one is rebuilt in Webflow, replaced with an app or embed, or retired.
Media
Files from the WordPress uploads folder are uploaded to Webflow’s assets. Important PDFs and files that people link to get redirects too.
The plan, step by step
01
Site review
We crawl the live site, list every URL WordPress generates and check Search Console and analytics to see which pages bring traffic, leads and backlinks.
02
Content inventory
Every page, post type, taxonomy, field, form, plugin and file goes into one sheet, each marked keep, merge, rewrite or retire.
03
Redirect map
Each old URL gets its new address. Webflow builds CMS URLs from the collection and item slugs, so we design the collection structure around the URLs you want to keep. Retired pages point to the closest relevant page, since search engines can treat a redirect to the homepage as a missing page.
04
Rebuild
We set up the class system and components in Webflow and build the templates. Then we import the content and clean up leftover formatting in post bodies.
05
QA
We check every page on desktop and mobile, test every form, compare metadata against the inventory and test the redirects before launch.
06
Launch
We publish, switch the domain to Webflow, confirm the redirects are live and submit the new sitemap in Search Console.
07
Post-launch checks
For the period agreed in the scope, we watch Search Console for 404s, crawl errors and changes in indexed pages, and fix anything that slipped through.
Risks and how we avoid them
Rankings
Some movement is normal while Google recrawls a moved site, and Google says new URLs can take a few weeks or more to show. Keeping URLs the same where possible, and using permanent redirects for the rest, gives search engines the clearest signal.
Broken links
WordPress creates many URLs nobody thinks about, such as archives, feeds, attachment pages and trailing-slash variants. The site review finds them, and the redirect map covers them. Webflow’s redirect CSV import replaces all existing redirects, so we keep one complete file and import it once. Google recommends keeping redirects for at least a year.
CMS limits
We count posts, authors, categories and other content against Webflow’s plan limits before you commit. Long lists on a page show up to 100 items unless pagination is turned on, so we plan archive pages with that in mind.
Data that doesn’t map cleanly
Custom fields, galleries and plugin-generated content may need restructuring before import. We test a sample import first and fix the mapping before moving everything.
How we handle it
We design in Figma and build in Webflow and Framer. We plan every move around what your WordPress site has already earned, which means its URLs, its content and its links. Daniel G. Bright leads strategy, creative direction and every relationship, and specialist designers and developers handle production and builds. For Arteway, an online art school taught from working artists’ studios, we designed the brand and the website, then built the site in Webflow.
We scope and price each move as a flat-fee website project, agreed in writing before work starts.
Questions
Daniel G. Bright
Founder, BrightStudios
Still have a question?
Book a call with me to talk through your project and agree the next step.
Keep exploring
Webflow to Framer
For teams whose designers want to publish changes themselves.
Framer to Webflow
For sites whose content and CMS have outgrown Framer.
WordPress to Framer
For marketing sites where every change waits on a developer.
Wix to Framer
For companies that have outgrown a template and need a site built around the product.
Squarespace to Framer
For companies that need page types and design control beyond a template.
Wix to Webflow
For growing sites that need a structured CMS and full design control.
Squarespace to Webflow
For content-led sites that have outgrown their template.
Plan your move
Bring your current site to the call and tell us why you’re thinking of moving. We’ll tell you whether a move is worth it and what it involves.