Migrate from AeronaClinic to Mailchimp

Every AeronaClinic patient record maps to one Mailchimp contact. The patient's email address is the unique key — if email is missing or invalid, FlitStack flags that record for manual review before import so it does not trigger hard bounces in Mailchimp.

Appointment records do not map 1:1 to any single Mailchimp object. Instead, the appointment type (checkup, hygiene, consultation, etc.) applies as a tag on the patient contact, and appointment date, time, and status land as merge fields on that contact record.

Treatment plan name, proposed treatment date, estimated cost, and plan status migrate as Mailchimp custom merge fields against the patient contact. Clinical notes and procedure codes cannot be stored in Mailchimp — these are flagged as no-equivalent data that must remain in AeronaClinic.

Patient address fields including street address, city, state, postcode, and country map directly to Mailchimp's built-in ADDRESS merge field type. Mailchimp uses address data for postal validation and geographic segmentation. All five address components are preserved during migration. Records with incomplete addresses are flagged for manual completion before the full import run.

Mobile phone and landline numbers stored in AeronaClinic map to Mailchimp's PHONE merge field. By default, Mailchimp does not use phone data for SMS outreach unless your account plan includes Mailchimp SMS functionality, but the field is preserved for contact segmentation purposes and can be leveraged for future SMS marketing initiatives. This ensures complete patient contact information carries over.

Clinical notes, treatment notes, medical history, procedure notes, and all clinical documentation stored in AeronaClinic have no equivalent field type in Mailchimp's contact model. Mailchimp contacts support only short text notes, which cannot accommodate detailed clinical information. These records are excluded from migration scope and must remain stored in AeronaClinic as the clinical system of record.

Invoice records, payment history, outstanding balances, insurance claims data, and all financial information stored in AeronaClinic do not map to any Mailchimp object or field type. Mailchimp's contact model has no financial or billing schema whatsoever. These records are explicitly excluded from the migration scope and should remain in AeronaClinic for financial record-keeping and billing management.

Insurance carrier name, policy number, and coverage details stored in AeronaClinic patient records have no Mailchimp equivalent. Mailchimp contacts do not support insurance metadata. If needed, this can be stored as a custom text merge field but Mailchimp does not use it for any built-in function.

The practitioner or provider associated with a patient appointment is extracted and applied as a tag on the contact record in Mailchimp (for example, 'Dr. Smith' or 'hygienist_Jane'). Alternatively, practitioners can be used to create Mailchimp segments based on provider assignment. This enables patients to be filtered and targeted by their preferred practitioner when building campaign audiences and Customer Journey automations.

Any custom fields configured in AeronaClinic — such as referral source, preferred appointment time, membership tier, recall interval, or custom patient classifications — require corresponding custom merge fields to be created in Mailchimp. FlitStack generates these custom fields during the Mailchimp audience setup phase and then maps AeronaClinic values to them on a field-by-field basis before the import run begins.

Patient opt-in and opt-out communication preferences stored in AeronaClinic translate directly to Mailchimp subscriber status values (subscribed, unsubscribed, cleaned). If AeronaClinic records consent for specific communication types such as SMS marketing, email newsletters, or recall reminders, these can map to Mailchimp interest groups if your Mailchimp audience has these groups configured during setup.

Automated appointment-reminder settings in AeronaClinic (email reminder 24h before, SMS reminder 1h before) are a scheduling-system feature with no Mailchimp equivalent. These reminders should be recreated in AeronaClinic or migrated as separate Mailchimp Customer Journey automations triggered by appointment tags.