Wordpress to Webflow: Double-Edged Sword

I’d like to initiate some discussion regarding a common scenario for many Webflow developers — migrating a Wordpress site to Webflow.

Often, as a freelancer or agency, we sell this idea of how we can add value to a client by switching their website from Wordpress to Webflow. One of the more common selling points is that a Webflow site will allow for more control, essentially removing the developer (you or your agency) from the equation once the project is completed. Now, we know this not to be fully true, as there are often requests for changes, upgrades, etc. that can produce a steady stream of work. However, there is also the potential pitfall of offering up too much freedom & control to a client that can diminish the long-term work & value you can provide to a client.

What I think isn’t talked about enough, is how you can simultaneously increase your long-term work & value with a client by making this migration from Wordpress to Webflow. Traditionally, web agencies have been able to not only survive but thrive by creating consistent & long-term work with a given client, as opposed to seeking out new client after new client.

If this is a common migration you make, how do you sell this in a way that not only benefits your client but also your business? Do you offer one-off builds or do you propose long-term solutions for clients?