Microsoft Graph Migration Tool

Things to know before starting

  • The migration tool is currently in beta. If you would like to participate in the beta, reach out to your Customer Success Manager.
  • 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. 
  • Make sure you have the correct permissions set up. 
    • If you’re migrating via enterprise app, a Microsoft global admin is required.
    • If you’re migrating via service account, ensure that the service account has delegate access on the room calendars.
  • For more background information, please see our Migration FAQ

Migration steps:

1. Navigate to the Manage > Integrations tab within Robin's web dashboard.

2. Scroll down to workplace integrations, and click “Start Migration”

Screenshot 2024-05-28 at 11.37.26 AM.png

3. Choose how to migrate: Screenshot 2024-05-28 at 11.38.39 AM.png

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. 

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 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 your calendars failed 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 roll back.

Screenshot 2024-05-29 at 12.30.34 PM.png

Common errors when migrating to Graph

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:

  • Calendar does not exist in Outlook. 
  • If you’re connecting via service account, ensure that the service account has delegate permissions for the room calendar. You can add delegation permission for room calendars individually in the Microsoft 365 admin center by navigating to: Recipients > Resources > Select the calendar > Manage delegate settings > Full access > Add service account
  • Does the service account already have delegate access? Permissions can take 24-48 hours to propagate on the Microsoft side. If it still isn’t working, it could be the incorrect service account was integrated. Please reach out to support to verify whether the intended service account was used.

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.

Did this article help?