Stabilize or Rebuild?
Decide the safer first move for an aging PHP, CMS, ecommerce, portal, or admin system that still runs important work.
Answer the system as it exists today, then get a practical recommendation, plain-language rationale, risk map, and next-step list. Rebuild is one possible outcome, not the default.
What you get
- Directional first-move recommendation
- Why it fits the current situation
- Main risks to address before bigger scope
- Copyable and printable report summary
Best used when
You need a grounded first direction before promising a migration or rebuild plan, especially when backup confidence, hosting reality, or workflow fragility are still partly unclear.
Start with what is true today, including uncertainty. Unknown backups, unclear hosting, or fragile repeated work are often the reason to slow down before promising bigger change.
Quick briefing
The four paths
The recommendation explains which of these is the safest first move right now, and why. “Wrap” means keeping the old system running while moving fragile repeated work into safer workflows around it.
Assessment readiness
0% answered0 of 23 question groups answered. Start with the facts you know. Uncertainty is part of the signal.
Report readiness
The report unlocks after at least 6 answered question groups.
Honest partial knowledge is more useful than polished guesses. Unknown backup, hosting, or publishing details usually justify a steadier first move.
Map the current reality
Work through the parts you can confirm today. Unknowns around hosting, backups, recovery, or update workflow are useful signals, not mistakes to hide.
Start with the parts you can answer confidently. You do not need every fact upfront for the form to become useful.
Report unlock
6 more answered question groups unlock the first-move recommendation.
Best approach
Pick the closest description of how things work now, not the cleaned-up future state.
Next useful section
System context (0 / 4 answered)
Assessment map
Move in order or start where the facts are easiest to confirm.
0 of 23 question groups answered
Focus here next
System context
What kind of system this is, roughly how old it feels, and whether the knowledge to change it safely still exists.
Focus here next
Hosting and change safety
How the system is hosted, how code changes reach it, and whether changes are tested before going live.
Focus here next
Data, backups, and recovery
Where important data actually lives, how recoverable it is, and whether its structure is understood well enough to move or repair safely.
Focus here next
Day-to-day operations
How much of the daily update work depends on spreadsheets, manual steps, awkward publishing flows, or needing a developer to make routine changes.
Focus here next
Business dependency
What the system directly touches in the business and what the real cost would be if it stalled, broke, or became too slow to change.
Focus here next
Change pressure
What people are already pushing for, and whether there is enough clarity and control to act on it safely.
Optional examples
See how a similar system reads
Need a reference point before you keep going? These example systems show how different situations lead to different first moves. Use them to calibrate your own answers, not as a template to force-fit your situation.
First-move recommendation
Answer at least 6 question groups to unlock the first-move recommendation.
Once enough signal is in place, the report appears here with a recommendation, rationale, next steps, and a copyable summary. "Not sure" answers are valid, they lower confidence, but uncertainty is itself a risk signal and often points toward the safer first move.