Migrate from Spotler CRM to Mailchimp

Spotler CRM Contacts map 1:1 to Mailchimp Audience members by email address as the dedupe key. Standard fields (first name, last name, email, phone, address) map to Mailchimp's built-in merge fields (FNAME, LNAME, EMAIL, PHONE, ADDRESS). Custom field values on Spotler Contacts migrate to Mailchimp merge fields that we pre-create in the destination Audience before import. Opt-in and email consent status migrates to Mailchimp's subscribed/unsubscribed status flag.

Mailchimp has no native Company or Account object. Spotler Company records cannot migrate as structured account records. We extract the Company name and industry per Contact and recreate them as Mailchimp Groups (company name) and Tags (industry) on the corresponding Audience member. If the customer relies on Company-level segmentation for email sends, we recommend a Group-based structure in Mailchimp to replicate account-level filtering.

Mailchimp does not have a Deal, Opportunity, or pipeline object. Spotler CRM Opportunities cannot migrate to any Mailchimp record type. We flag every Opportunity record during discovery, note the pipeline stage and deal value in the handoff document, and advise the customer to manage deal tracking in a separate tool post-migration or to adopt Mailchimp's Retargeting feature for recapturing abandoned-cart style campaigns tied to deal-stage events.

Spotler CRM Activity records (calls, emails, meetings, tasks, notes) link to Contacts or Companies and form the CRM activity timeline. Mailchimp stores only campaign-level engagement metrics (opens, clicks, unsubscribes) and does not have a native activity timeline for individual contacts. We do not migrate Activities. We document the activity volume per Contact in the handoff spreadsheet so the customer can assess which contacts had high engagement history in Spotler CRM before migrating.

Spotler CRM custom fields on Contacts (dropdown, text, number, date, checkbox types) migrate to Mailchimp merge fields. We export the field definition table alongside the data export, create matching merge fields in the Mailchimp Audience before import, and map field values row by row. Dropdown list values in Spotler CRM are stored as reference IDs in the export; we resolve these to display labels and recreate the corresponding Mailchimp merge field options. Merge field types in Mailchimp are limited to text, number, date, phone, website, image, and dropdown; unsupported types (e.g., multi-select, rich text) are stored as plain-text JSON in a single text merge field.

Spotler CRM Tags on Contacts migrate directly to Mailchimp Tags on the corresponding Audience member. We export tag names per contact and recreate them as Mailchimp Tags during import. If the customer uses Spotler static Lists, these map to Mailchimp Groups (where a Group is a category and the list name becomes the Group name, with individual contacts as Group members). Dynamic segments in Spotler CRM have no Mailchimp equivalent and must be recreated using Mailchimp's segment builder post-migration.

Spotler CRM Users (sales reps, admins) map to Mailchimp account roles. We export the user table and note which contacts were assigned to which owner. Owner assignment does not transfer as a field on the contact record in Mailchimp; instead, we document the owner-to-contact mapping in the handoff document so the customer can assign Mailchimp account access to the corresponding team members post-migration.

Spotler CRM Workflows store automation logic referencing field IDs, object types, and internal identifiers. Mailchimp Customer Journeys use a different trigger model (event-based rather than property-change-based) and cannot import Spotler workflow definitions. We do not migrate Workflows. We deliver a written workflow inventory document listing every active Spotler CRM Workflow with its trigger, conditions, and actions so the customer's admin can rebuild equivalent automations in Mailchimp Customer Journeys post-migration.