Migration support and escalation

Your named contacts

• Deployment engineer. Your primary technical contact from scoping through the final cutover. Named, not a queue.
• Solutions architect. Owns boundary and inheritance questions, and stays engaged through your own authorization work.
• Mission support operations. Owns hardware allocation, provisioning timelines, and anything touching physical delivery.
• Security Operations Center. Continuous coverage for anything touching platform integrity, during a migration or otherwise.

Escalating a window at risk

If a cutover window is at risk, contact your deployment engineer directly rather than filing a ticket. Tickets are triaged on a normal schedule and a date-driven risk is not a normal schedule.

Tell us what the date is tied to. A window driven by a contract option exercise gets handled differently from one driven by team availability, and we cannot make that judgment without knowing.

Escalating early is not an imposition. A provisioning delay found three weeks out is a scheduling problem; the same delay found three days out is an outage.