Repair when the foundation is healthy
The platform is maintained, content is recoverable, journeys are simple, and priority corrections can be isolated without multiplying workarounds.
Rebuild when every change increases risk
Abandoned code, confused architecture, incompatible components, unusable content, and no deployment process can make repair more expensive than reconstruction.
Measure transition cost
A rebuild involves content, redirects, forms, data, analytics, training, and launch. Ignoring them makes reconstruction appear artificially cheaper.
Ask for two comparable scenarios
A useful diagnosis presents cost, gains, limitations, and probable lifespan for both repair and reconstruction.
Keep in mind
This guide provides a general starting point. A diagnosis must account for the actual site, access, data, and constraints before any change.