Migrate from Quanum Practice Management to Mailchimp

Patient first name, last name, email address, phone number, and physical address map directly to Mailchimp subscriber fields. These are the primary data elements that carry over intact. Email address is the unique identifier in Mailchimp and must be present for every migrated contact.

Quanum PM stores patient communication consent preferences within the patient record. These translate to Mailchimp subscriber status (subscribed, unsubscribed) and can be reinforced with a marketing_consent tag. Only patients with confirmed opt-in migrate as subscribed; unclear consent status is flagged for manual review.

Appointment date, type, and provider from Quanum PM do not map to a native Mailchimp object. FlitStack extracts the most-recent appointment date as a custom merge field and tags contacts by appointment type (e.g., Annual Physical, Follow-Up) to enable segmentation without a scheduling construct.

Insurance carrier and plan name from Quanum PM have no native Mailchimp field. These are created as text merge fields (INSURER_NAME, PLAN_NAME) and optionally expressed as tags for filtering patient segments by coverage type — useful for benefits communication campaigns.

Quanum PM recall scheduling — follow-up dates set by providers — is preserved as date-type merge fields in Mailchimp so recall campaigns can be triggered via date-based segments. This is one of the highest-value custom fields for a medical practice migrating to Mailchimp.

Quanum PM billing account status maps directly to Mailchimp tags for contact classification. Active accounts receive an 'Active_Patient' tag enabling standard outreach campaigns. Pending and closed accounts are tagged distinctly so billing-related communications can be directed only to appropriate patient groups without disturbing patients whose accounts are already settled or inactive.

Practices with multiple locations in Quanum PM can route contacts to separate Mailchimp audiences per location or consolidate into one audience with a LOCATION_TAG. FlitStack presents both options: separate audiences (better for multi-brand practices) vs. single audience with location tags (simpler for single-brand multi-location).

Quanum PM provider attribution maps to Mailchimp merge fields so patients can be segmented by their assigned provider. Provider email addresses are included as a merge field so campaigns can reference the patient's care team without exposing internal contact data.

Clinical data stored in Quanum PM — lab orders, results, problem lists, medication histories, allergy records, clinical encounter notes — has no Mailchimp construct. These records are excluded from migration and must remain in a HIPAA-compliant clinical system. FlitStack generates a structured clinical data export file as a reference archive.

Billing and financial records in Quanum PM — procedure codes (CPT, HCPCS), charges, payments, adjustments, claim status, payer remittances — are financial data with no Mailchimp equivalent. These must remain in a billing or RCM system. FlitStack exports this data as a structured CSV for import into a replacement practice management or billing platform.

Quanum PM workflow automation — automated appointment reminders, recall triggers, insurance verification rules — operates within the practice management context and cannot be translated to Mailchimp's campaign automation model. Mailchimp automations must be rebuilt manually in Mailchimp's automation builder based on the migrated contact structure.

Custom billing codes, modifiers, and payer-specific claim adjustments defined in Quanum PM represent billing configuration and practice-specific rules rather than contact data, so they do not migrate to Mailchimp. Practices must manually configure equivalent billing logic within their replacement billing or revenue cycle management platform as a separate configuration task after the contact migration is complete.