Overview
When configuring field mapping between Dazos CRM and iCampaign, User/Group List and Lookup field types cannot be mapped or synced. If you attempt to map these field types, the values will not transfer — the mapping fails to carry any data over to iCampaign.
This is a current platform limitation. A workaround exists for standard user fields, but it is not suitable for all use cases (see details below).
Key Concepts
Affected field types: User/Group List fields and Lookup fields in the CRM cannot be mapped to iCampaign. No data will appear in iCampaign for these field types, even if the mapping appears to be configured correctly.
Workaround availability: A multi-step workaround exists for direct user fields (e.g., Assigned To or similar user-based fields), but it requires creating custom fields and a workflow.
Referral contact limitation: The workaround is not practical for referral contacts and their associated referral sources. There is currently no viable workaround for those use cases.
How It Works
Because User/Group List and Lookup field types store references (such as user IDs or linked record IDs) rather than plain text values, iCampaign is unable to interpret and receive this data through the standard field mapping process. The sync completes without error, but no value is written to the iCampaign subscriber field.
For user fields specifically, you can work around this limitation using the following approach:
Create a custom text field in the CRM to serve as an intermediary for the user data you want to sync.
Set up a CRM workflow that populates this custom text field with the user's ID whenever the record is created or updated.
Create a second custom text field with a Case When expression that translates the user ID into the user's display name (the human-readable name you want to appear in iCampaign).
Map this second custom text field (containing the display name) to the corresponding iCampaign field in your CRM iCampaign Mapping settings.
This text-based field can then be synced to iCampaign successfully, since it stores a plain text value rather than a User/Group List or Lookup reference.
Important Notes
⚠️ Referral contacts and referral sources: The workaround described above is not a practical solution for referral contacts and the referral sources they are associated with. If your use case involves syncing user or lookup data related to referral contacts, there is currently no available workaround.
Feature request status: Native support for mapping User/Group List and Lookup field types from CRM to iCampaign has been submitted as a feature request to the Dazos product team. This does not guarantee the feature will be built. Development roadmap priorities are set quarters in advance and are based on the volume and frequency of customer requests. If this becomes a priority, Dazos will reach out with updates.
If this limitation significantly impacts your workflow, contact Dazos Support to add your voice to the feature request and provide details about your use case.