Every agency knows the dread of telling a high-growth client: “We need to freeze content publishing for two months while we migrate.” When one of our customer outgrew Webflow’s strict 300-page limit and rigid URL structures, their marketing team—pushing 120-140 posts a month—couldn’t afford to stop.
Instead of a traditional content freeze, we ran Webflow and WordPress in parallel.
In this session, I’ll walk through the exact architecture we used to perform a seamless migration. We will explore how we used a reverse proxy configuration to serve existing, high-converting marketing pages from Webflow, while simultaneously routing new blog traffic to a highly scalable WordPress environment deployed on AWS. To the user, it was a single, flawless domain; to the client, it meant uninterrupted organic growth.
Join this session to learn how to handle complex, enterprise-level migrations without halting your client’s marketing engine, and how to execute a smooth final cutover.
Learning Outcomes (What attendees will take away) 1. Technical Strategy: How to implement a reverse proxy to run two distinct CMS platforms seamlessly on a single domain. 2. Client Management: How to pitch and execute complex migrations without forcing the client into a restrictive “content freeze.”
// on_stage
