Migration engine
Import mapping
Member, family, billing, rank, and verification mapping for controlled migrations from incumbent systems.
Import-mapping board is live
Migration now has a field-mapping surface, which is one of the practical trust moments in switching systems.
Ready
1
Items that are ready enough to operate or demo.
Active
1
Items already represented in active workflow shape.
Watch
1
Items that need review, risk handling, or sharper rules.
Roadmap
5
2 planned and 0 blocked items in this surface.
Member field mapping
Owner: Migration
Incoming names, dates, emails, roles, and statuses need a reviewable mapping before import.
Family relationship rebuild
Owner: Migration
Family data is usually where incumbent systems leak the most operational pain.
Membership and billing map
Owner: Billing
Plan, payer, invoice, and payment states need careful reconstruction before cutover.
Rank history import
Owner: Progress
Martial arts migrations need rank history treated as first-class, not optional notes.
Owner verification report
Owner: Owner
Owners need confidence through counts, skipped rows, and human-readable warnings.