Custom Mapping: Creating a Custom List Map file

Created: 2012-04-20 08:09:59
Modified: 2022-09-10 09:06:48
Tags: Custom Mapping UnitySync

A custom list map file allows you to change any aspect of how the sync creates new Group objects on the Destination directory for this connection. Default mappings for list map files differ according to directory type. The Source and Destination directory type of the connection must be appropriate for any given list map file. For example, a Notes-to-AD list map file may not be used in an AD-to-AD connection.

The most common use for a custom list map is to change how attributes are mapped between systems. It is also possible to customize the sync container, so that your synced group objects are created in a different container than synced contact or user objects.

IMPORTANT NOTE: A custom list map is typically not needed if you are syncing Groups as Contacts (default group sync functionality). When you sync Groups as Contacts, the object map will be used by default. If you are syncing Groups as Contacts and feel you need to alter the map file, please contact our technical support team to discuss your needs.

Creating a Custom List Map File

  1. In the UnitySync UI, select your connection, then click the Custom tab.
  2. Click the List Map button, then type in a name for your new custom list map and click Save.
  3. The map file will open with default values. Make any desired changes to the map file.
  4. Click Save to save your map file changes.
  5. Click Save again at the bottom of the Custom tab to save your selection of the custom list map file for your connection.

A Note about using a custom DN mapping to change your sync container for Groups:

The ~struct~ is a required part of the syntax. This value will be the structure specified by PlacementDN and/or StructName.

You may not remove ~struct~ and try to hard code the entire DN mapping, such as:


This syntax will result in inaccurate structure.

You may, however, customize the DN to add structure where ~struct~ is a common root of the destination sync container for both Contacts and Groups.

For example:

Placement DN is: dc=domain,dc=test
Custom Contact (Object) DN mapping: dn=cn=~mail#64~,ou=Contacts,~struct~
Custom Group (List) DN mapping is: dn=cn=~component0~,ou=Groups,~struct~

With these mappings:

Your Groups will be synced to: ou=Groups,dc=domain,dc=test
Your Contacts will be synced to: ou=Contacts,dc=domain,dc=test

For additional guidance on custom mapping syntax, refer to the UnitySync Administrator’s Guide. Please contact for assistance, if needed.

Share this article:

  1. Directify - Self Service

  2. Mimic - Replication

  3. UnitySync - Sync
  1. emPass - Sync
  1. Profiler
  2. SimpleSync