What is the Mapping Table Used For
Convert email addresses during migration for permissions and metadata.
Email Address Conversion
Purpose
The mapping table is a critical component that converts email addresses during migration. When migrating between different domains or tenants, source email addresses must be translated to their target equivalents.
Example Conversion
john.smith@oldcompany.com → john.smith@newcompany.com Applications
📧 Mail Migration
- → Mail headers (From, To, CC)
- → Contact entries
- → Calendar appointment attendees
📁 Drive/Sites/Groups/Teams
- → File and folder permissions
- → Metadata (CreatedBy field)
- → Metadata (ModifiedBy field)
Where Mapping Applies
Critical Importance
⚠️ Data Integrity Risk
If the mapping table is incorrect or incomplete, your migration data may get corrupted.
Email addresses without mapping entries won't be converted
Target system rejects non-existent source addresses
Delta passes only remigrate changed documents - incomplete mapping cannot be corrected later
Prepare Before Migration
CSV Import Structure
You can add entries manually or import in bulk using a CSV file with these fields:
| Field | Description | Example |
|---|---|---|
| FirstName | User's first name | John |
| LastName | User's last name | Smith |
| DisplayName | Full display name | John Smith |
| SourceEmail | Original email address | john@source.com |
| TargetEmail | New email address | john@target.com |
| EntryType | 0 = user, 1 = group | 0 |
Example CSV
FirstName,LastName,DisplayName,SourceEmail,TargetEmail,EntryType
John,Smith,John Smith,john@oldco.com,john@newco.com,0
Sales,Team,Sales Team,sales@oldco.com,sales@newco.com,1
Automatic Entries
Mapping entries are automatically added when you create migration users in the Cloudiway platform. You can also manually configure entries before migration begins.