Choose the CMS that lets your team publish the pages it needs without creating an operating burden it cannot support. For one content-led marketing site, start with a managed publishing system. Choose a headless CMS when several sites or channels need the same structured content and a technical team can maintain the separate frontend.
TL;DR
- For one content-led site, start with a managed CMS that lets your editors publish without a developer.
- Choose a separate headless CMS when structured content must serve several channels and a team can maintain the frontend.
- For one site, WordPress.com Personal lists $48 a year and Webflow Premium lists $300 a year when billed annually; setup and extras are separate.
- Contentful Lite lists $300 a month for the CMS, with a separate website frontend and hosting still needed.
- A supplier reports that a 95-post migration with a rebrand took 14 weeks; a migration without redesign can need a different schedule.
- Test editing, approval, publishing and export with real content before you move the whole site.
A content management system stores and organizes content. Some products also host and render the website; a headless CMS supplies content to a separate website or app. Hosting and headless architecture answer different questions: a headless CMS can itself be hosted or self-hosted.
Which CMS approach fits your team?
Keep a working CMS if editors can publish safely and the main problem is a fixable template, plugin or hosting issue. A migration is most useful when the current system cannot support an important workflow after reasonable cleanup.
| Approach | Best fit | Work that remains |
|---|---|---|
| Managed WordPress.com | One site with articles and pages, where editors want a familiar dashboard. | Configure roles, content, plugins and integrations for the chosen plan. |
| Managed visual platform such as Webflow | A design-led site where the team wants visual page editing and structured CMS content. | Maintain templates, publishing permissions, integrations and any paid workspace seats. |
| Self-hosted WordPress | A team that needs control over its hosting and plugin setup and has an owner for it. | Manage the hosting, updates, backups, recovery and compatibility. |
| Headless CMS plus a frontend | Structured content shared across sites, apps or other channels, with developer support. | Build and host the frontend; provide previews, integrations and deployment ownership. |
WordPress.com is a managed service; WordPress.org provides software you can host separately. The WordPress comparison explains that distinction. Astro can use local content collections or a headless CMS, so choosing Astro does not require editors to write Markdown. See Astro collections versus a CMS for that narrower decision.
For the visual-platform option, review Webflow’s benefits and limits against the same publishing tasks.
What will the CMS cost?
Compare the same period and identify what each price buys. These US dollar list prices were checked November 14, 2026. They are examples for a small publishing site, not a quote for a completed migration.
| Example | Listed price | What to add or check |
|---|---|---|
| WordPress.com Personal | $4 a month, billed annually: $48 for 12 months. | Managed hosting and 6 GB storage are listed. Check paid plugins, setup, taxes and domain renewal. |
| Webflow Premium Site plan | $25 a month, billed annually: $300 for 12 months. | Site hosting and CMS are listed. Check workspace seats, add-ons, setup, taxes and domain costs. |
| Contentful Lite | $300 a month: $3,600 over 12 months at the listed rate. | CMS service with 20 users and scheduled publishing; a separate frontend and its hosting still need a budget. |
The plans do not provide the same features or service. For one site, the listed WordPress.com and Webflow site charges differ by $252 over 12 months before setup and extras. That is not the cost of moving platforms or proof that one option is cheaper for your whole team. Contentful also offers a free tier with different limits; the paid example is useful when its scheduled publishing and collaboration features are required.
Non-price limits can change the decision. WordPress.com lists 6 GB of storage on Personal. Webflow’s current plan changes describe 20,000 CMS items and 40 collections for the new Premium plan. Storage and item counts measure different things. Check your own images, entries, traffic and permissions against the current plan before comparing them.
What should an editor be able to do?
A good CMS lets the people responsible for content complete their normal work without giving every writer administrator access. WordPress roles separate capabilities such as authoring, editing others’ work and publishing. Other systems use different role and plan limits.

Run the same short trial on each shortlisted system. Give an editor one article and one landing page. Ask them to create a draft, add an author and image, preview it on mobile, send it for approval, publish or schedule it, correct an error, and export the content. Record where they need help and whether an unauthorized role can publish. For a headless option, test the preview and deployment path too: a flexible API does not by itself give an editor a usable preview.
A visual builder can help a marketer change layout. Structured fields can keep repeated articles consistent. Pick the model that suits the team’s real tasks, then test how forms, analytics, CRM connections and accessibility work on the actual templates.
How long should a migration take?
A small pilot should establish the content model, one article template, one service page and one form before the whole site moves. Allow time for content review, redirects, testing and editor training as well as the build.
One agency, Webnomads, estimates four to six weeks for a 30–100 page Webflow migration with a basic CMS and standard integrations, assuming a clean source and prompt feedback. It reports one 95-post migration with a concurrent rebrand took 14 weeks. These are one supplier’s estimate and example, not a delivery promise for another site. Different templates, integrations, approval cycles and redesign work change the schedule.
Before launch, map each important URL to its destination, transfer metadata and media, test forms and analytics, and confirm a recoverable backup. Rehearse the import with a difficult sample, not only the homepage. The website migration checklist covers the launch and monitoring work in more detail.
Who will operate and secure it?
Name an owner for accounts, updates, backups, restore tests, integrations and billing before choosing the platform. A managed plan can take over some infrastructure work; it does not own your editorial permissions or every third-party integration. The US Federal Trade Commission recommends regular software updates and backups as basic protections for small businesses.
Choose the smallest setup that supports the required workflow. If the current CMS passes the editor trial after a focused repair, keep it. If the team needs a separate content layer, budget for the frontend and the people who will maintain it. Hapy provides website and software services, so we have a commercial interest in the decision. Compare Hapy’s service options against the same scope and operating costs as the alternatives.



