MyLogin | MIS migration guide

Your Management Information System (MIS) is the central hub for your school data. Because MyLogin identifies users based on unique IDs synced via Wonde, switching MIS providers (e.g., moving from SIMS to Bromcom or Arbor) can disrupt how users are recognised.

Without proper preparation, data can appear to the system as a "brand new" set of users which can result in lost credentials, matching and saved passwords.

Use this guide to ensure a smoother transition, protect user data, and minimise technical disruption during your MIS migration.

Before you migrate (action required) 

MyLogin (via Wonde) now attempts to match existing student users using their Unique Pupil Number (UPN). To make migrations smoother and to prevent students from losing credentials, matching and saved passwords, you’ll need to ensure:

• UPN scope is approved: In the Wonde School Portal, go to MyLogin > Settings > Permissions and ensure "Student UPN read" is approved.
• Data consistency: Ensure UPNs are correctly populated in both your old and new MIS.
• Notify us: Email [e-mail] with your migration date so we can support and monitor the sync.

💡 Using MyLogin Lite? While you still need to follow the UPN steps to protect credentials and saved passwords, you can skip any steps related to Google/Microsoft "User Matching". 

⚠️ Please Note: Unlike students, Staff do not have UPNs. Their IDs will change regardless of migration success. Staff will always need to reset their passwords. If you use full MyLogin, you will also need to re-match their Google/Microsoft accounts after a migration.

After migration

To confirm if your user IDs were successfully maintained following the migration, please review the Activity Logs in the MyLogin portal

Scenario A: Success ✅

• What you see: Only Staff members show as "User Created" (and perhaps a few truly new students) after the migration date.  
• What it means: Students kept their old IDs. No action is needed for students.

Scenario B: IDs reset ⚠️

• What you see: Your entire student list shows as "User Created" after the migration date.  
• What it means: Students have "brand new" accounts. You must re-issue all student credentials.

Final task list

Task	For staff	For students
Passwords	Use "Forgot Password" or re-invite them.	Only if Scenario B: All student credentials will need to be re-distributed to users
Matching	Re-link Google/Microsoft in "User Matching." (Not required for MyLogin Lite)	Only if Scenario B: Re-link Google/Microsoft in "User Matching." (Not required for MyLogin Lite)
Saved passwords	Must be re-entered by the admin or user in MyLogin.	Only if Scenario B: Must be re-entered by the admin or user in MyLogin.
Apps	Re-sync or contact the app provider.	Only if Scenario B: Re-sync or contact the app provider.

Need a hand?

If you have any questions or need further support please contact the team on [e-mail] or [phone].