How we Migrate Looked After (In Care) and Local Authority Information

This article explains the migration process for Looked After (In Care) and Local Authority information from various systems like SIMS, Bromcom, and ScholarPack. It details what data is migrated, including in-care statuses and responsible local authority details, and provides tips for managing the data post-migration.

Please note the following can vary for a GroupCall API migrator, we are working on adding the GroupCall Migrator specifications to this guide. If you need to raise any data discrepancies post migration please contact Arbor support or your dedicated partner and we will be advised of the next steps.

Local Authorities

We migrate details of students' Responsible Local Authority from SIMS, Bromcom and ScholarPack. You can find this in the Looked After (In Care) section of the student profile, and you can change this using these instructions.

We do not migrate details of students' Home Local Authority, but you can add these details by following these instructions.

Looked After (In Care)

• We migrate in care statuses (current only, not Post Looked After) from ScholarPack. Top Tip: The dates will migrate as Ongoing as Scholarpack doesn't store dates for this field.
• We migrate in care statuses (whether a student is Looked After or Post Looked After) from SIMS, Bromcom, Integris, Progresso and CMIS.

Top Tip: When migrating from SIMS, as this is taken from point-in-time data in the census section, you may see multiple instances. You will need to amend these after migration.

You can see how to edit Looked After (In Care) here: Adding a Looked After (In Care) or Post Looked After status