Migrate from PANDA Perio to Mailchimp

Email address uniqueness enforcement creates duplicates from guarantor-linked patients

PANDA Perio allows multiple patients (e.g., spouses or family members) linked to the same guarantor email address. Mailchimp enforces one audience member per email address — a hard constraint in the platform. When duplicate emails are encountered, we flag them for manual resolution: either add a secondary identifier to make emails unique, merge records under one contact with multiple tags, or exclude the duplicate from the import. Practices that imported without resolving this in advance end up with missing contacts after Mailchimp rejects duplicates. We validate email uniqueness against Mailchimp's member status before the migration commits.

Mailchimp merge field 255-character cap truncates long clinical notes

PANDA Perio progress notes and letter templates can contain extensive clinical narrative. Mailchimp merge fields are capped at 255 characters — the same limit as Salesforce text fields. Long-form clinical notes cannot survive a direct field import intact. We handle this by excluding long-text fields from standard field mapping and storing only structured, truncated metadata (procedure codes, dates, provider names) as tags and custom fields. Practices that need to communicate clinical detail via email use PANDA's letter-generation feature to produce PDFs and attach them to campaigns manually rather than pushing raw text through merge fields.

Marketing consent gap requires post-migration re-permission campaign

PANDA Perio does not track marketing opt-in or email consent as a patient-record field. All patients imported as Mailchimp 'subscribed' members by default — but GDPR, CAN-SPAM, and state-level telehealth regulations may require affirmative consent for marketing emails to patients. If your state requires explicit opt-in for healthcare communications, importing without consent verification creates compliance exposure. We flag this as a required decision point before migration and recommend a double opt-in sequence or a re-permission confirmation campaign within the first 30 days after import.

Tag proliferation from treatment codes creates noisy segmentation if not aggregated

PANDA treatment plans can generate dozens of procedure codes per patient over multiple visits. If we apply every historical code as an individual tag, patients end up with 20–50 tags, cluttering Mailchimp's segmentation UI and making campaigns harder to build. We aggregate procedure codes by category (e.g., 'TXN: Surgical' vs. 'TXN: Maintenance') rather than applying each code individually. Practices that want granular per-code tags can opt in during scoping — we configure the aggregation rule upfront to match your campaign strategy.

Mailchimp's suppressed-contact model does not auto-sync unsubscribes back to PANDA

When patients unsubscribe in Mailchimp, their status updates within the Mailchimp audience but does not propagate back to PANDA Perio — Mailchimp is a marketing platform, not a clinical system, and has no mechanism to write back to PANDA's patient database. If your practice uses PANDA to manage appointment reminders via email, unsubscribed contacts will continue to receive PANDA-generated reminders. We recommend either disabling email reminders in PANDA for contacts who have unsubscribed (managed via export of Mailchimp suppression lists) or routing all patient email through Mailchimp post-migration.