Free · no signup · privacy-first
Tools that answer the meeting-stopping questions
Four tools, four questions every migration decision hits: what's in the estate, does the timeline fit, what does it save, and how locked in are we. Everything runs in your browser; nothing requires an account.
VMware exits
RVTools Estate Analyzer
"What in my VMware estate will fight the migration?"
Drop your RVTools .xlsx and get licensing core counts, estate totals, and a blocker report (RDMs, FT, USB dongles, snapshots), parsed entirely in your browser, never uploaded.
Open the tool →
All paths
Renewal Deadline Planner
"Can we still migrate before the contract renews?"
Pick any of the 88 published migration paths and your renewal date; the planner back-schedules all six phases from the deadline, gives a verdict, and exports the plan as calendar events.
Open the tool →
All paths
3-Year TCO Calculator
"What would leaving actually save us?"
Model source vs. target cost over three years with product-specific sizing units, support tiers, and migration cost included, every figure editable.
Open the tool →
All paths
My Migration Tracker
"Where are we against the plan this week?"
A private workspace saved only in your browser: renewal countdown, back-planned phase schedule, and a checklist you tick off as the migration progresses. No account.
Open the tool →
Research
The Lock-in Index
"How hard is this product to leave, really?"
Original research scoring 60+ commercial products on five lock-in dimensions, licensing power, data portability, proprietary surface, ecosystem, and exit-path maturity, as a browsable heatmap.
Open the tool →
How the tools fit together
They chain in the order a real decision runs: the analyzer (or your own inventory) establishes what you actually have and what blocks; the Lock-in Index calibrates how hard the incumbent will resist; the calculator turns sizing into a 3-year cost comparison; and the renewal planner tests whether the whole thing fits before your contract forces the question. The output of each step is the input to the next, and every migration path page links the relevant guide for execution.