GALSync Field Mapping Between Tenants
Complete reference for how user and group attributes are synchronized between directories during coexistence.
Overview
GALSync (Global Address List Synchronization) transforms users and groups from source systems into contact objects in destination systems. This enables directory coexistence where users can see and communicate with each other across different platforms.
Email Address Required
A source item without email addresses will not be synchronized. All objects must have at least one valid email address to be included in GALSync.
How GALSync Works
During synchronization, GALSync reads directory objects from the source tenant and creates corresponding contact objects in the destination. Some data transformation occurs because not all fields are compatible between platforms.
Extract users, groups, and contacts
Map fields to contact format
Write to destination directory
No Customization Available
Field mapping is standardized. No changes, customization, or specific mapping modifications are available for individual projects.
Office 365 Contact Field Mapping
When synchronizing to Office 365 contacts, the following fields are supported based on the source object type:
| Field | User | Group | Contact |
|---|---|---|---|
| Display Name | ✓ | ✓ | ✓ |
| Email Addresses | ✓ | ✓ | ✓ |
| Birthday | ✓ | - | - |
| Business Address | ✓ | ✓ | ✓* |
| Home Address | ✓ | ✓ | ✓* |
| Business Phones | ✓ | ✓ | - |
| Mobile Phone | ✓ | ✓ | - |
| Company Name | ✓ | ✓ | - |
| Department | ✓ | ✓ | - |
* Contacts support only one address (business or home)
Guest User Restriction
Updating businessPhones, mobilePhone, or otherMails on guest users is restricted to non-administrator roles or specific Azure AD role assignments.
Google Contact Field Mapping
When synchronizing to Google Contacts, the following fields are supported:
👤 Name Fields
- ✓ Given Name (First Name)
- ✓ Family Name (Last Name)
- ✓ Full Name
- ✓ Name Prefix (Mr., Ms., etc.)
- ✓ Name Suffix (Jr., Sr., etc.)
📧 Contact Fields
- ✓ Email (with primary/work labels)
- ✓ Phone Numbers (multiple)
- ✓ Instant Messenger
- ✓ Languages
📍 Address Fields
- ✓ Street Address
- ✓ City
- ✓ Region/State
- ✓ Postal Code
- ✓ Country
🏢 Organization Fields
- ✓ Company Name
- ✓ Department
- ✓ Job Title
- ✓ Office Location
Multiple Addresses Supported
Google Contacts supports multiple addresses with detailed formatting options that may not be available in other systems. Multiple phone numbers and email addresses are also fully supported.
Limitations
Data Loss During Conversion
Some data loss occurs because certain fields cannot be recognized during conversion between different platforms. Fields that don't exist in the destination system are not synchronized.
Email Address Required
Objects without valid email addresses are skipped during synchronization. Ensure all users and groups have at least one email address.
No Custom Mapping
The field mapping is standardized and cannot be customized for individual projects or tenants.
Single Address for O365 Contacts
When syncing to Office 365, contacts can only have one business address and one home address.