Skip to main content
  1. CloudM
  2. Migrate 4
  3. ...
  4. Navigating Migrate
  5. Projects
  6. Migration Batches
  7. Migration Items

Bulk Add/Import Items

Updated

You can efficiently add multiple entities to your 'Items to migrate' list by importing a Comma Separated Values (CSV) file. This method is ideal for adding users, groups, or other items in bulk.

 

To access this feature:

  1. Navigate to 'Add items to migrate'.

  2. Select 'Bulk add/import items'.

 

 

Once there, you'll see two options:

  • Upload button: Use this to directly upload a prepared CSV file.

  • Download sample CSV: This provides a template with all the correct header fields, ensuring your CSV is correctly formatted for import.

 

 

Understanding the CSV Template

The CSV template contains a total of 25 header values. Each header corresponds to specific information about the entities you're migrating. The following sections detail each header, indicating whether it's Required, Optional, or Not Required.

 

CSV Template Example:

Migrate,ExportObjectType,ImportObjectType,ExportName,ImportName,GivenName,FamilyName,Password,ArchivePath,DocumentsPath,MigrateMail,MigrateContacts,MigrateCalendar,MigrateDrive,MigrateSites,MigrateTasks,ExportObjectRef,ImportObjectRef

 

 

Importing a Subset of Information

You can import a CSV file containing only a subset of the entity information. The required fields vary depending on the batch type (e.g., user, group).

 

See: Adding a Migration Batch

 

For most batch types, the following values are required:

  • Migrate

  • ExportObjectType

  • ImportObjectType

  • ExportName

  • ImportName

All other values in such cases are considered optional.

 

 

Value Descriptions

Note: The applicability and specific requirements for these values can depend on your source-to-destination platform combination and the entity batch type. For detailed specifics, please refer to our comprehensive Migration Guide.

  • Migrate:

    • Type: Boolean (True or False)

    • Required: Yes

    • Description: Determines whether the associated user or item will be processed during the migration.

  • Priority:

    • Type: Boolean (True or False)

    • Required: Yes

    • Description: This option is also available in the web user interface (UI). If set to True, this user will be processed before other users in the migration queue.

  • Id:

    • Type: String

    • Optional: Yes

    • Description: This value is automatically generated by the tool and can be left blank in your CSV.

  • ParentNodeId:

    • Type: String

    • Optional: Yes

    • Description: This value is also automatically generated by the tool and can be left blank.

  • ExportObjectType:

    • Type: String

    • Required: Yes

    • Description: Specifies the type of object being exported from the source platform.

    • Accepted Values: User, Resource, PublicFolder, MicrosoftTeam, UnifiedGroup, TeamSite (for SharePoint Online sites), TeamDrive, Site (for Google Sites), or GoogleGroup.

  • ImportObjectType:

    • Type: String

    • Required: Yes

    • Description: Specifies the type of object to be created or mapped to on the destination platform.

    • Accepted Values: User, Resource, PublicFolder, MicrosoftTeam, UnifiedGroup, TeamSite (for SharePoint Online sites), TeamDrive, Site (for Google Sites), or GoogleGroup.

  • ExportName:

    • Type: String

    • Required: Yes

    • Description: The unique identifier for the user or item on the source platform. This value varies depending on the source system:

      • GroupWise: The user's login name.

      • Exchange (2007/2010/2013/2016/Microsoft 365): The user's primary SMTP email address, or the part before the '@' symbol. If using only the part before the '@', ensure the export domain matches the domain of the users being migrated.

      • Lotus Notes/Domino: The user’s abbreviated Notes name.

      • Google Workspace: The user’s email address, or the part before the '@' symbol. If using only the part before the '@', ensure the export domain matches the domain of the users being migrated.

      • Scalix: The user’s primary SMTP address.

      • Zimbra: The user’s primary SMTP address.

      • IMAP: The user’s IMAP login name.

      • Box: The user's logon email address.

      • Dropbox: The user's logon email address.

  • ImportName:

    • Type: String

    • Required: Yes

    • Description: The desired name for the user or item on the destination platform. You can specify a full email address or just the part before the '@' symbol; the import domain will be appended automatically.

  • GivenName:

    • Type: String

    • Optional: Yes (Required when provisioning new users)

    • Description: The user's given name (first name) or the item name for resources/groups.

  • FamilyName:

    • Type: String

    • Optional: Yes (Required when provisioning new users)

    • Description: The user's family name (last name) or the item description for resources/groups.

  • Password / Resource Type:

    • Type: String

    • Optional: Yes (Required when provisioning new users)

    • Description: The password for the user being provisioned. For resources, this field might specify the resource type.

  • ArchivePath:

    • Type: String

    • Optional: Yes (Required when migrating archives)

    • Description: The file or folder path (or paths) to the user's archive files on the source system.

  • DocumentsPath:

    • Type: String

    • Optional: Yes (Required when migrating documents from a file system)

    • Description: The folder path (or paths) to the user's documents within the file system on the source.

  • DocumentsDestinationPath:

    • Type: String

    • Optional: Yes (Required when migrating documents from a file system)

    • Description: Specifies a particular subfolder within the Shared Drive where documents will be migrated.

  • MigrateMail:

    • Type: Boolean (True or False)

    • Required: Yes

    • Description: Controls whether mail data for this user will be migrated.

  • MigrateContacts:

    • Type: Boolean (True or False)

    • Required: Yes

    • Description: Controls whether contact data for this user will be migrated.

  • MigrateCalendar:

    • Type: Boolean (True or False)

    • Required: Yes

    • Description: Controls whether calendar data for this user will be migrated.

  • MigrateDrive:

    • Type: Boolean (True or False)

    • Required: Yes

    • Description: Controls whether document/drive data for this user will be migrated.

  • MigrateSites:

    • Type: Boolean (True or False)

    • Not Required: This field is typically not required for site migrations.

    • Description: (Further clarification needed on specific use cases if it's "Not Required" but still present).

  • MigrateTasks:

    • Type: Boolean (True or False)

    • Required: Yes

    • Description: Controls whether task data for this user will be migrated.

  • MigrateChannels:

    • Type: Boolean (True or False)

    • Required: Yes

    • Description: Controls whether Microsoft Teams Channels or user private chats will be migrated.

  • MigrateGoogleChat:

    • Type: Boolean (True or False)

    • Required: Yes

    • Description: Controls whether Google Chat or Spaces will be migrated.

  • ExportObjectRef:

    • Type: String

    • Optional: Yes

    • Description: This value is usually set automatically by the system and can often be left blank.

  • ImportObjectRef:

    • Type: String

    • Optional: Yes (Required only for public folders)

    • Description: This value is usually set automatically by the system. It is only required when migrating public folders.

  • MigrateNotes:

    • Type: Boolean (True or False)

    • Optional: Yes

    • Description: A True or False setting specifically for Notes on Microsoft 365. This can be ignored if you are not using or do not have any Notes to migrate.

Was this article helpful?
0 out of 0 found this helpful