Migrate from Visual Practice to Mailchimp

Mailchimp's flat subscriber model collapses multi-record patient data

Visual Practice patients can have N appointments, N treatment plans, and N insurance records all linked to one patient ID. Mailchimp has no native linked-record model — each subscriber has one profile. Appointment history and treatment records cannot be displayed within Mailchimp's contact view. We export full appointment and treatment histories to CSV so your team can reference them during recall campaign planning. Recurrence-based automations (e.g., 'send recall 6 months after last cleaning') must be rebuilt using Mailchimp's date-based automation triggers with the LASTAPPT merge field as the anchor date.

HIPAA compliance requires Mailchimp Pro + signed BAA before patient data lands

Visual Practice stores protected health information subject to HIPAA. Mailchimp is not HIPAA-compliant by default — your practice needs a Business Associate Agreement with Mailchimp and must be on a Pro plan to qualify. We will not migrate patient data to a non-BAA Mailchimp account. If your Visual Practice data includes treatment notes, diagnosis codes, or clinical fields beyond basic demographics, those fields must be excluded or handled under the BAA. FlitStack can export a list of fields being migrated and their data types to help your compliance team identify any PHI that should not enter Mailchimp.

Billing, insurance, and payment records have no Mailchimp equivalent

Visual Practice tracks outstanding balances, insurance claims, payment history, and billing status per patient. Mailchimp has no billing model — none of these fields map. Attempting to store financial data in Mailchimp merge fields creates compliance risk (billing data in an email marketing platform) and operational confusion (no reporting or reconciliation tools). We flag all billing-related fields during the pre-migration audit and exclude them from the Mailchimp import. Your billing team should retain Visual Practice access or migrate to a dedicated practice management or accounting tool.

Visual Practice automations and recall workflows must be rebuilt in Mailchimp

Visual Practice appointment reminders, recall notifications, and follow-up sequences are platform-native automations that do not transfer to Mailchimp. Mailchimp's automation builder uses different trigger logic — instead of 'send when recall_date = today', you build 'wait until DATE_DIFF(LASTAPPT, today) = RECALLDAYS then send'. We deliver a Workflow Recreation Map documenting every Visual Practice automation with its trigger, conditions, and actions so your Mailchimp admin can rebuild them. Date-based automation logic is the main rebuild effort for recall campaigns.

Duplicate email handling across merged patient records

Visual Practice may have duplicate patient records (same person with separate entries due to intake errors) or patients who share one email address (e.g., family members on one inbox). Mailchimp enforces one email address per subscriber in an audience — duplicate emails result in a single subscriber record that gets updated with the most recent data. We flag duplicate emails during the pre-migration audit and provide a merge decision report so you can decide which Visual Practice record takes priority or whether to combine family members under one subscriber with tags indicating the relationship.