Firebase migration: what's ready to cut off

MEIT v1 (Firebase) → v2 (our server). Read from our server only; this page never reads Firebase.

Connecting…

–ready for cut-off

–syncing with Firebase

–already on v2

–still on 14 Oct snapshot

Modules

Loading migration status…

How to read this page

Same as Firebase (big bar). 100% means every Firebase record of that module exists in v2 with identical content and has been filed into v2's tables. It is measured by a full record-by-record check every night at 01:30. Between checks, every change made in v1 is copied across as it happens, so the figure stays true.
Ready for cut-off needs: the live link on, nothing waiting to be filed, the last check at 100%, and 7 clean nights in a row.
Snapshot loaded (thin bar) is how much of the 14 Oct copy loaded into v2 without errors. A snapshot module is not kept in step: its v2 data is as of 14 Oct.
Already on v2 means staff work in v2 and Firebase is no longer the source. Any Firebase write that still arrives for it is blocked and flagged red.
The page checks the server once a minute and redraws only when the server's data changed.