Skip Ribbon Commands
Skip to main content

How do I migrate Exchange or Office 365 resources to Google resources?

Last Update: 3/13/2017 11:13 AM

​How do I migrate Exchange or Office 365 resources to Google resources?​

Answer:

 

Using MigrationWiz, it is possible to migrate Office 365 resource calendars to Google resource calendars by performing the steps detailed below.

The two most important elements that work together when migrating resource calendars to Google are permissions and folder mappings. Learn more about folder mapping by reviewing the Knowledge Basic article Can I add folder mappings MigrationWiz?

The calendar should migrate with any single Destination user account that has "make changes and manage sharing" access.

To successfully migrate an Exchange or Office 365 resource calendar to a Google calendar, perform the following steps:

 1. Go to your Google admin console: https://admin.google.com and create a new resource calendar. Here is a Google article on how to do this.

 2. As the admin user, go to the Google Calendar and click on Browse Interesting Calendars.

 3. Click on the More tab at the top of the calendar list, and select the resource calendar you just created. The calendar has been added to your list of available calendars in Google Calendar.

 4. Share the calendar with the user you want to migrate the calendar with. This user will show up as the "creator" of all the shared events in the Destination, Google Apps. Any user will work, and although we recommend applying a single user the permissions before the migration, it will not be a problem to add multiple users. You will end up adding the rest of the users to the calendar after the migration.

 5. In the Share with Specific People section, change the permission type to Make changes AND manage sharing. To the left, add the user with whom you would like to share the calendar. You can learn more about changing calendar ownership in this Google Apps article.

 6. Go to your project's Advanced settings in MigrationWiz and add MigrateGmailAllCalendar=1 as a Support Option.

 7. Add recipient mapping in the format of: RecipientMapping="SourceResourceAddress->resourceuser_domain.com@resource.calendar.google.com". You will want to replace "SourceResourceAddress" with the email address of your Source resource mailbox. You will also want to exchange the resourceuser_domain.com@resourec.calendar.google.com with the address of the resource calendar in Google.

 8. Add the folder mapping: FolderMapping="^Calendar->NameOfDestinationResourceCalendar" and replace the "NameOfDestinationResourceCalendar" with the display name of the resource calendar as it appears in your Google Calendar App.

 9. Go back into the project so you can see the list of users you are going to migrate. To migrate the resource calendar, you will need to configure the Source address as the resource mailbox and the Destination as the user you applied the calendar permissions to.

10. Start the migration as a Full Migration, and be sure Calendars is selected when you start the migration. It is not a problem to have other data types selected at the same time for the same user.

11. When you migrate the user that has permissions to the resource calendar, the calendar items will be mapped to the resource calendar at the Destination because of the folder mapping you added above.

12. When the migration completes, go back to Share this Calendar. In the Share with Specific People, grant permissions to each user who should have access to the calendar. It is no longer relevant what level of permissions you specify for each user.

Notes:

  • Regarding Step 4, it is not a problem to share the resource calendar in Google with all the users prior to the migration. However, keep in mind that the Destination will show the "creator" of the event as whatever user that calendar migrated with.
  • Regarding Step 8, if you fail to add the folder mapping, all the calendar items will be migrated from the Source resource calendar to the Destination user's primary calendar. If more than one Destination user already has permissions to that calendar, a separate instance of each event will be migrated to each of those users' primary calendars.