Completing a data cleanse in your current MIS ahead of your move to Arbor is one of the most important actions a school can take to ensure the migration goes as smoothly as possible.
To help you with the data cleanse, Arbor has created a workbook that includes two checklists. These checklists are “Pre Migration Data Cleanse” & “Pre Migration Data Counts & Checks”.
You can download the workbook from the bottom of this page.
We have popped an explanation of how to complete both checklists below.
Completing the cleanse will help you to understand the quality of your data before you send it to Arbor. It will also help to make sure the data is up to date, formatted correctly, and in the right place in your current MIS - which increases the chances of the data migrating correctly to your new Arbor MIS and minimises the need to tidy up post-launch, so you can get to work on the important tasks in your new MIS!
You should start completing the data cleanse as soon as possible and sign off the checklist before your migration date.
We have provided more information in the checklist on what to look for in your current MIS and why it is important. Once you have checked this area, you should mark the “Check Complete” column.
There may be reports that you can run in your current MIS that will help you to check and update information.
Signing off your Data Cleanse
Once you have completed the checklist, you should sign off on them using the link in the workbook. Without the data check sign-off, Arbor cannot take any responsibility for the quality of your data post-launch.
It is imported to complete the data counts and checks before your Arbor MIS launches, to take a snapshot of the data that you held in your current MIS, which you can then compare to Arbor once your new MIS launches.
Work through the checklist provided in the workbook before sending Arbor your data, completing the “current MIS” column with the numbers required. Once you have access to Arbor, you’ll be able to complete the “verified in Arbor” column and are looking for the numbers that match between both systems.
You should verify the data in Arbor as soon as possible after launch to ensure the data has migrated across correctly. To help, you can download a data migration report from your Arbor MIS. Click here for more information.