Migrate from Myprosperity to Mailchimp

Mailchimp counts all contacts toward pricing regardless of subscriber status

Mailchimp bills based on total audience size — including unsubscribed contacts, cleaned contacts, and contacts that have bounced. Myprosperity's practice-portal model prices per active client portal subscription, which is structurally different. After migration, your Mailchimp bill will reflect the full contact count imported, not just opted-in subscribers. We suppress hard-bounced and explicitly unsubscribed contacts at import to keep the billed audience as clean as possible, but any contacts that arrived in Myprosperity without a clear unsubscribe record will count in Mailchimp's pricing from day one. This is a billing construct with no workaround — budget accordingly before migration.

Myprosperity relationship codes must be manually decoded and applied as Mailchimp tags

Myprosperity stores adviser-to-client relationship as an integer code (0=Owner, 1=Accountant, 2=Lawyer, 3=Wife, 4=Husband, 5=Child) with no string label in the API response. Mailchimp has no native relationship field — there is no field that natively holds 'Accountant' or 'Lawyer' on a subscriber record. FlitStack decodes each integer to its string label using Myprosperity's documented enum and applies the result as a tag within a dedicated 'Adviser Role' tag group. If you have more than 5 relationship types in your Myprosperity setup that are not documented in the standard enum, those codes must be flagged before migration so we can add custom value mappings before the tag group is configured in Mailchimp.

Custom profile fields exceeding 40 require pre-migration triage

Mailchimp imposes a 40-merge-field limit per audience. Myprosperity custom profile fields are unbounded — a firm with 60 custom fields (investment profiles, risk assessments, compliance flags) cannot map all of them directly to Mailchimp merge fields on a single audience. We work with you before migration to identify the 40 highest-value fields for email marketing use cases, map those first, and flag the remainder. You can create a second Mailchimp audience for compliance-specific fields or store less-marketing-critical data in a third-party CRM and sync via Mailchimp integration later.

Document vaults and eSignature records have no Mailchimp equivalent

Myprosperity's 50–200GB document vault with Annature eSignature integration stores signed documents, compliance records, and client correspondence. Mailchimp has no document storage, no eSignature capability, and no native attachments in the contact model. Document references and eSignature status from Myprosperity surface as a DOC_VAULT merge field and ESIGN_STATUS tag in Mailchimp — the actual documents must remain in Myprosperity or be moved to a separate document management system. We flag which contacts have pending documents at migration time so you can trigger follow-up sequences in Mailchimp, but the documents themselves stay outside the ESP.

Myprosperity automation logic cannot migrate to Mailchimp Customer Journey Builder

Myprosperity's task reminders, document-request workflows, and client-portal notification automations run inside the wealth-portal context and have no Mailchimp equivalent. These automations must be rebuilt from scratch in Mailchimp's Customer Journey Builder. FlitStack AI can export your Myprosperity workflow definitions as a structured rebuild reference — listing triggers (document pending, portfolio update received, anniversary date), conditions (client tier, adviser role), and actions (send email, assign task) — so your Mailchimp admin can recreate them in Customer Journey Builder without reverse-engineering the logic from scratch.