Migrate from NeoDeck Holdings to Mailchimp

NeoDeck patient contact records map directly to Mailchimp contacts in your target audience. The patient's email address is the required key — contacts without a valid email address are excluded from migration. We validate email deliverability before inserting into Mailchimp.

Direct map. Mailchimp's FNAME merge field is a standard field on every audience. We populate it from NeoDeck's patient first-name property. If the source field is empty, the contact is created without FNAME and tagged as 'incomplete name' in Mailchimp.

Direct map similar to FNAME. LNAME maps directly from NeoDeck's patient last-name property. Incomplete last names are permitted in Mailchimp but flagged for your team's post-migration review. This ensures you can follow up to complete missing contact information without blocking the migration.

The email address is the primary key in Mailchimp and must be present on every contact. We deduplicate by email during migration — if NeoDeck has duplicate patient records for the same email, we create one Mailchimp contact and merge the other fields. All associated tags and merge field values from duplicate records are consolidated into the single contact.

Direct map to Mailchimp's standard phone field. Phone numbers migrate regardless of your SMS capabilities status — if SMS is not yet enabled, the field populates but remains inactive until you activate Mailchimp SMS. Note that Mailchimp phone numbers are used for SMS campaigns only if your account has SMS capabilities enabled.

NeoDeck's provider objects do not have a native equivalent in Mailchimp. We create a PROVNAME merge field on the Mailchimp audience and populate it with the provider name associated with each patient record. You can use this field to segment patients by their care provider in Mailchimp campaigns, enabling targeted newsletters or provider-specific health tips.

Insurance carrier maps to a custom INS_CARRIER merge field. NeoDeck stores carrier as a text field; we map it directly. If your NeoDeck setup uses an insurance-carrier pick-list, we apply value-mapping to ensure consistent capitalization and naming across all migrated records. This prevents segmentation issues caused by inconsistent carrier naming.

NeoDeck patient type values such as 'New Patient', 'Returning', or 'Specialty Care' have no Mailchimp equivalent. We create a PATIENT_TYPE pick-list merge field and map values directly. This enables you to run onboarding drip sequences for new patients in Mailchimp and segment returning patients for follow-up care campaigns.

NeoDeck's marketing consent flag maps to Mailchimp's contact status. Contacts with explicit marketing consent in NeoDeck are inserted as 'subscribed' in Mailchimp. Contacts without consent are inserted as 'non-subscribed' — Mailchimp will not send marketing emails to these contacts without a re-permission campaign. Re-engagement campaigns require a separate permission-capture workflow in Mailchimp before these contacts can receive sends.

NeoDeck labels on patient records such as 'appointment-reminder', 'billing-followup', or 'wellness-series' migrate as Mailchimp tags. Tags are additive — if a patient has multiple NeoDeck labels, all apply as tags in Mailchimp. We recommend reviewing tag names post-migration to consolidate duplicates and establish a consistent tagging taxonomy for your marketing operations.

Mailchimp has no native appointment or visit concept. We create a LAST_VISIT date merge field and populate it from NeoDeck. This supports re-engagement automations — for example, you can configure Mailchimp to send re-engagement campaigns to contacts whose LAST_VISIT is more than 90 days ago, targeting lapsed patients for follow-up appointments.

NeoDeck billing status values such as 'paid', 'pending', or 'insurance-submitted' have no native Mailchimp equivalent. We create a BILLSTATUS merge field and map values directly. You can use this field for conditional content in billing-related Mailchimp campaigns — for example, sending different messages to patients with 'pending' versus 'paid' status.

NeoDeck custom patient properties such as care program enrollment, referral source, and preferred contact method migrate as custom merge fields in Mailchimp. Mailchimp allows up to 30 merge fields per audience — if your NeoDeck schema exceeds this, we prioritize the fields used in your most important segmentation rules and surface the remainder for a second-pass migration.

NeoDeck stores addresses as a structured object. Mailchimp has separate ADDRESS merge fields (ADDR1, CITY, STATE, ZIP) plus a generic ADDRESS field. We split NeoDeck's address into the standard Mailchimp address fields. If NeoDeck stores a two-line address (street + suite), the second line is appended to ADDR1 or placed in a custom merge field per your preference.

NeoDeck appointment reminder workflows have no direct Mailchimp equivalent. We export the workflow definition including trigger conditions, timing intervals, and message content as a reference document. Your team rebuilds the automation in Mailchimp Customer Journeys using the exported definitions as a blueprint. The document includes step-by-step logic so your Mailchimp partner can replicate the workflow accurately.