Migrate from SalesPro CRM to Mailchimp

SalesPro Contact records map to Mailchimp Audience Members using email address as the primary dedupe key. We extract first name, last name, phone, and any custom fields as Mailchimp merge fields (FNAME, LNAME, PHONE, and custom field names). Email validation runs before import to flag bounces and malformed addresses. Contacts with no email address are excluded from the audience and logged separately for the customer's team to resolve manually.

SalesPro Company records do not map to a native Mailchimp object because Mailchimp is contact-centric. We derive Company association in two ways: if the Company name field is populated, we add it as a merge field (COMPANY) on the Audience Member. If the customer wants Company-level segmentation, we create a Mailchimp Tag per unique Company name and apply it to all Contacts belonging to that Company.

SalesPro Groups (if the customer used group-based contact segmentation) map directly to Mailchimp Tags. Tags are applied at the individual contact level and support segmentation in Mailchimp's audience builder. We preserve the original tag name and apply it during the audience import phase.

SalesPro Task records have no Mailchimp equivalent because Mailchimp does not track sales task management. We extract all open and completed Tasks as a CSV inventory with fields: task subject, assignee, due date, status, and associated contact email. The customer receives this as a structured handoff document for manual follow-up in their task management tool of choice.

SalesPro Events (central to the hospitality and venue-sales use case) have no native Mailchimp equivalent. We extract Events as a CSV inventory with fields: event name, date range, group details, associated contact emails, and linked BEO reference. The customer uses this inventory to manually create Mailchimp campaigns or customer journey automations for event-based outreach.

BEO records are auto-generated from Events in SalesPro and contain cost calculations, timeline details, and event specifications. Mailchimp has no BEO object. We extract BEO data as structured CSV with event linkage preserved, and where the customer wants this content in Mailchimp, we map key fields (event date, venue, estimated cost) to custom merge fields on the associated Audience Members or as campaign content in an event-specific email template.

SalesPro Milestones are custom goal or sales-cycle tracking markers with no Mailchimp equivalent. We export Milestones as a CSV with milestone name, associated contact or deal reference, stage, and completion date. The customer receives this as a reference document for rebuilding milestone-based marketing triggers in Mailchimp Customer Journeys if desired.

SalesPro Users map to team member records in Mailchimp (if using Mailchimp's user and permission model) but do not map to Audience Members. We extract the user roster as a CSV with email, role, and active status. If Mailchimp is also used as the team's collaboration tool, the customer provisions Mailchimp user seats separately from audience management.

SalesPro Pipeline Stages and Deal records have no Mailchimp equivalent. We export a Pipeline Stage inventory as CSV showing stage names, order, probability, and associated deal count. The customer uses this to design Mailchimp Customer Journey branches if they want marketing-stage-based email sequences, but Mailchimp does not natively track pipeline progress.

SalesPro Calendar entries map to a booking or appointment record with no Mailchimp equivalent. We export Calendar entries as CSV with booking date, contact email, resource assignment, and status. This inventory supports the customer's manual recreation of event reminder campaigns in Mailchimp if needed.