Migrate from Gensolve Practice Manager to Mailchimp

Every Gensolve client with a valid email address becomes one Mailchimp contact. Clients without an email address cannot migrate to Mailchimp and are flagged for separate handling. Primary contact fields (name, email, phone) map directly; all other Gensolve fields become Mailchimp merge fields or tags.

When the SMS opt-in flag is true, the contact status is set to subscribed; when false, unsubscribed to respect consent preferences and Mailchimp's compliance requirements. The mapping also respects Mailchimp's double opt-in settings if enabled, and we can optionally apply a GDPR-related tag to flag contacts awaiting explicit confirmation. Any contacts with missing opt-in data are flagged for manual review before import.

Gensolve practitioners (clinicians) are not native Mailchimp contacts. We create a PRACTITIONER text merge field on the Mailchimp audience and populate it with the assigned practitioner name per client. When multiple practitioners are assigned, all names are combined or split into tags to preserve the relationship.

Gensolve sites represent physical clinic locations. Each site maps to a SITE text merge field on the Mailchimp audience. If the practice splits clients by site, we can also create separate Mailchimp Audiences per site and import clients accordingly, using audience tags as a fallback.

Gensolve referrers (referring doctors or clinics) are practitioner-adjacent records. We map the referring practitioner or clinic name into a REFERRER_NAME merge field. If a client has no referrer in Gensolve, the merge field is left blank. This field is for marketing attribution only — Mailchimp has no native referrer object.

Gensolve custom fields created via Administration > Custom Fields support multiple types: checkbox, checkbox group, combo box, date/time picker, list of values, radio button, score field, and text box. Each type maps to a Mailchimp merge field of the closest type (text, number, date, or checkbox as boolean text). Clinical assessment data becomes hidden tags for segmentation.

Gensolve appointment history has no direct Mailchimp equivalent. We extract the most recent appointment date and type as LAST_APPOINTMENT and LAST_APPOINTMENT_TYPE merge fields for re-engagement use cases. Full appointment history does not migrate — Mailchimp automations cannot reconstruct Gensolve's clinical scheduling logic.

Gensolve invoices, payments, ACC claims, and Medicare billing records have no Mailchimp equivalent. We can surface outstanding balance as a text merge field for reference, but Mailchimp contacts cannot store financial transaction history. Invoice reconciliation remains in Gensolve or the accounting system.

Gensolve inventory management tracks clinical supplies and stock levels. Mailchimp contacts have no inventory concept. If the practice uses Gensolve for product sales tracking (e.g., supplements), that data does not migrate to Mailchimp and must remain in Gensolve or a separate inventory system.

Gensolve template merges and reporting exports are not automation logic. Appointment reminder sequences, birthday outreach, or inactive-client follow-ups created in Gensolve do not transfer to Mailchimp. We export Gensolve's workflow definitions as a reference document so your Mailchimp admin can rebuild automations using Mailchimp's automation builder.