Migrate from eSalesTrack to Mailchimp

eSalesTrack Contacts map directly to Mailchimp Members within a designated Audience. The Contact's email address becomes the Member email; first name and last name map to FNAME and LNAME merge fields. Any CRM custom field with text, number, or date type maps to a Mailchimp merge field with the same label, subject to the 255-character limit enforced on all Mailchimp merge field values. Long-text CRM fields are truncated at 255 characters or omitted from mapping with a note in the migration report. Email opt-in status is inferred: Contacts without an explicit unsubscribe record are imported as subscribed; Contacts with an unsubscribe flag are imported as unsubscribed. The migration user must confirm with the customer whether eSalesTrack Contacts were collected with explicit marketing consent before setting the initial Member status.

eSalesTrack Accounts do not have a direct Mailchimp equivalent because Mailchimp does not store company-level records as separate objects. Account data (company name, industry, website, annual revenue) is transferred as merge fields on the Member record. We use a naming convention like COMPANY_NAME, COMPANY_INDUSTRY, and COMPANY_WEBSITE on the Mailchimp merge fields to distinguish account-level attributes from contact-level fields. If the customer requires company-level segmentation in Mailchimp (e.g., B2B account-based campaigns), we recommend creating Mailchimp Tags derived from the Account name so that Tags can be used as a segmentation proxy for company groupings.

eSalesTrack Leads are unqualified prospects that have not yet converted to Contacts. In a Mailchimp context, Leads can be imported into a separate Audience (e.g., 'eSalesTrack Leads') or merged into the main Contacts Audience depending on the customer's list hygiene strategy. We do not automatically merge Leads and Contacts into a single Audience because this creates duplicate email addresses if a Lead later converts to Contact in eSalesTrack. The customer chooses the Audience assignment during scoping. If the customer uses Mailchimp only for marketing and plans to manage sales prospects in a separate tool, we recommend keeping Leads in a separate Audience for re-engagement campaigns.

eSalesTrack Opportunities carry deal stage, amount, close date, and owner assignment. Mailchimp has no opportunity or pipeline object. We export Opportunities to a CSV file during migration and deliver it to the customer as an archive for reference. The customer can import this CSV into a separate CRM (e.g., HubSpot Free, Zoho CRM Free) if they wish to retain deal history. Opportunity data cannot be stored inside Mailchimp without compromising the subscriber data model. Owner assignments on Opportunities have no Mailchimp equivalent; we note these in the inventory report as records requiring manual reassignment if the customer adopts a new CRM for pipeline management.

eSalesTrack custom fields on Contact and Account objects map to Mailchimp merge fields of the corresponding type (text, number, or date). We pre-create the merge fields in the destination Mailchimp Audience before import. Mailchimp enforces a 255-character maximum on text merge fields; any custom field exceeding this limit is flagged during scoping and either truncated or excluded from mapping with a documented note. Custom fields of type long text area in eSalesTrack are not suitable for Mailchimp merge fields and are excluded from mapping. We also flag any custom field with a picklist or multi-select type in eSalesTrack, as these map to text-based merge fields in Mailchimp without the picklist constraint, and the customer must validate that the values are acceptable for Mailchimp's tag and segment filtering.

eSalesTrack Owner names cannot be stored as a record attribute in Mailchimp because Members have no owner field. We encode owner information as a Tag on each Member record using the notation OWNER: <OwnerName>. After migration, the customer can use Mailchimp Tags to filter the audience by rep-assigned contacts for reporting purposes. This is a workaround, not a native ownership model; if the customer requires true record-level assignment, we recommend pairing Mailchimp with a lightweight CRM that supports owner fields.

eSalesTrack Workflow automations are not migratable to Mailchimp because they use event-triggered logic (property changes, stage changes, date-based triggers) that has no Mailchimp equivalent in the Audience-Member data model. We deliver a written inventory of every active eSalesTrack Workflow with its trigger, conditions, and actions. The customer's admin rebuilds equivalent automations inside Mailchimp's Automation builder (available on Standard and Premium plans) using the migrated contact data and merge fields as the basis for segment conditions and campaign triggers.

eSalesTrack engagement history (logged calls, emails, meetings, notes attached to Contacts or Accounts) has no Mailchimp equivalent. Mailchimp tracks campaign-level engagement (opens, clicks, unsubscribes, bounces) but not rep-level activity notes. We export engagement history to a CSV archive during migration. If the customer requires engagement history to be available post-migration, we recommend exporting it as a PDF or CSV and attaching it to the relevant Contact records in a separate CRM tool or document management system.