This guide is designed for Secondaries moving to Arbor and will show you how to check migrated data in Arbor and highlight some common migration checks.
The Data Checking Process
To make sure the data migration is accurate, we give secondary schools one dummy data run - once migration is complete you will be able to log in to your Dummy site to see how your schools' data looks in Arbor.
You'll need to thoroughly check the migrated data ahead of your final migration to ensure everything transfers as expected, and continue to cleanse the data in your current MIS.
You will also need to complete these checks again after your final migration has happened.
You should record your data checks in tab 4 of your Onboarding Workbook, so you can keep track of the work still to be done. The Current MIS Counts should be completed just before your migration to Arbor.
Using the Data Migration Report
After each migration, you can view a summary of the migrated data by downloading your Data Migration Report.
How to download and use the Data Migration Report
To access the Data Migration Report, you will need the Student Profile: Admin: Administer All Students permission. If you don't have the permission, you'll need to ask your admin team to give you permission using these instructions.
1. Go to School > Data > Data Migration Report
2. Click the Download QA Report button
A lot of the information in the report is linked to your Arbor system. For example, if you click on the section that shows your total number of Pupil Premium students, it will take you to a list of those students in Arbor.
There are some figures which you cannot click, but you can report on these here:Additional custom reports for your Data Migration QA Report
You can use the pre-migration data counts from your Onboarding Workbook to quickly compare figures and highlight any discrepancies.
Handling Discrepancies
If you find any discrepancies between the report and your data in the previous MIS, please report these directly to your Arbor Support team. If you are Partner Supported, you will need to raise discrepancies with your Support Partner directly.
When raising data discrepancy issues, please include as much information as possible on the ticket including examples from both Arbor and your previous MIS. You can see how to do this here: How can I report migration issues?
Sign Off
After verifying data accuracy on your site by using the report to compare data with your previous MIS, sign off the report by going to School > Data > Data Migration Report and clicking the Sign Off button.
Migration Data Counts
Your Onboarding 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 final migration.
In these videos, we'll show you how to find the data needed for these counts in Arbor.
Counting Student Data
Counting Staff Data
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.
Checking Student 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 10 students.
Checking Staff Data
We recommend checking a sample of staff, with a range of job roles and start dates. You should check a minimum of 10 staff.
Checking Attendance Data
We recommend checking a sample of attendance certificates to ensure that all attendance marks and absences 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.
Checking Behaviour Data
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.
Checking Exams Data
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.
Checking Timetables
You should check a sample of student and staff timetables, and review any timetable clashes.
Checking Student Enrolments
Carefully check the enrolment figures for the whole school, year groups, registration forms and courses.
Checking Medical Conditions and Dietary Requirements
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. You can see more information here: Migrated Dietary requirements, Medical Conditions, Events and Notes
Comments
Article is closed for comments.