Migration Architecture | PointClickCare to SeniorCRE Entity Mapping
Where this page sits. Integration philosophy is the parent doctrine: we surface systems rather than replace them, and the default motion moves no data out of your EHR. This page is the nested child that applies only when an operator qualifies into a gated exception motion — a greenfield opening or a paper turnaround — where data genuinely has to land somewhere. If you are on the default motion, read the parent, not this page.
1. PointClickCare → SeniorCRE entity map
One row per PCC entity. The transform column is the actual operation; the notes column is what your clinical and finance teams will care about.
2. Other source systems
The same canonical targets receive data from MatrixCare, Yardi, and QuickBooks. The mapping is published; only the column names on the source side differ.
3. The cutover model
Migration is a sequence, not a flip. Each community runs the same five phases.
https://seniorcre.com/migration-architecture