Webflow or WordPress: decide who maintains the website and its features

Analysis of official documentation, with no testing on a paid account.

Differences that change choice

Do not compare a subscription to software alone

WordPress can be downloaded without a license fee from the core of the software, but the site always has costs: hosting, domain, maintenance and possible paid modules. Estimate the necessary elements. Webflow requests to distinguish Site plan, Workspace and additional services.

The comparison must cover two years and the same features. If WordPress needs a booking plugin, include its licence and maintenance. If Webflow needs an external service for the same workflow, also include that subscription and the connection between the two.

Technical freedom involves an organization

WordPress has an ecosystem of themes and plugins that can meet varied needs. This flexibility requires checks on compatibility, updates and recovery after an incident. Adding modules for every small request can make diagnosis difficult.

With Webflow, the design and publishing framework reduces some infrastructure choices, but service limitations remain to be examined. A very specific need must be demonstrated before signing, especially when it depends on external development or integration.

Preparing for site transmission

Make a news release and correct a page by the person who will ensure daily life. Then ask for a backup or export and explain how another provider would take over the site. Export Webflow does not automatically take over the hosted CMS and trade functions.

Choose WordPress if its features and technical control justify this maintenance. Choose Webflow if its framework covers the project and the team will be able to use it. Keep domain access and the original content; the theoretical ability to migrate is useful only if the data and dependencies are known.

Exporting a site with a blog and a form: what's missing at ZIP

Let's take this case: an SME wants to take a showcase site with thirty articles, a form and a protected page. The Webflow documentation indicates that code export does not include CMS and trade functions, processing forms, or password protection. The collections may be subject to a separate data export. Receiving the code therefore does not mean recovering the same service ready to work elsewhere.

1. List the functions used, beyond visible pages: forms, search, blog and protected access.
2. Ask for an inventory of exports and services that would need replacing with another hosting provider.
3. Open a copy of a test environment and verify an article, a form submission and access to the protected page.
4. Estimate the reconstruction of the missing functions, then compare this cost to that of the planned maintenance.

The choice according to the person who takes over the site

WordPress does not become maintenance-free because the software is freely available: themes, plugins and hosting still need someone responsible for them. Webflow also does not remove the need to organise content and access. Ask the person responsible for daily operations to edit a real test page. Choose the solution whose limitations, backups and need for outside assistance they understand.

Reviews to consult

• Webflow