How Gal sync fields are mapped between tenants

Transformed data, tenant to tenant leads to data loss.

On the same tenant type, some data are lost because no field of contact type could welcome the data from the source.
The Gal sync product takes users and groups from the source and transform them to source contacts. Then, if needed, transforms them to target contacts.

Here is how the data is kept from one object to another :

Convert to Office Contact

FieldsOffice userOffice groupGoogle contact
Birthdayx
BusinessAddress
(City, Country, PostalCode, State, streetAddress, AdditionalData)
xx
Only one as Office contact can only get one
BusinessPhonesxx
For work phones, work fax, work mobile, work pager
CompanyName
xx
Departmentxx
DisplayNamexxx
GivenNamexx
HomeAddress
(City, Country, PostalCode, State, streetAddress, AdditionalData)
xx
Only one as Office contact can only get one
HomePhoneUser Don't have home phones propertyx
(Home & home fax phones)
ImAddressesxx
JobTitlexx
MobilePhonexx
OfficeLocationxx
Surnamex
EmailAddresses
(Name, Address, AdditionalData)
xxx
Only mail address
ProxyAddressesxx

Specific case : Guest users

There is restrictions on Microsoft side on updating guest users depending it’s role:

Updating a user’s businessPhonesmobilePhone, or otherMails property is only allowed on users who are non-administrators or assigned one of the following roles: Directory Readers, Guest Inviter, Message Center Reader, and Reports Reader.

So we don’t alter those fields in this specific case.

Convert to Google Contact

FieldsGoogle userGoogle groupOffice contact
Etagxx
GivenNamexxx
GivenNamePhonetics
AdditionalName
AdditionalNamePhonetics
FamilyNamex
FamilyNamePhonetics
NamePrefix
NameSuffix
FullNamexxx
Mail
(Address, Label, Primary?, Rel)
xx
(1 address set as primary + work)
x
PhonesNumbers
(Primary Rel, Phone number)
x
PostalAddresses : Relxx
PostalAddresses : Primaryxx
PostalAddresses : Streetxx
PostalAddresses : Cityxx
PostalAddresses : Neighborhood
PostalAddresses : Regionx
PostalAddresses : Subregion
PostalAddresses : Postcodexx
PostalAddresses : Poboxx
PostalAddresses : Agent
PostalAddresses : Countryxx
PostalAddresses : FormattedAddressxx
Languages
(Label, code)
Organizations : Relxx
Organizations : Labelxx
Organizations : Namexx
Organizations : Titlexx
Organizations : Symbolx
Organizations : Departmentxx
Organizations : JobDescriptionxx
Organizations : Locationxx
Organizations : Primaryxx
IMs (Rel, Primary, Protocol)x

Warnings : A source item without mail addresses won’t be synchronized. No changes, customization or specific mapping could be done for your project.

Meet Cloudiway - A powerful and automated migration and coexistence platform. We support G Suite, Office 365, Zimbra, Lotus and lots more...
Register Now