Migrate from SalesTown CRM to Mailchimp

SalesTown CRM Contacts migrate to Mailchimp Members within a designated Audience. The Contact email address becomes the Member email and the dedupe key. First name, last name, phone, and any standard custom properties map to Mailchimp Merge Fields (FNAME, LNAME, PHONE, and customer-defined MERGE tags). Owner email from SalesTown maps to a Mailchimp Merge Field for record attribution. We run deduplication on email address before load to prevent duplicate Members in the destination Audience.

SalesTown CRM Leads migrate to Mailchimp Members in the same Audience as Contacts, using email as the dedupe key. Leads and Contacts merge into a single Member record in Mailchimp because Mailchimp has no separate Lead object. The original SalesTown Lead status and lead source map to Mailchimp Tags (e.g., tag: lead_source=indiamart, tag: lead_status=qualified) so that Segments can reconstruct the original qualification funnel.

SalesTown CRM Company records have no direct Mailchimp equivalent because Mailchimp is contact-centric rather than account-centric. We map available Company fields (company name, domain, industry) to Mailchimp Merge Fields on the Member record, and store the Company ID as a hidden Merge Field for audit and future reference. If the customer needs account-level segmentation in Mailchimp, we encode Account name as a Tag on each Member so that Segments can filter by company.

SalesTown CRM Deals have no structural equivalent in Mailchimp. Deal amount, stage, owner, and expected close date do not map to any native Mailchimp object. We encode Deal metadata as Tags on the associated Contact or Lead Member record (e.g., tag: deal_amount=50000, tag: deal_stage=negotiation) for historical audit rather than as structured records. The customer receives a written Deal inventory summary showing all migrated Deal fields for manual entry into a spreadsheet or a linked CRM if they retain one.

SalesTown CRM Pipelines have no equivalent in Mailchimp's Audience model. We map each Pipeline name to a Mailchimp Tag Group (Mailchimp's grouping structure for organizing Tags) and encode pipeline membership as Tags within that group. This gives the customer a visual filter layer in Mailchimp Segments that approximates pipeline awareness without a native pipeline object.

SalesTown CRM Pipeline Stages map to individual Tags within the Pipeline Tag Group. For example, a Deal assigned to a Lead pipeline stage becomes tag: Lead_Pipeline/Lead_Sourced. Stage probability percentages are encoded as a Merge Field (STAGE_PROB) on the Member for use in any probability-based Audience analysis the customer runs post-migration.

SalesTown CRM email activities carry timestamp, subject, and direction (sent/received). Mailchimp does not store individual email touchpoints as structured activity records on Members. We create a text-based engagement summary Merge Field on each Member recording the count of historical emails and the date range of email activity. If the customer requires full email thread preservation, we recommend exporting email bodies to a linked document store and referencing them by Contact in the CRM.

SalesTown CRM WhatsApp activities include message status flags and timestamp sequences that are not native to Mailchimp. Flat CSV exports split WhatsApp threads into individual rows, losing thread-parent relationships. We reconstruct thread continuity using timestamp ordering and sender IDs, then write a plain-text engagement summary to a Merge Field on the Member. The full WhatsApp thread does not render in Mailchimp; the summary preserves the fact and volume of WhatsApp engagement for audit purposes.

SalesTown CRM Users map to a Merge Field on the Member record (OWNER_EMAIL) rather than a separate object because Mailchimp has no User/Owner model. We resolve owner email from the destination Mailchimp workspace by cross-referencing against the Member's owner assignment in the source export. Any SalesTown Owner without a matching email in the Mailchimp workspace is flagged in the reconciliation report for the customer's admin to assign manually.

SalesTown CRM email and communication templates have no documented schema and cannot be exported as structured records. We provide a written inventory of available template metadata from the export and flag template body mapping as a post-migration cleanup task. The customer manually recreates templates in Mailchimp's Content Studio using the template inventory as a reference guide.