The decision to migrate from traditional to headless WordPress is a strategic commitment. A migration that is timed correctly pays back in 12 to 24 months; a migration that is timed wrong wastes 6 to 12 months of engineering and 2x to 3x the build budget. The difference is in the readiness signals.
This post covers the 9 concrete signs that a South African business is ready to migrate, the signs that indicate the timing is wrong, and the practical evaluation for a specific business.
Sign 1: Site is core to revenue
The single most important signal: the website generates 30%+ of new customer acquisition. A business whose website is core to revenue has the budget to justify the migration and the strategic motivation to follow through.
A business whose website is a brochure (5% of acquisition) does not have the budget or the motivation. The migration is unjustified.
Sign 2: Page speed is a measurable conversion blocker
The site's Core Web Vitals are failing (LCP over 2.5s, CLS over 0.1, INP over 200ms). The site is measurably losing conversions because of speed. The speed loss is documented in analytics.
A site that does not have a measurable speed problem does not have a measurable speed solution. Headless helps; the migration cost is only justified when the speed problem is real.
Sign 3: Site traffic exceeds 50,000 visits per month
The site is large enough that the infrastructure cost of traditional WordPress (hosting, caching, CDN) exceeds the infrastructure cost of headless. The break-even is typically around 50,000 monthly visits; below that, traditional WordPress is cheaper.
A site below 50,000 monthly visits benefits from headless speed but does not benefit from the infrastructure cost savings. The migration is harder to justify on cost alone.
Sign 4: Team has a developer or agency partner with modern frontend skills
The business has access to a developer (internal or agency) who can build and maintain a Next.js, Astro or similar frontend application. The capability is the most common reason headless migrations fail — the business adopts headless, then cannot maintain it.
A business whose only technical resource is a traditional WordPress developer should not adopt headless. The capability gap will compound.
Sign 5: Content needs to flow to multiple channels
The same content powers a website, a mobile app, an in-store display, or other surfaces. The multi-channel requirement is the strongest strategic argument for headless — the API-first architecture enables the multi-channel publishing.
A business that publishes only to a website does not have the multi-channel need. The headless benefit is smaller; the cost is the same.
Sign 6: Existing WordPress site has accumulated significant technical debt
The traditional WordPress site has accumulated technical debt over 3+ years — outdated plugins, custom PHP theme code, performance workarounds, security patches. The site is becoming unmaintainable.
A migration to headless is a natural moment to reset the codebase. The cost of the reset is justified when the existing codebase is already a liability.
Sign 7: Security is a regulatory or reputational concern
The business operates in financial services, healthcare, legal, or another regulated industry where a security breach has regulatory consequences. The headless architecture's decoupled security model is a meaningful improvement.
A business in a less-regulated industry has less to gain from the security model. The migration is harder to justify.
Sign 8: Existing site has reached its scaling ceiling
The traditional WordPress site cannot be scaled further without significant infrastructure investment. The hosting cost is growing faster than the traffic; the page speed is degrading under load.
A site that is hitting its scaling ceiling has a strategic incentive to migrate. The headless architecture scales differently — to global CDN, to edge rendering, to static generation.
Sign 9: The business has a 2- to 3-year strategic horizon
The business is committed to the site as a strategic asset for 2+ years. The migration cost is amortised over the strategic horizon; a short-horizon business (planning to sell, to wind down, to pivot) cannot amortise the cost.
A long-horizon business can justify the migration as a strategic investment. A short-horizon business cannot.
The readiness scorecard
For a South African business, score each of the 9 signs as 0 (no), 1 (partial), or 2 (yes):
| Sign | Score (0–2) |
|---|---|
| Site is core to revenue | |
| Speed is a measurable conversion blocker | |
| Traffic exceeds 50,000 visits/month | |
| Team has developer with modern frontend skills | |
| Content flows to multiple channels | |
| Existing site has significant technical debt | |
| Security is a regulatory/reputational concern | |
| Site has reached its scaling ceiling | |
| Business has 2- to 3-year strategic horizon |
- Score 14 to 18: Migration is strongly justified. Begin planning immediately.
- Score 10 to 13: Migration is worth considering. Investigate further; identify which signs are weakest.
- Score 6 to 9: Migration is premature. Address the lower-scoring signs first.
- Score 0 to 5: Migration is unjustified. Stay traditional.
A business that scores 14+ has the strategic and operational case for migration. A business that scores below 10 should either build a stronger case for migration or stay traditional.
The signs that indicate the timing is wrong
Five signals that the migration is premature:
- The site is new (under 12 months old). A new site does not have the technical debt, the traffic, or the strategic track record to justify migration. The first 12 months should be on the existing architecture.
- The site is about to be redesigned anyway. A business that is about to redesign the site should not migrate simultaneously. The two projects compete for engineering capacity; one will suffer. Redesign first; migrate in 18 to 24 months.
- The team is non-technical. A business with no developer should not adopt headless. The maintenance burden will compound.
- The budget is for either redesign OR migration, not both. A business with R200,000 to invest should not spend it on a headless migration. The traditional WordPress redesign is the higher-ROI option for most SMEs.
- The team is small (1 to 2 people). A small team cannot maintain two systems. The headless migration is justified when the team can support both.
A business showing any of these signals should defer the migration. The deferral is the strategic choice.
The decision
For a South African SME, the migration decision is:
- Score the readiness scorecard. Total the 9 signs.
- Check the wrong-timing signals. If any of the 5 are present, defer.
- If the score is 14+ and no wrong-timing signals, plan the migration. The migration takes 2 to 4 months for a typical SME site. The post-migration maintenance is 1.5x to 2x the cost of traditional.
A migration that follows this process is a strategic investment. A migration that ignores the readiness signals is a strategic error.
FAQ
How long does a headless migration take?
2 to 4 months for a typical SME site with 50 to 200 pages. Longer for larger sites or sites with significant custom functionality.
What's the biggest risk in a headless migration?
Capability. The business adopts headless, then cannot maintain the frontend application. The capability gap is the most common reason migrations fail or stall.
Can I do headless migration in phases?
Yes. A common pattern is to migrate the marketing site first (the part of the site that benefits most from speed), then the blog, then the application functionality (eCommerce, member areas). The phased approach reduces risk.
How do I find a developer for the migration?
Look for an agency or freelancer with both WordPress and modern frontend (Next.js, Astro) experience. The capability should be demonstrated in past work, not claimed in pitches.
What's the ROI of a headless migration?
Typically 12 to 24 months for a business that scores 14+ on the readiness scorecard. The ROI comes from improved conversion (from speed), reduced security risk, and improved developer velocity on subsequent projects.
If you want help scoring the readiness for a specific site or scoping a phased migration, send us the current site's traffic, the team that maintains it, and the strategic goals for the next 2 to 3 years. Most headless WordPress engagements we scope include a readiness assessment and a phased migration plan, with the build work scoped against the priority surface area (typically the marketing site first).