Migration Assessment & Roadmap

Most migration pain is purchased in the first month: the wrong tool, the wrong wave order, or a promise to finish before anyone counted the databases. An assessment exists to stop that. We spend a fixed window on inventory, interviews, and a look at the target platform so leadership gets a plan they can fund — or a clear recommendation to wait.

The output is not a generic maturity score. It is a host- and application-level backlog: what moves, what is retired, what is blocked on a vendor, and what the first 90 days should contain. We include dependency maps, a first-wave candidate list, and the operational gaps (backup, identity, observability) that would make any landing unsafe.

Cost is treated as a range with assumptions, not a fake single number. We separate one-time migration labour, landing-zone build, dual-running, and the steady-state cloud or datacenter bill. Risks are written as events with owners — license audits, change freezes, appliance replacements — so the program can sequence around them.

You can take the roadmap to a procurement process, to an internal team, or back to Audmins for delivery. The assessment is useful even if we never run the cutover. That is the point: decide with evidence.