How we migrate Language and EAL

This article explains the process of migrating Language and EAL data for students from various systems to Arbor, detailing how First Language is treated and the implications for EAL status. It also guides managing incorrect EAL flags and adding additional languages, noting that bulk amendments are not possible.

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.

We migrate Language and Language Ability for students (not for guardians or staff) from SIMS, ScholarPack, Integris, ScholarPack and Progresso.

When migrating from SIMS, the student's First Language will be migrated to Arbor as their Native Language.

Any First Language set as Believed to be English or Refused will not set the student's language as English. This then flags the student as EAL (English as an Additional Language), because their native language may not be English.

For any students that are flagging as EAL incorrectly, you can see how to manage EAL statuses here, or add additional languages here.

It is not possible to amend this in bulk.