Webflow to WordPress migration
Keep the parts of your Webflow website that work while giving your team a WordPress editing system. Norml rebuilds the agreed layouts, maps CMS collections into WordPress content types, and reconnects forms and other services. The move includes the content relationships and publishing tasks your team needs after launch.
A few clients we’ve worked with
What we do
Rebuild your Webflow website in WordPress with mapped CMS collections, editable layouts, working forms, media transfer, and redirects.
What the migration covers
Webflow’s code export and CMS exports serve different purposes. We review both, then define the WordPress structure and the content that belongs in it.
- Solution
- Migrations
- Current platform
- Webflow
- Destination
- WordPress
- Collections and content relationshipsPosts, people, projects, categories, and other collections get a field-by-field mapping. References are rebuilt as relationships in WordPress, with source identifiers retained during import. We check a page with linked records before processing the rest of that collection.01
- Editable layouts and interactionsWe use the current site as the design reference and agree any changes separately. WordPress templates need editable fields and reusable sections. Navigation, tabs, animation, and responsive layouts are rebuilt or adapted, then checked on desktop and mobile.02
- Media and localized contentCollection exports can point to images and files still hosted by Webflow. We copy agreed assets into the destination, update links, and check downloads and inline images. Each language needs its own content inventory and URL mapping; a primary-language export is not evidence that all translations moved.03
- Forms, search and redirectsWebflow form processing and site search do not arrive as working WordPress features in a code export. We configure replacements, verify submission destinations, and map legacy URLs. Existing lead capture, analytics, and consent behavior become explicit test cases.04
Client reviews
“Norml Studio's professionalism and responsiveness were impressive.”
“They were proactive in suggesting improvements we hadn't considered.”
“They delivered what they said they would, on time.”
“They focused on how to make our daily operations easier, not just on building features for the sake of it.”
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”
What we need before the move
- Workspace and content accessWe need access to the Webflow project, collection definitions, exports available on your plan, original assets, and domain settings. Include any external services used by forms or embedded components.01
- Membership and commerce boundariesAccount access, paid content, ecommerce, and custom applications need separate mapping and acceptance checks. We identify dependencies before promising a replacement. Exported page files alone do not preserve these systems.02
How we prepare the move
- [Define the WordPress model]Step 01
Review the collection structure and the way editors create a new page. Choose the required content types, fields, taxonomies, and relationships before importing records.
- [Build a representative page]Step 02
Reproduce an agreed layout and populate it with imported content, linked records, and images. Check that an editor can update it without changing the design unintentionally.
- [Move and verify]Step 03
Complete the approved content transfer, compare record counts, and inspect formatting and assets. Test form destinations, search, responsive behavior, and redirects before switching the domain and repeating the launch checks.
The people who do this work.
Meet the whole teamNo account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedRelated services.
From the Norml blog.
Questions about the migration
Can CMS relationships be preserved?
Yes, where the source relationship is available and the destination mapping is defined. A CSV may describe a reference as text rather than a connected record. We resolve those values and verify the resulting WordPress relationships.
Can you keep the existing design?
We can use the live Webflow site as the agreed visual reference. The WordPress implementation still needs its own editing structure and testing. A code archive is not an installed, editable WordPress theme.
Which interactions need rebuilding?
Anything relying on Webflow-hosted processing needs a replacement. Other frontend interactions are assessed individually for compatibility and accessibility. We document the chosen behavior for menus, animations, forms, search, and embedded tools.
Plan your Webflow migration
Share your current website, the features you rely on, and what needs to change. We will review the WordPress requirements and identify the content, rebuild work, and launch checks your move needs.