Migrate from The Dental System to Mailchimp

The Dental System patient records map directly to Mailchimp subscribers. Each patient record with a valid email address becomes one subscriber in the target Mailchimp audience. Patients without email addresses are flagged as excluded records — your team can choose to import phone numbers for SMS campaigns separately.

Mailchimp's standard FNAME and LNAME merge fields accept first and last name directly from The Dental System patient record. No transformation required. These fields populate personalization tokens in email templates like *|FNAME|* and *|LNAME|*. Personalized greetings improve open rates and subscriber engagement. First and last names also enable geographic segmentation when combined with address data, and they support mail-merge for postal campaigns if needed.

The email field on the patient record maps to Mailchimp's subscriber email address — the primary key for the audience. Mailchimp validates email format before accepting the subscriber. Invalid email formats are logged and excluded from the import. Validation ensures your audience stays clean and protects your sender reputation. Duplicate email addresses are detected and consolidated, preserving the most recent subscriber status.

Phone numbers from The Dental System patient record populate Mailchimp's PHONE merge field. Note that phone number availability depends on whether The Dental System stores mobile vs. office phone — we map the primary contact number and flag if multiple phone types exist.

Patient address components from The Dental System (street, city, state, ZIP) map to Mailchimp's ADDRESS merge field. Mailchimp's address merge field requires all components — we flag records missing city, state, or ZIP as incomplete and surface them before the import commits.

Appointment types from The Dental System (e.g., 'Prophy', 'Root Canal', 'Whitening', 'Consultation') become Mailchimp tags on each patient subscriber. This enables segmentation by treatment history — practices can build Mailchimp campaigns targeting patients who received specific procedures or are due for follow-up.

The Dental System recall interval (e.g., 180 days for a cleaning recall) maps to a Mailchimp tag or group like 'Recall: 6-Month'. This becomes the basis for recall automation triggers in Mailchimp Customer Journey Builder. We preserve the original recall date as a custom merge field for date-based segmentation.

Active patients from The Dental System map to subscribed Mailchimp contacts. Inactive or archived patients can be imported as unsubscribed or held in a separate suppression list — your team decides based on re-engagement strategy. We do not automatically import archived patients as active subscribers.

Mailchimp's standard merge fields do not include insurance carrier. We create a custom INSURANCE merge field on the Mailchimp audience and populate it from The Dental System insurance carrier data. This enables segmentation by insurance provider — useful for targeted campaigns about in-network benefits or insurance updates.

The most recent appointment date from The Dental System populates a LAST_VISIT custom merge field in Mailchimp. This date enables segmentation for re-engagement campaigns targeting patients who have not visited within their recall interval. Original timestamp preserved for reporting continuity.

Treatment descriptions from The Dental System are too granular for direct tagging. We map treatment descriptions to category-level tags (Preventive, Restorative, Cosmetic, Emergency) so Mailchimp segments remain actionable. Individual treatment codes can be stored as a custom merge field if granular history is needed.

General patient notes in The Dental System have no Mailchimp equivalent for subscriber-facing purposes. We preserve these notes as Mailchimp internal notes on the subscriber record for admin reference only — they do not appear in email campaigns. Clinical notes are not migrated.

Patient billing balance from The Dental System has no mapping to Mailchimp. Emailing patients about outstanding balances via Mailchimp is not appropriate for HIPAA and billing-compliance reasons. Outstanding balance data is excluded from the migration. If balance reporting is needed, it should be handled within The Dental System or a separate billing tool. Excluding this data prevents accidental exposure of financial information in email campaigns.

We store The Dental System patient record ID as a custom merge field (SOURCE_PATIENT_ID) on each Mailchimp subscriber for traceability, delta-run deduplication, and future cross-reference. This is not visible to subscribers but essential for audit and reconciliation. The SOURCE_PATIENT_ID field also enables incremental syncs from The Dental System, allowing you to update subscriber data without creating duplicates. It serves as the key for integrations with practice management or analytics platforms.