When This Applies
This information is relevant when you need to:
Map Referral Source fields from Dazos CRM to KIPU EMR
Sync Referral Contact information to KIPU's contacts section
Understand workflow limitations for the Related Contacts table
Avoid data conflicts during KIPU integration setup
Current Integration Limitations
Workflow Automation Limitation
Dazos currently lacks a workflow to automatically add records to the "Related Contacts" table in the CRM. Automatic replication of Referral Contacts as Related Contacts is not available.
Field Mapping Conflict
Mapping both Referral Sources and Referral Contacts to the same "Contacts" field in KIPU creates a data conflict. When too much data hits the same destination field, it results in:
Blank fields in KIPU
Data loss during synchronization
Inconsistent or incomplete contact information
Recommended Solution: Custom Field Creation
The best approach is to have KIPU create a dedicated custom field for this data mapping:
Custom Field Setup — KIPU creates a dedicated custom field in their system layout
Direct API Mapping — Dazos maps the Referral Source and Contact data directly to this custom field through the API
Clean Data Sync — ensures data syncs without conflicts or data loss
Tips & Notes
⚠️ Important: Contact your KIPU administrator to set up the custom field before configuring the mapping in Dazos.
💡 Best Practice: Always use dedicated custom fields for specific data types rather than mapping multiple data sources to the same destination field.
✅ Implementation Tip: Coordinate between your Dazos team and KIPU support to ensure the custom field is correctly configured for API access before beginning the mapping setup.
Related Resources
KIPU EMR Integration with Dazos CRM (Bidirectional)
How to set up Field Mapping from Leads to other compatible modules
Understanding Webhook Limitations and Zapier Integration for Stage Change Automation