How can I make synced objects members of an existing destination Group?

Groups as Groups - new article added

You may have the desire to have SimpleSync created contacts automatically assigned to existing destination Groups. Group membership is controlled by the existing Group object itself (which SimpleSync can not modify). Therefor, your SimpleSync connection can not be configured to add synced contacts to existing destination groups.

Recommended solution for Ex200x :

On an Exchange 200x destination, the recommended method to accomplish this goal is to create a Query based Distribution Group . To add ALL synced contacts to a Query based Distribution Group, use a query to include all objects in the sync container. Alternatively, you may use an attribute based query. If necessary, you may use custom mapping to assign appropriate attribute values to be picked up by the Query based Distribution Group.

Recommendations for other directory types:

For all other email directory types, there is a solution which may give you the same result, which is to make contacts synced from source objects members of existing destination groups…

The solution for configurations (A) (B) and © may be applied in both v3 and v4 of SimpleSync. The solution for configuration (D) utilizes Group as Group sync which is only available as of Simplesync v4.x.

All solutions utilizes Grouping of objects on the source directory. In a nut shell, you will create new groups on your source directory, add source members to these groups, then sync the group to the destination (either as a Contact or as a Group). After the first sync creates new contact/group on your destination, manually add the new contact/group to your existing destination groups as desired .

NOTE: Due to the use of Query Filters in this solution, it is recommended you create a test connection to test your results before changing your production sync. Incorrect use of Query filters can result in deletion of destination objects.

Review of possible configurations and how to apply this solution. (A) New connection. (B) Existing connection which is not currently configured to pull source Groups. © Existing Connection which is already configured to pull source Groups, and uses sync As Email Address. (D) Existing connection which is already configured to pull Source Groups, and uses sync Groups as Groups.

Solution for environments (A) (B) ©

On your SOURCE directory, create one or more groups (in a container synced by your existing connection). 

Add your source members to these groups as desired.

The following configurations are required:
Destination tab: Use default List Processing of as email address
Source tab: Select Source Object Groups to be included in your sync
Source tab: Add a Group LDAP Query Filter to pull only your new source groups (optional): 
... One Group: (cn=Group Name)
... Two Groups: (|(cn=Group Name A)(cn=Group Name B))
... Three Groups: (|(cn=Group Name A)(cn=Group Name B)(cn=Group Name C))
... etc

(NOTE: If you wish to pull ALL source groups, instead of just those new groups created to facilitate this solution, then you may skip the use of the LDAP Query Filter.) 

Run your sync. Your source groups will be synced to the destination as Contacts.

On the destination, identify the newly synced group Contact(s) and make them members of your existing Destination Groups as appropriate.

Solution for environments (D)

On your SOURCE directory, create one or more groups (in a container synced by your existing connection). 

Add your source members to these groups as desired.
Run your sync. Your source Groups will be synced to the destination as Groups.
On the destination, identify the newly synced Groups and make them members of your existing Destination Groups as appropriate.

More Information: Review the basic Group as Group sync Knowledge Base article for general information on Group as Group sync.