Migrate from Denticon to Mailchimp

Denticon Patient records map directly to Mailchimp contacts. We extract email address, first name, last name, phone number, and full address fields from the Denticon Patients API. Each patient becomes one Mailchimp contact in the target audience. Duplicates are resolved by email address during Mailchimp bulk import.

Denticon custom fields on patient records migrate as Mailchimp merge fields. Mailchimp Standard caps merge fields at 30; Premium allows 80. If Denticon has more custom fields than the target plan supports, we work with your team to prioritize the most operationally relevant fields before migration. Merge field names are truncated to Mailchimp's 30-character maximum.

Denticon office identifiers and practice names do not have a native equivalent in Mailchimp's contact model. We convert each office location into a Mailchimp tag (e.g., 'Location: Downtown Office', 'Location: Suburban Clinic'). Tags enable per-location segmentation for campaigns without consuming merge field budget. Multiple tags per contact are supported.

The primary provider assigned to each Denticon patient record becomes a Mailchimp tag on the contact (e.g., 'Provider: Dr. Smith'). This allows segmentation by dentist for practice communication or referral follow-up campaigns. Provider names are extracted from Denticon's provider setup via the Practices API.

Denticon tracks referral sources (external providers, internal patient referrals, marketing sources). These values map to Mailchimp tags for segmentation (e.g., 'Referral: Dr. Johnson', 'Referral: Patient Word-of-Mouth'). Referral source data is extracted from the patient record's referral field, not from separate referral object APIs.

Insurance carrier names from Denticon patient records become Mailchimp tags (e.g., 'Insurance: Delta Dental', 'Insurance: Cigna PPO'). This supports segmented outreach for insurance-related communications without creating merge fields that consume the limited field budget. Self-pay patients receive a 'Self-Pay' tag.

Denticon assigns a unique patient account number to each record. Mailchimp has no native account number field, so we create a custom merge field (e.g., DENTICON_ID) to preserve the source system reference. This supports audit traceability and future integration reconciliation between Mailchimp and Denticon.

Denticon appointment records (date, procedure, provider, status) have no Mailchimp equivalent. Mailchimp contacts do not support appointment scheduling or procedure history. We do not migrate appointment data — your practice should retain Denticon or an alternative scheduling system for operational needs. If appointment-based outreach is required, a separate integration or manual workflow is needed post-migration.

Denticon clinical data (treatment plans, perio charting, clinical notes, imaging references, procedure codes) is HIPAA-protected and has no structure in Mailchimp. We do not migrate clinical records. If clinical history needs to be referenced in Mailchimp campaigns, it must be manually summarized and added as a custom text block — Mailchimp's contact model is not designed for clinical data storage.

Denticon billing records, payment history, outstanding balances, and insurance claims have no Mailchimp equivalent. Mailchimp is an email marketing platform, not a financial or practice management system. We do not migrate billing data. For billing-related patient communication, your team should use Denticon's built-in billing tools or a dedicated RCM platform.

Denticon's 2-way texting and patient communication logs are part of the patient record but have no Mailchimp equivalent. Mailchimp supports email campaigns and automated email responses, but not SMS or in-system messaging threads. Communication history is retained in Denticon; the migration does not carry over past message threads.

If Denticon tracks patient marketing consent, we map this to Mailchimp's subscriber status (subscribed, unsubscribed, pending) and optionally a merge field flag. Patients without documented marketing opt-in are imported as non-subscribed in Mailchimp to protect deliverability and compliance. Double opt-in configuration is available as a post-migration step.