Migration operations
Migration Ops
A cutover cockpit for source exports, import mapping, dry-run verification, owner sign-off, rollback planning, and first-week trust.
Ready
2
Migration items ready to feed dry run or cutover.
Watch
3
Items with warnings that need owner or migration review.
Planned
3
Items not ready for controlled apply.
Confidence
56%
Average confidence across migration and mapping work.
preflight
1 items
0
Ready
0
Watch
0
Blocked
Collect source exports, owner constraints, and known messy areas
mapping
5 items
2
Ready
2
Watch
0
Blocked
Use mapping in next dry run
dry run
1 items
0
Ready
1
Watch
0
Blocked
Run dry-run verification and review skipped rows
verification
1 items
0
Ready
0
Watch
0
Blocked
Document fields, transforms, and verification examples
cutover
0 items
0
Ready
0
Watch
0
Blocked
No current item
Migration queue
Ranked by readiness, trust risk, and whether the owner could safely approve a dry run.
Member field mapping
Mapping layer · Owner: Migration
86%
Score
mapping
Stage
Use mapping in next dry run
Gates
Field mapping approved
Transform rules documented
Sample rows checked
Owner-readable report
Apply disabled until verified
Risks
Required field gaps
Duplicate member records
Status mapping mismatch
Evidence
Owner: Migration
Status: ready
Incoming names, dates, emails, roles, and statuses need a reviewable mapping before import.
Rank history import
Mapping layer · Owner: Progress
76%
Score
mapping
Stage
Review active transform results
Gates
Field mapping approved
Transform rules documented
Sample rows checked
Owner-readable report
Apply disabled until verified
Risks
Promotion history loss
Belt/stripe ambiguity
Coach trust erosion
Evidence
Owner: Progress
Status: active
Martial arts migrations need rank history treated as first-class, not optional notes.
HRJJ
GymDesk · Owner: Dom
66%
Score
dry run
Stage
Run dry-run verification and review skipped rows
Gates
Owner sign-off
Count reconciliation
Skipped row review
Rollback window
First billing run hold
Risks
Identity duplicates
Household payer mismatch
Rank/progress history loss
Dry-run drift before cutover
Evidence
Source system: GymDesk
Stage: trial import
This is the proving-ground migration and should feel like a real cockpit, not a one-off back-office script.
Family relationship rebuild
Mapping layer · Owner: Migration
58%
Score
mapping
Stage
Resolve warnings before owner sign-off
Gates
Field mapping approved
Transform rules documented
Sample rows checked
Owner-readable report
Apply disabled until verified
Risks
Guardian relationship ambiguity
Pickup permission drift
Billing authority mismatch
Evidence
Owner: Migration
Status: watch
Family data is usually where incumbent systems leak the most operational pain.
Bayside Grappling
Mindbody · Owner: Migration specialist
52%
Score
mapping
Stage
Approve field transforms and household/billing assumptions
Gates
Owner sign-off
Count reconciliation
Skipped row review
Rollback window
First billing run hold
Risks
Identity duplicates
Household payer mismatch
Rank/progress history loss
Evidence
Source system: Mindbody
Stage: mapping
Good example of how different incumbents change both data cleaning and trust-building work.
Membership and billing map
Mapping layer · Owner: Billing
38%
Score
mapping
Stage
Document fields, transforms, and verification examples
Gates
Field mapping approved
Transform rules documented
Sample rows checked
Owner-readable report
Apply disabled until verified
Risks
Plan mismatch
Failed payment state drift
GST/accounting confusion
Evidence
Owner: Billing
Status: planned
Plan, payer, invoice, and payment states need careful reconstruction before cutover.
Owner verification report
Mapping layer · Owner: Owner
38%
Score
verification
Stage
Document fields, transforms, and verification examples
Gates
Field mapping approved
Transform rules documented
Sample rows checked
Owner-readable report
Apply disabled until verified
Risks
Owner cannot trust imported counts
Warnings hidden in technical logs
Evidence
Owner: Owner
Status: planned
Owners need confidence through counts, skipped rows, and human-readable warnings.
Southside Jiu Jitsu
Manual spreadsheets · Owner: Ops lead
34%
Score
preflight
Stage
Collect source exports, owner constraints, and known messy areas
Gates
Owner sign-off
Count reconciliation
Skipped row review
Rollback window
First billing run hold
Risks
Identity duplicates
Household payer mismatch
Rank/progress history loss
Inconsistent column names
Evidence
Source system: Manual spreadsheets
Stage: preflight
Not every migration is system-to-system; some are really workflow rescue missions in disguise.
Cutover runbook
The minimum reliable switching-system path for a real gym.
Preflight
Collect exports, source quirks, critical dates, billing freeze windows, and owner expectations.
Mapping
Approve member, household, plan, payer, rank, attendance, and waiver transforms before import.
Dry run
Run import into review mode, compare counts, inspect skipped rows, and produce owner-readable warnings.
Cutover
Freeze source changes, final export, import, spot-check priority members, and hold first billing send.
Rollback
Keep source export, import batch ID, applied-row ledger, and reversal plan visible before launch.
Durable tables next
What this should become once backed by real import state.
migration_projects
Source system, gym, owner, stage, freeze window, cutover window, and rollback owner.
import_mapping_rules
Source field, target field, transform, required flag, warning behavior, and sample rows.
import_dry_runs
Counts, skipped rows, warnings, critical blockers, import batch ID, and owner sign-off.
cutover_checklists
Freeze, final export, run import, verify priority members, billing hold, and rollback checkpoints.