Home > Active Directory Migration > Support Lists for Contact Attributes

Export to PDF

Support Lists for Contact Attributes

Refer to the table below to view the supported and unsupported attributes for Active Directory contacts.

NOTE

The attributes that are not listed in the table below are not supported. Refer to Microsoft document for details.

If the value of the Update Privilege entry is This value is set by the system, it means that the attribute is updated by system and is not supported in Active Directory migrations.

Value for the Update Privilege entry.

If the value of System-Only is true, it means that the attribute is not editable and is not supported in Active Directory migrations.

Value for the Update Privilege entry.

√ – Supported: Fly can update the attribute value in the migration.

System updated: The attribute value is updated by the Active Directory system.

Attribute NameDescriptionSupportedComment
descriptionDescriptions
displayNameDisplay Name
dSCorePropagationDataDS-Core-Propagation-Data
cCountry (abbreviations)
cnCommon Name
coCountry
companyCompany
countryCodeCountry Code
departmentDepartment
facsimileTelephoneNumberFacsimile-Telephone-Number
givenNameFirst Name
infoInfo
instanceTypeInstance-Type
homePhoneHome Phone
lLocation
mailEmail
managerManager
memberOfGroup Membership
mobileMobile
msExchALObjectVersionms-Exch-AL-Object-VersionOnly supported when creating a new object in the destination.
msExchCanaryData0ms-Exch-Canary-Data-0Only supported when creating a new object in the destination.
msExchCanaryData1ms-Exch-Canary-Data-1Only supported when creating a new object in the destination.
msExchCanaryData2ms-Exch-Canary-Data-2Only supported when creating a new object in the destination.
msExchDirsyncIDms-Exch-Dirsync-IDOnly supported when creating a new object in the destination.
msExchEdgeSyncCookiesms-Exch-Edge-Sync-CookiesOnly supported when creating a new object in the destination.
msExchEdgeSyncSourceGuidms-Exch-Edge-Sync-Source-GuidOnly supported when creating a new object in the destination.
msExchExternalDirectoryObjectIdms-Exch-External-Directory-Object-IDOnly supported when creating a new object in the destination.
msExchInconsistentStatems-Exch-Inconsistent-StateOnly supported when creating a new object in the destination.
msExchIsMSODirsyncedms-Exch-Is-MSO-DirsyncedOnly supported when creating a new object in the destination.
msExchLastExchangeChangedTimems-Exch-Last-Exchange-Changed-TimeOnly supported when creating a new object in the destination.
msExchOnPremiseObjectGuidms-Exch-On-Premise-Object-GuidOnly supported when creating a new object in the destination.
msExchSetupStatusms-Exch-Setup-StatusOnly supported when creating a new object in the destination.
msExchVersionms-Exch-VersionOnly supported when creating a new object in the destination.
nameName
notesAdditional-Information
objectCategoryObject-Category
objectClassObject Class
otherFacsimileTelephoneNumberPhone-Fax-Other
otherHomePhonePhone-Home-Other
otherIpPhonePhone-Ip-Other
otherMobilePhone-Mobile-Other
otherPagerPhone-Pager-Other
otherTelephonePhone-Office-Other
pagerPhone-Pager-Primary
postOfficeBoxPost-Office-Box
urlWWW-Page-Other
physicalDeliveryOfficeNameAddress
postalCodePostal Code / ZIP
snLastname
stState
streetStreet
streetAddressAddress
telephoneNumberPhone
titleJob Title
wWWHomePageWWWHomePage
initialsinitials
distinguishedNameObj-Dist-NameSystem updated
createTimeStampCreate-Time-StampSystem updated
modifyTimeStampModify-Time-StampSystem updated
objectGUIDObject-GuidSystem updated
uSNChangedUSN-ChangedSystem updated
uSNCreatedUSN-CreatedSystem updated
whenChangedWhen-ChangedSystem updated
whenCreatedWhen-CreatedSystem updated

Support Lists for Other Contact Properties

Refer to the table below to view the other supported and unsupported properties for Active Directory contacts.

Property NameSupportedComment
Contact in custom OU 
Contact in Default ContainerPartially SupportedManually created contacts in the default Builtin and Users containers can be migrated.
Deleted Contacts×If contacts have been scanned to Fly and then you delete the contacts from the source OU, Fly will not sync the deletion to the database.
ManagerTo migrate the manager of a contact, you can run a Migrate object managers job.Note that make sure the manager has been scanned to Fly and exists in the destination.