MOVE DATA

What you can move

Task data and this theme

Sign in with Firebase, then open Manage account. Export / Import / Backup / Migrate download a .mct package (tasks + history + EDI receipt). It never writes the Operator board on mc-board.net.

01

Export data

On the source host, sign in, open Manage account, click Export wizard. Step 1: all projects or one project. Step 2: all data or my dates. Download the .mct.

02

Import data on the other host

Open dest Manage account, sign in, click Import data, preview, confirm.

03

Confirm reports

Open Reports. Meters should show the live-board snapshot (280 tasks, 500 history) — not the old 100 IT/office demo.

Operator · do this now

Next steps (you)

1. Open Mission Blue home. Confirm React banner and no Export/Import buttons on home.
2. Sign in at login.html. Open Manage account — password, kit data, delete.
3. Open Reports. Confirm open/done/history/project meters fill.
4. Export wizard on A account page (project, then dates). Import that .mct on dest /kits/react/mission-blue/account-delete.html.
5. Confirm dashboard.php and reports.php still load as usual.
6. Approve PR-0249 if smoke passed.

Program · phases

What is done vs what is next

Phase 0 — shipped. React home, Firebase login pages, Manage account (EDI + delete), dest copy under /kits/, live snapshot in sample data.

Phase 1 — Operator smoke (now). The steps above. Card stays awaiting review until you Approve.

Phase 2 — Transfer pack. A→B import with ACK. Dest reports match source counts.

Phase 3 — Theme / template restore. Use Alien Dark for Backup theme / Restore theme (ember tokens). Mission Blue keeps classic-hud cyan.

Phase 4 — Store hardening. Deploy Firestore rules for mct_kits/react/mission-blue/* if you want cloud writes (file in docs/firestore-mct-kits.rules). Refresh snapshot from api.php only on request. Never SFTP tasks.json.

Phase 5 — Later kits. Remaining vanilla kits wait for your next framework call. Do not rewrite Operator dashboard.php.