Migrate from Prospects CRM to Mailchimp

Deal and pipeline data has no Mailchimp structural equivalent

Prospects CRM stores deals with amounts, stages, close dates, and owners in a relational model with foreign-key links to contacts. Mailchimp has no opportunity or deal object — deal fields can only be stored as custom merge fields and stage values as tags. This means deal-level reporting, pipeline visualization, and deal-related automations in Prospects CRM have no Mailchimp equivalent. We preserve all deal data as merge fields and tags for reference and rebuild use, but the pipeline management logic must be reconstructed in Mailchimp's Customer Journey builder post-migration. This is the highest-impact gap in the data model translation.

N:N contact-to-company associations collapse to one company per contact

Prospects CRM supports multiple company associations per contact — a sales rep may link a contact to both their employer's company and a partner company for multi-party deal tracking. Mailchimp's contact model has a single COMPANY merge field per member, not a relational junction. We resolve the primary linked company (most recently modified by default, or per your specified rule) to the COMPANY merge field, and store all secondary company links as tags prefixed with 'also-linked:'. This loses the relational integrity of the multi-company association for segmentation purposes.

Mailchimp's audience model does not preserve note author and timestamp

Prospects CRM attaches notes to contacts with original author, body content, and create timestamp — this history is often critical for account management and deal context. Mailchimp's tagging model can store note content as tags, but it cannot preserve the original author name or creation date per note entry. A note reading 'Champion contact, prefers email over calls — Nov 2024, J. Smith' becomes a tag 'note: champion contact' with no attribution or date. We disclose this limitation before migration and give teams the option to include a truncated note body as a tag prefix rather than losing the content entirely.

Inventory-order integration data does not transfer to Mailchimp

Prospects CRM's defining feature is live inventory and order data pulled from Unleashed, Katana, Cin7, or similar back-office systems. This integration data — live stock levels, order history, purchase frequency, product allocations — lives in Prospects CRM's data model and has no Mailchimp equivalent. The data cannot be mapped to merge fields or tags in a way that preserves its operational meaning. Teams requiring inventory-aware email segmentation in Mailchimp must rebuild that logic through Mailchimp's e-commerce integration or a third-party middleware layer pulling directly from the back-office system.

Workflows, sequences, and automation logic do not migrate

Prospects CRM workflows and sequences — the business logic that routes leads, triggers follow-up tasks, or automates outreach based on deal stage — are automation definitions, not data. Mailchimp's Customer Journey and automation tools build this logic differently: event triggers, time delays, A/B conditions, and goal actions are configured from scratch in Mailchimp's builder. We export Prospects CRM workflow definitions as a written reference document for your Mailchimp admin to use during the rebuild phase. The automation logic itself must be rebuilt; we do not migrate it.