How to Fill the Users/Groups CSV File
Learn how to format and upload CSV files containing user and group information for your Cloudiway migration.
Overview
Cloudiway allows you to import users and groups via CSV files for bulk migration setup. This guide explains the required formats for different migration types.
Sample Templates
A sample CSV template is available during the import process in the Cloudiway platform. Use it as a starting point for your data.
File Constraints
File Size Limit
Browser uploads are limited to approximately 5,000 lines per file
Multiple Uploads
You can upload as many files as needed - previously uploaded data won't be overwritten
For Large Files
If your user list exceeds 5,000 lines, split it into multiple CSV files and upload them separately.
Mail Migration Format
For email migrations, use the following CSV structure:
| Field | Required | Description |
|---|---|---|
| FirstName | Yes | User's first name |
| LastName | Yes | User's last name |
| SourceEmail | Yes | Source mailbox email address |
| TargetEmail | Yes | Target mailbox email address |
| SourceRecipientType | Yes | Standard, Archive, SharedMailbox, or RoomsAndEquipment |
| TargetRecipientType | Yes | Standard, Archive, SharedMailbox, or RoomsAndEquipment |
| BatchName | Optional | Group users into migration batches |
# Example Mail Migration CSV
FirstName,LastName,SourceEmail,TargetEmail,SourceRecipientType,TargetRecipientType,BatchName John,Doe,john.doe@source.com,john.doe@target.com,Standard,Standard,Batch1 Jane,Smith,jane.smith@source.com,jane.smith@target.com,Standard,Standard,Batch1 Support,Team,support@source.com,support@target.com,SharedMailbox,SharedMailbox,Batch2
File Migration Format
For file migrations (OneDrive, SharePoint, Google Drive), use this extended format:
| Field | Required | Description |
|---|---|---|
| FirstName | Yes | User's first name |
| LastName | Yes | User's last name |
| SourceEmail | Yes | Source account email |
| TargetEmail | Yes | Target account email |
| SourceFolder | Optional | Specific source folder path |
| SourceRecipientType | Yes | None or Archive |
| TargetRecipientType | Yes | OneDrive, SharePoint, Teams, GoogleDrive, GoogleSharedDrive, or None |
| TargetLibrary | Optional | Target document library name |
| TargetFolder | Optional | Target folder path |
| TargetSiteUrl | Optional | SharePoint site URL (for SharePoint target) |
| BatchName | Optional | Migration batch identifier |
Site Migration Format
For SharePoint or Google Sites migrations:
| Field | Description |
|---|---|
| SourceName | Source site name |
| SourceId | Source site identifier |
| Location | For Google Sites: owner/fileId or fileId@domain |
| SourceRecipientType | Classic, GoogleSite, or ModernSite |
| TargetName | Target site name |
| TargetUrl | Target site URL |
| TargetRecipientType | Target site type |
| TemplateName | SharePoint site template |
| BatchName | Migration batch identifier |
Group Migration Format
Group migrations support various scenarios with different field requirements:
Teams-to-Teams
Migrate Microsoft Teams between tenants
Teams-to-Google Spaces
Migrate Teams content to Google Chat Spaces
Google TeamDrives-to-SharePoint
Migrate shared drives to SharePoint document libraries
Slack-to-Teams
Migrate Slack workspaces and channels to Teams
Scenario-Specific Fields
Each migration scenario has different required fields. Download the sample template from the platform for your specific migration type.
Best Practices
Don't fill fields that don't apply to your migration scenario
Save your CSV with UTF-8 encoding to support special characters
Ensure all email addresses are valid and correctly formatted
Group users by department, location, or priority for organized migrations