Migrate from Panacea to Mailchimp

Each Panacea Contact becomes a single Mailchimp Member within the target Audience. Email address is the unique key — if a member with the same email already exists in Mailchimp, FlitStack updates the existing record rather than creating a duplicate. Phone number migrates as a custom merge field if Mailchimp's phone-compatible fields are enabled on the account.

Panacea's firstname property maps directly to Mailchimp's built-in FNAME merge tag. If the contact record has no first name, the merge field is left blank — Mailchimp allows blank merge field values without rejecting the member import. This preserves the source data without forcing incomplete information into the field.

Panacea's lastname property maps directly to Mailchimp's built-in LNAME merge tag. Blank last names are preserved as blank values in Mailchimp. For contacts where lastname is missing but a company name exists, FlitStack flags the record for your team to decide whether to populate LNAME with the company name or leave it blank.

Email is the primary identifier and the only required field for a Mailchimp member record. FlitStack validates email format before import and routes malformed addresses to a separate error report. Bounced or unsubscribed emails from Panacea are imported as suppressed members in Mailchimp to preserve list hygiene.

Panacea's company association (the related Company record name) maps to Mailchimp's COMPANY merge tag. Note that Mailchimp COMPANY is a flat text field with no link back to an Account or related record — if you need company-level segmentation, tags or segments should be built around the COMPANY value after migration.

Panacea phone number maps to Mailchimp's PHONE merge field. PHONE must be enabled in the audience's merge field settings before the migration runs — it is not active by default. International phone formats are preserved as entered in Panacea without reformatting.

Panacea contact tags and group memberships become Mailchimp Tags on the member record. Tags are not a standard field in Panacea — if your Panacea setup uses custom tagging or labeling, FlitStack maps each unique tag value to a Mailchimp Tag. Tag count and tag names are preserved exactly. Mailchimp allows unlimited tags per member; Panacea tag limits, if any, are documented during discovery.

Panacea's Company records have no direct Mailchimp equivalent. The company name is preserved as the COMPANY merge field on each related contact. If your Panacea instance uses company-level segmentation (e.g., all contacts at Company X belong to a specific region), FlitStack creates a tag on each contact named after the company so Mailchimp segments can reproduce the grouping.

Panacea custom properties (any field beyond standard contact fields) require a Mailchimp merge field to be created before migration. FlitStack creates merge fields named after the source property API name truncated to Mailchimp's 30-character limit. Text properties over 255 characters are truncated and flagged; long-text properties are stored as tags with a prefix indicating the source field name.

Panacea deal records have no Mailchimp equivalent — email marketing platforms do not model sales pipeline stages. FlitStack preserves deal stage as a tag on the related contact (e.g., Tag: DealStage-Prospecting) and exports a separate deal mapping reference CSV for your team to use when rebuilding Mailchimp segments based on sales stage.

File attachments on Panacea contact or company records (e.g., intake forms, signed documents) cannot migrate to Mailchimp member records. FlitStack exports a file manifest with original filenames, download URLs, and the associated contact email so your team can re-host files in a shared drive or CMS and link to them from Mailchimp campaigns manually.

Panacea workflows and automation rules do not transfer to Mailchimp. FlitStack exports the workflow definitions (trigger conditions, action steps, and logic branches) as a JSON reference document your Mailchimp admin uses to rebuild equivalent Customer Journeys in Mailchimp's automation builder.