If you have a CSV file of all your users, you can upload the file to Cloudiway. A sample CSV file is available for download during the Import.
Note that many browsers limit CSV file uploads to 5000 lines, so files larger than that should be split up and uploaded separately. Data already uploaded will not be overwritten, so you can upload as many files as required.
You might also want to upload multiple CSV files depending on the license type. For example, if some users don’t have a OneDrive but do have files shared with them, you could upload them all within a single CSV file and not run a migration on these users, then all the other OneDrive users will be assigned the relevant license to migrate their data.
The BatchName field can be left blank. If required, you can use this field to name different batches so they can be run in a certain order.
CSV Data for Mail Migration
FirstName;LastName;SourceEmail;TargetEmail;
SourceRecipientType;TargetRecipientType;BatchName;
| Field | Description |
|---|---|
| FirstName | First Name of the user. |
| LastName | Last Name of the user. |
| SourceEmail | Email Address of the source. |
| TargetEmail | Email Address of the target. |
| SourceRecipientType | The Type of the Mailbox: enter Standard, Archive, SharedMailbox, or RoomsAndEquipment. |
| TargetRecipientType | The Type of the Mailbox: enter Standard, Archive, SharedMailbox, or RoomsAndEquipment. |
| BatchName | The name of the batch you want to assign the user to. The BatchName field can be left blank. If required, you can use this field to name different batches so they can be run in a certain order. |
CSV Data for File Migration
The file must have the following fields in the header row:
FirstName;LastName;SourceEmail;TargetEmail;SourceFolder;
SourceRecipientType;TargetRecipientType;TargetChannelName;
TargetLibrary;TargetFolder;BatchName;TargetSiteName;TargetSiteUrl;
| Field | Description |
|---|---|
| FirstName | First Name of the user. |
| LastName | Last Name of the user. |
| SourceEmail | Email Address of the source (Google Drive, OneDrive, Blobstorage, Box, or Dropbox). |
| TargetEmail | Email Address of the target (Google Drive, Office 365 – OneDrive, SharePoint Sites, Blob storage…). |
| SourceFolder | Name of the Folder in the source, the Folder must be in the root (optional: applies only if you’re migrating from a specific Folder). |
| SourceRecipientType | This must specify if we are migrating from Archive or not. So, it must be "None" or "Archive". |
| TargetRecipientType | This must specify the type of the target you are migrating to. For Office 365, it must be “OneDrive”, “SharePoint”, or “Teams”. Otherwise, it must be “None”. |
| TargetChannelName | Not needed in most scenarios, it depends on whether you want to migrate into a Channel (Teams) or not. |
| TargetLibrary | Not needed in most scenarios, it depends on whether you want to migrate into a Library or not. |
| TargetFolder | Name of the Folder in the target to migrate to, the Folder must be in the root (optional: applies only if you’re migrating to a specific Folder). |
| BatchName | The name of the batch you want to assign the user to. The BatchName field can be left blank. If required, you can use this field to name different batches so they can be run in a certain order. |
| TargetSiteName | Name of the Site in the target to migrate to (when SharePoint is the target) |
| TargetSiteUrl | Url of the Site in the target to migrate to (when SharePoint is the target) |
Not needed fields must be left blank.
Example: Bob;Marley;B.Marley@source.com;B.Marley@target.com;MySourceFolder;Archive;
OneDrive;;;MyTargetFolder;Batch1;
CSV Data for Site Migration
The file must have the following fields in the header row:
SourceName;SourceId;Location;SourceRecipientType;TargetName;TargetChannelName;
TargetEmailAddress;TargetUrl;TargetRecipientType;ParentObjectId;TemplateName;Description;BatchName;
| Field | Description |
|---|---|
| SourceName | The site name. |
| SourceId | The relative URL of the site. |
| Location (only for new google sites) | Drive the site is located in (Owner) & site ID & Domain (if published). |
| SourceRecipientType | Enter "Classic", "GoogleSite" or "ModernSite". |
| TargetName | The target site name. |
| TargetChannelName | Not used, leave blank. |
| TargetEmailAddress | Leave blank. |
| TargetUrl | The relative URL at the target SharePoint site. |
| TargetRecipientType | ModernSite for site. |
| ParentObjectId | Enter 0. |
| TemplateName | Leave blank by default or enter the name of the SharePoint template site to use (check out the complete list here). |
| Description | Short description of the site (without special characters). |
Not needed fields must be left blank.
Example: mysourcesitename;/sites/mysourcesiteurl;;ModernSite;destinationsitename;;;
/sites/destinationsiteurl;ModernSite;0;STS#3;;
Important Note:
CSV Data for group Migration
The headers have different formats based on the scenario
Scenario: Microsoft Teams or Unified Group to Microsoft Teams or Unified Group.
SourceName; SourceEmailAddress; SourceUrl; TargetName; TargetEmailAddress; BatchName;
Scenario: Microsoft Teams or Unified Group to Google Spaces.
SourceName; SourceEmailAddress; SourceUrl; TargetName; AllowExternalMember; BatchName;
Scenario: Google TeamDrives to Google TeamDrives.
SourceName; SourceId; TargetName; TargetId; BatchName;
Scenario: Google TeamDrives to SharePoint.
SourceName;SourceId;TargetName;TargetUrl;TargetLibraryName;TargetFolderName;BatchName;
Scenario: Google TeamDrives to Microsoft Teams.
SourceName; SourceId; TargetName; TargetEmailAddress; TargetChannelName; BatchName;
Scenario: Google TeamDrives to Microsoft Blob Storage.
SourceName; SourceId; TargetName; BatchName;
Scenario: Dropbox Team Folders to SharePoint.
SourceName; SourcePath; SourceId; TargetName; TargetUrl; TargetLibraryName; TargetFolderName; BatchName;
Scenario: Dropbox Team Folders to Microsoft Teams.
SourceName; SourcePath; SourceId; TargetName; TargetEmailAddress; TargetChannelName; TargetVisibility; BatchName;
Scenario: Dropbox Team Folders to Google TeamDrives.
SourceName; SourcePath; SourceId; TargetName;
Scenario: Dropbox Team Folders to Azure Blob Storage
SourceName; SourcePath; SourceId; TargetName;
Scenario: Slack To Microsoft Teams
SourceName; SourceId; TargetName; TargetEmailAddress; TargetChannelName; TargetVisibility; BatchName;
Scenario: Slack To Google Spaces
SourceName; SourceId; TargetName; AllowExternalMember; BatchName;
Scenario: Google Spaces to Microsoft Teams
SourceName; SourceEmailAddress; SourceId; TargetName; TargetEmailAddress; TargetChannelName; TargetVisibility; BatchName;
| Field | Description |
|---|---|
| SourceName | The source site group e-mail (Google), or SharePoint Security group loginName. |
| SourceId | Take note of the ID of the shared drive:  For Google groups, you need to enter the URL of the group. |
| SourceEmailAddress | Enter your primary email address if you migrate from Teams or Google groups, otherwise, leave blank. |
| SourceRecipientType | Enter "GoogleGroup" if you migrate from Google groups, "MicrosoftTeams" if you migrate from Teams. |
| TargetName | The target group name. |
| TargetChannelName | You can specify only if you migrate to Teams, otherwise, leave blank. |
| TargetEmailAddress | The target email address of the target group or team you want to migrate to. |
| TargetUrl | The relative URL at the target Teams. Leave blank for group. |
| TargetRecipientType | "MicrosoftTeam" if you migrate to Teams, "SharedMailbox" if you migrate to a SharedMailbox and "UnifiedGroup" if you migrate to an O365 group. |
| TemplateName | Leave blank by default. |
| Description | Short description of the group or team (without special characters). |
| TargetVisibility | Public, Private or Shared for Microsoft Teams |
Not needed fields must be left blank.
Product: