Free tool
Score your migration out of 100 before you agree a launch date, and see which three variables are driving the risk.
What it outputs
Risk score
A single number from 0 to 100
Status
Green, amber or red verdict
Top three risks
The variables driving your score
Traffic loss band
Typical loss for this migration type
What this tool does
This calculator converts a migration plan into a single risk score out of 100, then names the three variables contributing most to it. It is the same pre-launch scoring we run on every Visionary migration, and it exists because most migration disasters are governance failures rather than technical mysteries.
It takes seven inputs: migration type, the percentage of URLs changing, one to one redirect coverage, schema parity, content parity, whether a pre-launch test environment exists, and the launch timeline. It returns the score, a green, amber or red verdict, your top three risk drivers, and the typical short-term traffic loss band for that migration type drawn from our client portfolio.
It is built for in-house marketing leads and development teams who have a replatform, CMS swap, rebrand or redesign in the pipeline and need an honest read before committing to a date. The full method, phased rollout model and 47 point checklist sit on our SEO migration page, alongside the technical SEO work that follows a launch.
The calculator
Risk score
55/100
AmberAmber - close the top-3 gaps before launch.
Top-3 highest-risk variables
How to use the results
Below 25 is a green light, and you can proceed with the plan you have. Between 25 and 65 is amber, which means close the top three gaps before you launch rather than after. Above 65 is red: a single day cutover at that score is how sites lose a third of their organic traffic, so the plan needs rebuilding before a date is agreed.
Redirect coverage carries the heaviest weight in the score, and rightly so. A gap here means live URLs with equity pointing at 404s on launch day. Getting to a genuine one to one map for every indexed URL, validated for chains, moves the score further than any other single action.
The three variables listed are ranked by contribution to your score, so work them in that order. Change one input at a time and rerun. If a change barely moves the number, it was not the constraint, and you have just saved your development team a sprint.
Moving from a single day cutover to a phased four week rollout, and adding a full pre-launch test environment, together remove up to thirty points. That is usually cheaper and faster than cutting features from the new build, so try the timeline levers before you start negotiating scope away.
Worked example
A CMS swap with 60% of URLs changing, 80% redirect coverage, partial schema parity and a single day cutover scores in the red band. Lifting redirect coverage to 100%, closing schema parity, adding a full test environment and moving to a phased four week rollout drops the same migration into the green band without changing a single feature of the new build.Same build, same team, thirty fewer risk points.
Redirect coverage
80% to 100%
Launch model
Cutover to phased
Verdict
Red to green
FAQ
Next step
Send us the migration you are planning and we will crawl the test environment, build the redirect map and give you a phased launch plan with the risks scored properly.
Get a Migration PlanStart Here
Tell us about your business and we'll show you exactly where the opportunities are - no obligation, no sales pitch.
■ Senior specialists only
■ No long-term contracts
■ Free audit included