Atlas migration — weekly status

Week of Jul 27 2026 · report 11 of 16

At risk

68% completeTarget cutover Sep 14 2026

Migration work is on plan technically — 41 of 60 services now read from Atlas, and last week’s dual-write cutover held for six days with no data drift. The risk is contractual, not engineering: the SSO vendor contract is still unsigned, which gates the identity migration and therefore the cutover date. We need a decision on the cutover date this week, because a slip past Sep 14 pushes us into the clinic onboarding freeze.

Done this week

In progress

Blocked

Risks

RiskSeverityMitigation
Cutover slips past Sep 14 into the onboarding freezeHighDecide the date this week; hold Sep 21 as the only fallback
Untested behaviour above 1.5× peak loadMediumQuota increase, then test Aug 7; shed non-critical jobs if refused
Reconciliation job masks slow drift on low-traffic tablesMediumAdd per-table row-count assertions, shipping Jul 31
Single owner of Atlas schema knowledgeLowPair Ines on schema reviews from Aug 3

Decisions needed

  1. Confirm Sep 14 as the cutover date, or move it to Sep 21 now.Owner: Mara Chen · needed by Jul 31. Deciding later costs us the comms window.
  2. Approve escalating the SSO contract to the vendor’s VP of Sales, or switch to the fallback provider.Owner: Dana Whitfield · needed by Jul 30.
  3. Accept a 1.5× load test if the quota increase is refused.Owner: Devon Okafor · needed by Aug 5.