Microsoft Graph Migration Tool

Things to know before starting

  • We recommend migrating at an off-peak time to minimize disruption. In case of any errors you are able to roll back the migration to revert to your previous setup. 
  • A Microsoft Global admin or a user with an Application Administrator & Privilege Role Administrator role is required to migrate via the Enterprise app. Scopes can be limited using Role Based Access Control (RBAC).
  • For more background information, please see our Migration FAQ

Migration steps

1. In Robin's web dashboard, navigate to Manage > Integrations tab. 

2. Scroll down to workplace integrations and click Start Migration. 

Screenshot 2024-05-28 at 11.37.26 AM.png

3. Click Migrate via App.

4. This will start the OAuth flow to connect to your account. If the migration does not start immediately, you may need to do this step again. Review the permissions and click Accept to continue.

Screenshot 2025-01-16 at 1.47.29 PM.png

5. The migration will start. Depending on how many calendars you have, this could take a few minutes. You can exit this page and come back later. 

Screenshot 2024-05-29 at 12.32.58 PM.png
6. Once the migration is complete, check for any errors. Common error reasons are below.

7. You can close this page and view the status anytime.

Screenshot 2024-05-28 at 11.42.37 AM.png

8. If the migration was successful, we recommend logging in with a separate user to verify SSO and room booking is working as expected.

If most or all of your calendars fail to migrate, we recommend rolling back to your previous setup while you figure out how to resolve the errors. We suggest you roll back as soon as possible to keep your calendars in sync. Any updates to calendars done after the migration will be lost during a rollback.

Screenshot 2024-05-29 at 12.30.34 PM.png

Common errors when migrating to Graph

If all calendars fail after migrating, roll back and migrate again. This fixes issues in the majority of cases.

If most calendars were migrated successfully, we recommend fixing the individual errors instead of rolling back.

Screenshot 2024-05-28 at 11.54.02 AM.png

Here are some common reasons why there was an error with migrating the calendars:

  • A calendar does not exist in Outlook. 
  • If the app had its scope limited via an application access policy, it might not have the proper scope to access the calendars. 

Screenshot 2024-05-28 at 11.53.11 AM.png

Calendars being skipped:

If your room calendars were in a bad state prior to migrating and haven’t been synced successfully in the last 48 hours, they will be skipped. Check that the calendar exists in Outlook.

Need admin approval message

If after logging in, folks receive a “Need admin approval” message, use a Microsoft global admin account to sign in and consent on behalf of the organization.

Articles in this section

Was this article helpful?
1 out of 1 found this helpful
Share