How GALSync Fields Are Mapped Between Tenants
Understanding contact field mapping during GAL synchronization.
GALSync Field Mapping
Overview
GALSync synchronizes users and groups between G Suite and Office 365 by transforming contact data. However, some data may be lost because the target contact format cannot recognize all data from the source.
Data Loss Consideration
Office 365 Contact Mapping
When converting to Office 365 contacts, the following fields are supported:
User & Group Fields
- • Birthday
- • CompanyName
- • Department
- • DisplayName
- • GivenName
- • JobTitle
- • MobilePhone
- • OfficeLocation
- • Surname
Communication Fields
- • BusinessPhones
- • HomePhone
- • ImAddresses
- • EmailAddresses
- • ProxyAddresses
Address Data
BusinessAddress and HomeAddress are supported (only one per contact type).
Guest User Restriction
Microsoft restricts updates to businessPhones, mobilePhone, and otherMails for guest users in non-administrator roles.
Google Workspace Contact Mapping
When converting to Google Workspace contacts, the following field conversions are applied:
Name Fields
- • GivenName
- • FamilyName
- • FullName
- • NamePrefix
- • NameSuffix
Organization Fields
- • Department
- • JobDescription
- • Location
- • Title
Communication
- • Mail addresses (one set as primary work)
- • Phone numbers
- • IMs
Other Fields
- • PostalAddresses (street, city, region, postcode, country)
- • Languages
Critical Limitations
Email Address Requirement
A source item without mail addresses won't be synchronized.
This is a fundamental constraint—no customization can override this requirement for successful synchronization. Ensure all users and groups you want to sync have valid email addresses.
Fields That May Be Lost
Some data may be lost during synchronization because the target contact format cannot recognize data from the source. Custom fields and platform-specific attributes that don't have equivalents in the target system will not be synchronized.