Migrate from Advance Practice Management Suite to Mailchimp

Every patient record with an email address maps directly to a Mailchimp contact within the target audience. Patients without email addresses cannot be added to Mailchimp — we flag these records separately as undeliverable contacts for your team to handle outside the migration.

First name, last name, email, phone, and postal address map to Mailchimp's native contact fields (FNAME, LNAME, EMAIL, PHONE, ADDRESS). Date of birth, gender, and any extended demographics migrate as merge fields since Mailchimp has no native DOB or gender field.

Insurance properties map to Mailchimp merge fields named INSURANCECARRIER, POLICYNUMBER, GROUPNUMBER, and SUBSCRIBERID. These are created as TEXT merge fields before migration. If your source stores multiple insurance plans per patient (primary, secondary), we create separate merge field sets and note the limitation in the mapping plan.

Referral source (physician name, clinic name, website form, or other origin) maps to a single REFERRALSOURCE TEXT merge field on each contact. If the source stores a structured pick‑list of referral sources, we apply value mapping to keep the exact label in Mailchimp, and any unmapped or missing values are logged as exceptions for manual review before the migration finalizes.

The most recent patient visit date migrates as a LASTVISIT DATE merge field in Mailchimp. If the source stores visit history as a multi-row table (multiple visits), we extract the latest date only — full visit history requires a separate note in the migration plan since Mailchimp contacts do not support multi-row historical data.

Patient conditions are challenging because practice management systems store conditions as a multi-select list while Mailchimp merge fields are single-value. We store the most significant or most recent condition as a CONDITION merge field and optionally create Mailchimp tags per condition for segmentation. Full condition history requires external storage or a documented exclusion.

Clinical notes, SOAP notes, progress notes, and any structured clinical documentation have no Mailchimp schema equivalent. These records are documented as excluded from the migration. FlitStack exports a clinical notes CSV separately so your team can decide whether to store it externally, print as PDFs, or retain in the source system for compliance.

Appointment scheduling records cannot be represented in Mailchimp. Mailchimp has no calendar, scheduling, or appointment object. We do not migrate appointments. If appointment reminders are needed in Mailchimp, the practice must configure Mailchimp automations separately using the LASTVISIT date or a calculated next-appointment date as the trigger.

Billing records, claims status, outstanding balances, and payment history are excluded from Mailchimp migration. Mailchimp is not a billing or financial system. We document the billing data fields present in the source and flag them as excluded so the practice is aware before migration runs.

Patients marked as unsubscribed or opted out in the practice management system are exported as a Mailchimp suppression list import. This prevents the migration from inadvertently re-adding suppressed contacts to the Mailchimp audience, which would violate email compliance and damage sender reputation.

If the migration targets a single Mailchimp audience, practice name and location become merge fields on each contact. If the practice has multiple locations requiring separate audiences, we create separate audiences per location and assign contacts accordingly — this doubles mapping validation work and increases migration cost.

Patient classification labels from the practice management system map directly to Mailchimp tags on each contact. Tags enable segmentation for targeted email campaigns. We map every source label to a corresponding Mailchimp tag and note any labels that exceed Mailchimp's tag character limits.

The source system's Medical Record Number migrates as a MRN TEXT merge field on each contact. This preserves the link between Mailchimp contacts and source patient records, which is critical for patient lookup, support requests, and any future data reconciliation.

Emergency contact name and phone number are stored as EMERGCONTACTNAME and EMERGCONTACTPHONE merge fields on each contact. Mailchimp provides no native emergency‑contact field, so these custom merge fields are created specifically for the migration and count toward the 30‑field per‑audience limit. Your team can leverage them in patient‑facing communications, appointment confirmations, or emergency notifications as needed.