How we Migrate Staff Contracts and Business Roles?

This article outlines the process for migrating staff contracts and business roles from various management information systems (MIS) such as SIMS, Bromcom, and Integris. It details what data is migrated, including contracts, roles, and allowances, and provides guidance on editing this information post-migration. It also addresses the migration of future staff and the importance of end dates for staff who have left.

Please note: the following includes schools migrating from SIMS via the GroupCall migrator. If you need to raise any data discrepancies after your migration, please contact Arbor support or your dedicated partner, and we will be advised of the next steps.

Business roles:

• We migrate business roles from SIMS (.bak migrations), Bromcom, Progresso, CMIS and ScholarPack. For more information, please visit: How do we migrate Business Roles from SIMS?
• We migrate business roles from SIMS for GroupCall migrations. Initially, we will base this on staff contracts, if they are available. If we don't have staff contracts, we will use data from additional SIMS columns ('roles', 'teacher Category', or the 'Is Teacher' flag). Where there is no data present, we will default the role to 'Teacher'. 
• For Integris, we only migrate business roles where contracts exist - this migrates from the roles section in Integris staff contracts. 

You can see how to find and amend business roles after the migration here: Adding a Business Role to a member of staff

Contracts:

• We migrate staff contracts, contract posts, post allowances, and post salaries from SIMS, Bromcom, Integris, Progresso, CMIS, and ScholarPack.
• We also migrate Contract Documents from SIMS.
• We also migrate Contract Positions from Integris and Progresso.

If you need to edit staff contracts after migration, you can find instructions on how to do so here. You can also see how to edit contract posts and positions here.

Future staff

Staff who are not currently employed but will start in the future will be migrated. Their future Contract and future Business Role will be migrated, and the staff member will become current on the same date they were set to start in your previous system.

Service agreements

We do not migrate service agreements, so staff without a contract may be migrated as current staff. The end date of the contract will determine whether they are migrated as current staff.

Staff who have left

To ensure that staff who have left your school are migrated correctly, ensure that the contract, staff post, and business role all have an end date input.

If one of these items does not have an end date, staff will be assigned a business role upon migration to Arbor and will be migrated as current staff. You can see how to resolve this here: The current staff list has missing staff or includes people who have left

Not all Staff Allowances have migrated, why?

Arbor only allows Allowances linked to a staff contract. Some other MISs, such as ScholarPack, don't have this requirement. If you've created standalone allowances, we haven't migrated them. You can see how to add them here.