0 of 20 answered
— / 100 pts
Your readiness score
What your score means
Answer all 20 questions across the 6 dimensions above. Your readiness score, level, and gap analysis unlock here once every question has an answer.
/ 100 pts
Strong foundation. Enterprise WordPress is a low-risk transition for your organisation.
Recommended path: proceed to a scoped pilot. Start with a 20-hour platform audit — free, and bounded.
Core capabilities are in place. 2–3 dimensions need targeted work before or during migration — most successful migrations start exactly here.
Recommended path: address priority gaps in parallel with migration planning. Book a 30-min validation call.
Significant gaps in 3+ dimensions. Migration risk is high without a structured readiness programme.
Recommended path: start with an Architecture Audit. Prioritise security, governance, and hosting baseline.
Foundational requirements across most dimensions are unmet. Attempting migration now would compound existing problems.
Recommended path: book a discovery call. Define a 90-day readiness roadmap before any migration scoping.
Dimension breakdown
Security & hosting
Scalability
Editorial workflow
Integration complexity
Governance
Team WordPress familiarity
Gap analysis
Dimensions marked gap need to be resolved before or during migration. Partial dimensions need targeted work. Strong dimensions are ready.
Security & hosting
Hosting unfit for enterprise traffic or compliance. Prioritise a VIP / managed migration path.
Managed hosting in place but compliance gaps remain. Address SOC 2 / SSO before launch.
VIP or equivalent in place. Compliance documented.
Scalability
Architecture cannot support planned traffic or multisite. Requires re-architecting before migration.
Caching and CDN in place; multisite architecture not yet defined.
Proven at scale. Multisite / headless approach defined.
Editorial workflow
Editors cannot publish without developer involvement. Gutenberg implementation and block library are migration prerequisites.
Block library in progress. Some editorial tasks still require dev tickets.
Editors publish independently. Governed Gutenberg implementation in place.
Integration complexity
Critical integrations undocumented. Map DAM, CRM, and SSO as a discovery output.
Core integrations mapped. 1–2 complex dependencies (DAM, personalisation) need scoping.
All integrations documented with a carry-over decision made.
Governance
No governance model. Content roles, approval flows, and design guardrails must be defined before launch.
Basic roles in place. Multi-step approvals and design lockdown not yet implemented.
OnePress or an equivalent governance framework active.
Team WordPress familiarity
No internal WordPress capability. Training and documentation must be scoped as a migration deliverable.
Basic familiarity present. VIP-level architecture and Gutenberg governance need structured onboarding.
Internal team confident with enterprise WordPress. Onboarding is optimisation, not foundation.
NEXT STEP
Get your readiness report by email
We’ll send you your score and gap analysis. Share it with your team, or walk through it with an rtCamp architect on a free 30-minute call. On the call, we’ll check your scores against what we see across 300+ migrations, flag the gaps teams usually underestimate, and recommend where to start.
