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.
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.
Posts, 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.
We 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.
Collection 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.
Webflow 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.
We 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.
Account 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.
Review the collection structure and the way editors create a new page. Choose the required content types, fields, taxonomies, and relationships before importing records.
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.
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.