Audit and URL map
Every page, post, category and tag crawled, and every active plugin listed, before anything moves.
Migrations
Headless & composable
Design & growth
Your posts, custom fields and redirects moved over, and every plugin mapped to its Webflow replacement. We crawl before and after, so every URL is checked.
Trusted by
It happens one fix at a time. A form plugin. An SEO plugin. A caching plugin to undo what the page builder slowed down. Then an update breaks one of them, and changing a headline needs a developer.
Webflow removes most of that. The risk is in the move itself: the permalinks, the custom fields, and the redirects a plugin was quietly handling for years.
The plugins go. What they were doing has to come with you.
Four workstreams, planned before anything moves and checked after cutover.
Every page, post, category and tag crawled, and every active plugin listed, before anything moves.
Posts, pages and custom post types mapped into CMS Collections, with a person checking what scripts miss.
Titles, descriptions and canonicals mapped from your SEO plugin, and redirects tested on staging.
Forms rebuilt and routed to your CRM, and tracking tested before cutover.
Teams leaving WordPress with years of posts, a plugin stack nobody wants to update, and rankings too valuable to gamble on the move.
Six things that decide whether traffic holds, and how we handle each one.
Field-mapped, with categories, authors and custom fields kept
Typically: exported, converted to CSV, imported as is
Every active plugin mapped to its replacement before the build
Typically: dropped at launch, gaps found later
Every changed URL on a 1:1 redirect map, tested on staging
Typically: changed without a map
Carried over field by field
Typically: left behind with the SEO plugin
A before and after crawl comparison you keep
Typically: “Traffic looks fine”
[X] days of ranking and 404 monitoring
Typically: handoff
Your WordPress site stays live until the new site has passed every check.
Every URL and active plugin logged, plus a traffic baseline you can compare against after launch.
Field map, plugin replacement map, 1:1 redirect map, and a staging build you review before anything moves.
Content import, redirect tests, form and integration tests, and a person checking what scripts miss.
Go-live, a before and after crawl comparison, and a monitoring report you keep.
Meet a technical lead to review your plugin list, your URL count, and what has to survive the move.
WordPress to Webflow · Airtable · Memberstack · Jetboost · Make.com · membership management · class registration · payments
Read the case study →WordPress to Webflow · DNS transition · new Webflow pages live while the old WordPress site continued to serve traffic · Webflow Enterprise plan
Read the case study →WordPress to Webflow
Read the case study →Most of them are doing a job Webflow already does. Here is where each one goes.
The 50-point checklist our team uses before a platform switch, with a WordPress plugin inventory you can fill in yourself.
“We originally hired Seattle New Media to build a complex, layered resource page to assist our users and intuitively drive them to additional content...”

“We needed our webflow website built in a really short timeline and Seattle New Media was able to work within not only our time constraints but...”

“Partnered with Seattle New Media on a project and they were awesome. Super collaborative, tons of experience, just overall a great...”

You can. Webflow’s own guide is to export WordPress as XML, convert it to CSV and import it into a Collection. That moves your posts. Design, media, redirects, forms and SEO settings are separate steps you handle yourself, and CSV import has limits on field types and item counts by plan.
Some movement in the first weeks is normal on any migration. A lasting drop usually comes from missed redirects, lost metadata or broken internal links, which is exactly what our process checks for.
Most are replaced by something Webflow does natively. The table above shows where each common plugin goes.
Yes. Posts and custom post types become CMS Collections, with categories, tags, authors and custom fields mapped as their own fields.
[CONFIRM: to Webflow Ecommerce, to Shopify, or not offered]
Often, yes. Webflow CMS pages sit under a collection path, such as /blog/post-name, so WordPress permalinks with dates or posts at the root usually change. Every changed URL gets a 301 redirect.
No. They move in batches by script or API, with URLs and metadata mapped first. Volume changes the timeline, not the method. Check your Webflow plan’s CMS item limit before you start.
No. We can rebuild your current design in Webflow, or redesign as part of the move. Doing both together avoids building the site twice.
Most run [X] to [X] weeks, depending on page count, custom fields and how much content can be scripted.
[X] days of ranking and 404 monitoring, CMS training, and a recorded walkthrough you keep. Retainer clients usually hear back within the hour, and most requests are picked up the same day.
For marketing teams who want to publish without a developer, usually. We compare the two in detail here. Webflow vs WordPress →
Our CMS migration page covers the rest. CMS migration services →
Our technical team will come back with a clear migration plan: what moves, what gets rebuilt, and what every changed URL redirects to.