✅ The short answer:
We have a simple tool for updating MIS IDs which you can you can find on the data management page. It will walk you through the process from start to finish and alert you to any issues.
If you use Wonde, you will find that we switched your auto-syncing off once Wonde told us you were migrating. Once you use this the tool above and Wonde has given us the green light, we'll switch it back on and inform you by email.
💬 Frequently Asked Questions
Why do only MIS IDs need to be updated like this?
🛠️ Troubleshooting Guide
Why aren’t all IDs in my file matched?
Why aren’t all existing STEER accounts matched?
💬 Frequently Asked Questions
Why do only MIS IDs need to be updated like this?
MIS IDs act as the lynchpin of our student accounts, with all other data (like year group, email, name etc) attached to them. That's why, to update the MIS ID, we need to use a special tool which lets us connect the old and new IDs.
🛠️ Troubleshooting Guide
Why aren’t all IDs in my file matched?
If you are seeing this error, it suggests that there are "OId MIS IDs" in your file which do not actually match any existing account on the STEER platform. These students will simply be ignored from the update, so you can proceed if you are happy with that.
Here are the most common explanations:
🗑️ These students have been deleted from your platform by you or another member of staff
Perhaps they were leaving the school or their parents withdrew consent. They may have never actually been added on STEER.
🧑🎓 They are new students who have not yet been set up on STEER
If this student has not yet been created on STEER (but you have included them in your CSV file) then this error will show. This may be because they are new, or because they are moving into a year group which used STEER Tracking, but has not actually been imported yet (usually because the school year has not yet begun).
🎒 These students are in a year group which you don't actually track on STEER
If your school doesn't track all year groups and you simply exported a list of all students from your MIS, you may have accidentally included year groups which don't actually have STEER accounts. We won't create accounts for them in this process, so you can finalise the import if you are confident this is the reason.
🪪 You've got the wrong Old MIS ID type
STEER requires schools to provide a stable ID type for all students. However, schools sometimes need to choose from a few different options. If 100% of the students have this error, then it's possible that you are using the wrong ID type. View a student's data using the edit function on data management to check.
⌨️ There is a mistake/typo in your file or a previous import on STEER
For whatever reason, this student may simply have a discrepancy between the MIS ID on STEER and your own system. If this is the case, you will also see the error Why aren’t all existing STEER accounts matched? in the other column. If you view that, you may be able to the erroneous MIS ID.
If you finalise the import, we’ll create fresh accounts for these students when your data is next imported/synced from your new MIS (assuming they appear in the import). They will not be connected to any existing historic data.
Why aren’t all existing STEER accounts matched?
If you are seeing this error, it suggests that there are existing accounts on STEER which do not actually match any of the "Old MIS IDs" in your file. These students will simply be ignored from the update, so you can proceed if you are happy with that.
The most common explanation is:
🧑🎓 These students simply left your school last year and have not yet been wiped from STEER
To avoid any unintended data loss, we wait until January (X if you are a January start school) to wipe the accounts of school leavers. Unfortunately, this means that these students who left at the end of the year will continue appearing as "existing STEER accounts" on this page until that happens. If you are confident that that is the explanation then you can simply go ahead with the update! Sorry for the confusion, we're working on a way to improve this.
If that's not it, then here are other possible explanations:
🪪 You've got the wrong Old MIS ID type
STEER requires schools to provide a stable ID type for all students. However, schools sometimes need to choose from a few different options. If 100% of the students have this error, then it's possible that you are using the wrong ID type. View a student's data using the edit function on data management to check.
⌨️ There is a mistake/typo in your file or a previous import on STEER
For whatever reason, this student may simply have a discrepancy between the MIS ID on STEER and your own system.
Comments
0 comments
Please sign in to leave a comment.