Migrate from LeadSimple to Mailchimp

LeadSimple contacts become Mailchimp audience members. Every exported contact field maps to a corresponding Mailchimp standard field or custom merge field. Only contacts with valid email addresses are included in the migration; contacts without emails are flagged separately in a skipped-contacts report for your review and manual handling.

LeadSimple pipeline names (Owner, Tenant, Referral) migrate as Mailchimp tags applied to each member. You can build Segments in Mailchimp from these tags to reproduce pipeline-level filtering for one-off campaigns, enabling targeted outreach based on your original pipeline structure.

LeadSimple stage names (e.g. New, Touring, Application, Lease Signed) map to Mailchimp tags applied per member. This preserves the contact's pipeline progression within Mailchimp's flat member model, which lacks native stage-history tracking.

LeadSimple stage status values (Active, Won, Lost, Dead) have no direct equivalent in Mailchimp's status model. We map them as additional tags — Active and Won contacts import normally, while Lost and Dead contacts are flagged for exclusion or re-permissioning before import to maintain GDPR compliance.

LeadSimple stores property and company data separately. In Mailchimp, the primary property address maps to standard address fields; property name and type map to custom merge fields and tags. Multi-property associations per contact cannot be represented in Mailchimp's flat member structure.

LeadSimple source attribution (Website, Referral, Zillow, etc.) has no Mailchimp native equivalent. We create a LS_SOURCE merge field and populate it with the exact source value from the export, preserving attribution data for segmentation and reporting purposes.

LeadSimple owner and assignee IDs represent internal team members. Since Mailchimp has no ownership model, we store the assignee name as a LS_ASSIGNEE merge field for reference purposes, though assignment-based workflows cannot be replicated in Mailchimp.

LeadSimple ACV is a numeric field that maps directly to a Mailchimp number-type merge field. This value enables segmentation by contract value in Mailchimp (e.g., contacts with ACV above a threshold), but cannot support native deal tracking or pipeline management.

Any LeadSimple custom contact fields migrate to Mailchimp custom merge fields. Text fields exceeding the 255-character limit are flagged during pre-validation for truncation or reformatting before the import run to prevent silent data loss.

LeadSimple workflows, autopilot rules, and process triggers do not export via the standard CSV. We document your workflow definitions during the audit phase so your team can reference them when rebuilding automations in Mailchimp's automation builder.

LeadSimple notes, call logs, email threads, and text history are excluded from the standard contact export. These must be documented separately or linked to contact record IDs before the migration closes, or retrieved via LeadSimple's API at additional scope.

Files attached to LeadSimple contacts are not accessible through the standard export. We recommend downloading all attachments separately before the migration date and re-uploading them to your preferred storage or document management solution.