Migration Tracking & Sign-off
Track each entity's progress through the migration lifecycle, and get the two-party go-live sign-off that gates loading a wave into C3.
Overview
Migration progress is tracked entity by entity, per wave, and the final gate before a wave loads to C3 is a two-party go-live sign-off. This is Phase 9 — the tracking is continuous throughout the process; the sign-off is its last step. It's owned by both sides: NewCo (the branch / source system) and Associa (implementation / target system).
The migration lifecycle
Each entity moves through a fixed set of states, in order:
Field Mapped → Ingested → Data Quality Reviewed → Standardized → App Validated → C3 UAT Loaded → C3 UAT Validated → C3 Prod Loaded
| State | Meaning |
|---|---|
| Field Mapped | Field mapping analysis is complete for the entity (Phase 2). |
| Ingested | The entity has been ingested into Strata (Phase 5). |
| Data Quality Reviewed | The review pass is complete and quality issues are triaged (Phase 7). |
| Standardized | Source codes are mapped to standards — applies only to GL accounts, charge types, delinquency statuses, and reimbursables (Phase 6). |
| App Validated | Validation is complete in the app (Phase 8). |
| C3 UAT Loaded | The entity has been loaded into C3 UAT (Phase 10). |
| C3 UAT Validated | The entity has been verified in C3 UAT (Phase 11). |
| C3 Prod Loaded | The entity has been loaded into C3 Production (Phase 13). |
Transitions are manual
State transitions are fully manual. A person advances an entity's state when the corresponding work is verifiably complete — no ingestion, mapping, or validation activity moves an entity forward on its own. Every transition is recorded with who made it, when, and an optional comment.
Current lifecycle states are visible per entity on the Data Availability page.
The go-live sign-off (two-party)
The wave-level gate is a single readiness confirmation — Mark ready for Go-Live — on the wave detail page.
It requires approval from both team affiliations: one Source System (NewCo) representative and one Target System (Associa) representative, each with an optional comment. The wave is only marked ready when both parties have approved. All sign-offs are logged with who approved, when, and their comments.
Mapping completeness and the cross-entity validation roll-up shown on the wave detail page are the informational signals that feed the decision — the two-party confirmation itself is the gate. See Roles & Access for how team affiliation determines each side.
After sign-off
Once a wave is marked ready for go-live, it's eligible for C3 UAT loading. See C3 UAT Loading & Testing.
Validation
Validate each association with the guided wizard, then resolve cross-entity and financial reconciliation panels — the results roll up into the wave's go-live sign-off.
C3 UAT Loading & Testing
Once a wave is signed off, its data is loaded into C3 UAT by the loading pipelines, then tested in C3 UAT before go-dark.