This article explains how to set up a migration batch for migrating resources from Google Workspace to Google Workspace. The setup shown here focuses on migrating calendar items, such as rooms and equipment, together with their bookings.
Before you start, complete the steps in the Migration Guide to set up your migration project and add your resources migration batch.
Two lists use two different values for the same resource, and mixing them up is the most common mistake. The Items to migrate list uses the destination resource ID in Import Name. The Address Replacements CSV uses email addresses, never resource IDs.
Work through the steps in order. Resources must exist at the destination before you create the address replacements and run the migration.
Prepare the Items to migrate list
1. Get items from source
Click Add items to migrate, then Get items from source. Migrate scans the source Google Workspace and adds every resource it finds to the list.
For each resource, Export Name is filled with the source resource email address. The same value is copied into Import Name as a default assumption. You will change that in the next step.
Further instructions on adding entities to your batch are in Adding Items to a migration batch.
2. Update the Items to migrate list
Use the fields below for each resource.
| Field | What to enter |
|---|---|
| Export Type | Resource |
| Export Name | The source resource email address |
| Import Type | Resource |
| Import Name |
Existing resource: the destination resource ID. New resource: the resource ID you want CloudM to create it with. |
| Given Name (Item name) | The resource name. Required if you are creating a new resource. For a resource that already exists, leave this blank. |
| Family Name (Item description) | The resource description. Optional. |
| Documents Path | Not required |
| Documents Destination Path | Not required |
In short:
- Existing destination resource: set Import Name to the destination resource ID and leave Given Name blank.
- New destination resource: set Import Name to the resource ID you want and Given Name to the resource name you want.
We recommend replacing the source email address in Import Name with the destination resource ID. You can keep the source address if you want a reference back to the source after the migration, but if CloudM creates the resource with it, the destination resource ends up with the source address as its ID, plus a separate email address of its own. That can make the configuration, address replacements and future management more confusing.
For each item, select the data types you want to migrate and make sure the Migrate checkbox is enabled for every resource you intend to include in the run.
3. Create the missing destination resources
Go to Progress, click Start, then select Check User State. If Create users/resources/groups/shared drives is enabled in Destination > User (see Google Workspace - Destination Settings), CloudM creates any destination resources that do not exist yet, using the Import Name and Given Name values from your list.
If that setting is disabled, Check User State only checks whether each resource already exists, which is a useful way to confirm your list before anything is created.
Every resource must exist at the destination, either already or created here, before you continue.
4. Get the resource IDs from the destination
CloudM Migrate does not report destination resource IDs, so collect them directly from the destination Google Workspace. In the Google Admin console, go to Directory > Buildings & Resources > Manage Resources and select the resource. The Resource ID is shown in the resource details, and the resource email address is available there too.
Use what you collect for two checks:
- Confirm that Import Name on your Items to migrate list matches the destination resource ID for every resource.
- Take the destination email addresses for the address replacements CSV in the next step.
Create the Address Replacements CSV
5. Create or update the Address Replacements CSV
The address replacements file is always required. It binds each calendar resource to its bookings at the destination, so rooms and equipment appear correctly on migrated appointments.
Map each source email address to its destination email address. Do not use resource IDs here. Include your resources, and also the users and groups that appear in your bookings.
# Resources (email address to email address, not resource IDs)
boardroom@oldco.com,boardroom@newco.comThe CSV format, with examples for users, groups, and domains, is covered in the Address Replacements article.
Configure the settings
General Settings
In the General Settings section, ensure all domain mappings are configured correctly to facilitate replacing the source domain with the destination domain during the migration.
You can also apply date range filters for various data types to migrate information within a specific timeframe. Specify the date ranges you wish to include.
Source Settings
For a standard resource-to-resource migration, keep most of the source settings at their default values. Detailed information about each setting is in the article linked below:
Google Workspace - Source Settings
Destination Settings
For a standard resource-to-resource migration, keep most of the destination settings at their default values.
The article below gives a detailed overview of all available destination settings for Google Workspace:
Google Workspace - Destination Settings
6. Import the Address Replacements CSV
In Advanced Settings, import the Address Replacements CSV you created in step 5. For a straightforward resource-to-resource migration, the other advanced settings can stay at their default values.
Additional settings are outlined in Advanced Settings.
Before you run the migration
Calendar resource auto-acceptance
When migrated events contain a resource or room calendar, the resource sends an acceptance or denial email to the meeting organizer if it is set to auto-accept meetings, which is the default. To avoid a large number of emails going to attendees, disable Auto-accept in the calendar settings of each resource before you migrate.
Google does not offer API access to the auto-acceptance setting, so this can only be done manually for each resource calendar.
Run the migration
7. Migrate
Check that the Migrate checkbox is enabled for every resource you want to include, then start the migration.
For a complete guide covering project planning, user communication, and pre- and post-migration checklists, see CloudM's Recommended Migration Strategy.