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.
Overview
After a wave is signed off as ready for go-live, its data is loaded into the C3 UAT environment and tested there. These are Phases 10 and 11. The loading itself is run by Data Platform engineering team; the testing is done by Implementation and the branch directly in C3 UAT.
C3 UAT loading (Phase 10)
The Loading team's pipelines consume the mapped records produced during Standardization — mapped GL accounts, charge types, delinquency statuses, and reimbursables. These mapped records are the interface between the app / Strata and the loading pipelines.
- The synthetic Setup Association (C3 Id
1) loads alongside the real associations and carries the organization's global mapping set into C3. - Every migratable record carries its External ID (your source-system identifier) and is assigned its C3 Id during loading — see the Data Identity Model.
When loading completes cleanly, each entity advances to the C3 UAT Loaded lifecycle state.
C3 UAT testing (Phase 11)
Testing happens directly in C3 UAT — it isn't done in this app. Implementation and the branch verify that the migrated data works correctly in the TownSq ecosystem:
- Associations display correctly (name, address, manager info).
- Unit structure sits under the correct associations with the right types.
- Account balances, transaction history, and charge types are correct.
- Member roles are assigned correctly (owners, tenants, occupants, board members, CAMs).
- Financial operations work (bank accounts, recurring charges, delinquency settings).
- Vendor relationships and GL integration with C3's financial modules are correct.
When an entity is verified in C3 UAT, it advances to the C3 UAT Validated lifecycle state. Passing UAT testing clears the way to Go-Dark.
Associa team members: the loading pipeline details are maintained by the Loading team in Confluence at Strata-to-C3 Process Flow.
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.
Go-Dark
On the go-dark date, pull fresh source data to capture changes since the initial ingestion, and re-validate the critical financial and membership data.