Resources are items from the source system such as resource calendars, shared with all users.
First you will need to configure CloudM Migrate for your destination system as shown in the setup guides.
When clicking ‘Get Users’ Resources will also be obtained from the source system and be presented in the list, displayed with a different icon. These objects can then be migrated along with the users.
Notes for Migrating Resources to G Suite
When migrating resources, only appointments are migrated to the resource within G Suite. When creating a resource only ‘Resource Name’ needs to be provided, ‘Resource Description’ is optional, and ‘Password’ is not relevant.
When a resource is migrated using the CloudM Migrate, the ‘Import Name’ becomes the resource ID within G Suite. If resources have been pre-created in G Suite then the resource ID should be extracted from G Suite and specified for the ‘Import Name’. Resource IDs can be found in the G Suite control panel by clicking on a resource name. The ID required is specified in the control panel as ‘Resource identifier’.
- Apps > G Suite
- Click on Calendar
- Then go to 'Resources', and select the Calendar that you need for the Resource ID
- On the left side panel, you will see the actual 'Resource ID' of the Calendar
When resources have been created, they will be allocated an email address, also available from the control panel. This email address allows the resource’s calendar to be added to other user’s calendar lists. Resources can be manipulated in the user list, including importing and exporting in the same way users can.
It is best practice for resource attributes tom match in source and destination. This includes fields such as building floor and room capacity. Google constructs an auto-generated resource name using these attributes so when migrating, if the values don't match, the destination's auto-generated resource name will be added into migrated events' resource field using the new values.
As well as this, CloudM Migrate will populate the location field on migrated events with the original source auto-generated resource name as a reference to the original resource values. This may or may not be desirable depending on your use case but can be worked around if needed by matching resource attributes.