Your migration, tracked
Set your path and renewal date once. From then on this page greets you with the countdown, where you should be against the back-planned schedule, and a checklist you tick off as phases land. Nothing is uploaded; the plan lives in this browser's storage and nowhere else.
Saved only in this browser (localStorage). No account, no server, clearing site data removes it. Come back any time on this device and the plan will be here.
How to use it
A migration runs nine to twenty-one weeks; the failure mode is losing the thread between waves. This workspace is the thread: check the pilot off only when the runbook actually survived contact with real workloads, and treat a "Behind plan" state as a scheduling decision, not a moral one, you can recover slack by shrinking wave scope, or re-plan against a later renewal. The Vendor Watch feed is worth a glance on the same visit: licensing moves mid-migration occasionally change the destination calculus, and it takes thirty seconds.