Prove Basalt beside your incumbent on real workloads, with the rollback story written down before anything moves. The person proposing this is putting their own credibility on the line: every step here has a named exit. There is no easy migration off an incumbent this deeply embedded, and this page does not claim one. Basalt accounts for that work and is built to support it, so you are not doing it alone.
Basalt stands up next to what you already run. You validate it side by side before anything real depends on it, then migrate in stages: never a single cutover, and never production first.
Count what you run, where it runs, and what the renewal covers. The output is a number finance can use.
Real workloads, beside the incumbent, with the rollback agreed in advance.
Disconnected endpoints and edge sites first, consolidation next, core last.
Every wave has its own exit, written before it starts.
Run the numbers with your own infrastructure, then put Basalt beside your incumbent in a controlled environment, with a rollback story written down before anything moves.