The first big milestone of your move to Arbor is the migration of data from your existing MIS. Your Project Manager will give you details of our migration process during your Discovery meeting.
To make sure the migration is accurate, we give secondary schools two dummy data runs - we’ll take a backup of your data, migrate it to Arbor, and you can log in to your Arbor system to see how it looks. You can see more information about what to do during each here: How to use your Arbor dummy sites
Once you’re into your Arbor dummy site, you’ll need to thoroughly check the data that has migrated and cleanse the data in your existing system ahead of the second dummy run. This guide will show you how to check data in Arbor, and highlight a few common migration problems.
Top Tip: You should record your data checks in your Implementation Workbook, to make it easy to keep track of the work still to be done.
Using the Data Migration Report
After each migration, you can view a summary of the migrated data by downloading your Data Migration Report. This interactive report can help you quickly identify discrepancies in the migrated data.
To access the Data Migration Report, you will need the Student Profile: Admin: Administer All Students permission.
A lot of the summaries in your Data Migration Report are linked to your Arbor system, so will take you to the relevant tables to look more closely at the data. For example, you can click the summary of migrated Pupil Premium students to go straight to the demographic report that shows Pupil Premium eligibility.
You can use the pre-migration data counts in your Implementation Workbook to quickly compare the data in Arbor with your old system.
Migration Data Counts
Your Implementation Workbook has a list of recommended data counts to perform in Arbor. This is a great way to identify discrepancies between the two datasets. You should make any changes in your existing system ahead of your second dummy data run or final migration.
In these videos, we'll show you how to find the data needed for these counts in Arbor.
Migration Data Checks
After each migration, it is important to thoroughly check your student and staff data to make sure it has migrated correctly. As well as checking student and staff profiles, we recommend undertaking detailed checks of migrated attendance, behaviour, exams, timetable, and enrolment data.
We recommend checking a sample of students from different year groups, with a range of demographic indicators (e.g. FSM, EAL, SEN Status, Dual Registered). You should check a minimum of 20 students.
We recommend checking a sample of staff, with a range of job roles and start dates. You should check a minimum of 10 staff.
We recommend checking a sample of attendance certificates to ensure that all attendance marks and absence notes have migrated correctly. You should also use the Attendance Statistics screen to check that the number and percentage of present, absent, and late marks match your previous MIS.
You should carefully check that statutory behaviour data - fixed-term and permanent exclusions - have migrated. Depending on your previous system, we may be able to migrate historic behaviour incidents - in this case, you should check a range of students to confirm that these have all migrated.
Your exams officer should carefully check candidates, entries, and results. Check out our Top Tips for Exams Officers for more information about getting started with Exams.
You should check a sample of student and staff timetables, and review any timetable clashes.
Carefully check the enrolment figures for the whole school, year groups, registration forms and courses.
If you have a Sixth Form, check that your Programmes of Study (e.g.A Level English Literature 2yr) and Programme Instances (e.g. A Level English Literature 2yr, 2019 - 2021) have migrated. Check that students are enrolled into the correct programme instances.
Because of the flexibility with these fields in other MIS systems, you'll need to check how they have been migrated. You may wish to update them in your previous system to ensure it's easy to manage these when your final site is released. You can see more information here: Migrated Dietary requirements, Medical Conditions, Events and Notes
What if data has migrated incorrectly or not at all?
If when doing your checks, you see that certain data has migrated incorrectly, or data you were informed would migrate does not, please report this.
- If you are supported by another provider, please contact them.
- If you are supported by Arbor, please contact the Arbor Support Team if supported by Arbor, or your Support Partner if not supported by Arbor. Include details of the issue and a screenshot of where you can see this information in your previous MIS so we can investigate.
Article is closed for comments.