Migrate from Spotler Mail+ to Mailchimp

Spotler Mail+ contacts map to Mailchimp subscribers within a defined Audience. Email address is the dedupe key. We map standard Spotler fields (first name, last name, email) directly to Mailchimp FNAME and LNAME merge fields. Custom fields require type selection in Mailchimp before import: text fields map to Mailchimp text merge fields, numeric fields to number merge fields, date fields to date merge fields, and list fields to radio or dropdown merge fields depending on whether single or multiple selection applies in Spotler.

Spotler Mail+ contact tags map directly to Mailchimp tags. Tags are extracted as a list per contact and bulk-applied via the Mailchimp Tags API during import. There is no tag limit in Mailchimp beyond audience size. Tags used for behavioral scoring (Spotler numeric scores as tags) require a separate mapping strategy: we either convert Spotler score ranges to Mailchimp tags (e.g., score_80_plus) or map numeric scores to a number merge field, depending on the customer's segmentation preference.

Spotler Mail+ lead scoring values stored as numeric contact properties map to a Mailchimp number merge field (e.g., leadscore__nm). Alternatively, the customer can elect to convert score ranges into tags (hot, warm, cold) for simpler segmentation in Mailchimp's automation builder. We confirm the preferred approach during scoping based on how the customer uses Spotler scores for campaign targeting.

Spotler Mail+ segmentations export as static contact sets (the resulting contact IDs), not as rule definitions. We extract each segmentation's contact membership and create a Mailchimp Group with all members subscribed to that group. The segmentation logic (tag-based, score-based, field-based conditions, exclusions) is documented in the handoff document for manual rebuild in Mailchimp using its Segment builder with AND/OR condition groups.

Spotler Mail+ database fields of type text, numeric, currency, list, date, date of birth, and permission require field-type mapping to Mailchimp merge field types. List fields (multi-select) map to Mailchimp checkboxes or dropdown merge fields depending on Spotler field configuration. Permission fields (consent flags) map to Mailchimp interest groups or the subscriber's marketing consent status field. Date fields map to Mailchimp date merge fields. Currency fields map to text merge fields with currency formatting since Mailchimp does not have a native currency field type.

Spotler Mail+ anonymizes mailing interaction data (opens, clicks, delivery stats) after 24 months. Mailchimp similarly limits engagement data migration to 90 days. The intersection of these two windows means that for any Spotler data older than 24 months, the export returns empty or scrubbed records; for data between 24 and 90 days, Mailchimp will accept it during import. We flag this limitation in scoping, scope the migration to the most recent 24-month window from Spotler, and deliver a written record of available Spotler analytics export for the customer's manual reference in Mailchimp reports.

Unsubscribed, bounced, and complained contacts from Spotler Mail+ are exported and imported into Mailchimp as a suppression list before any subscriber import begins. This step is required to prevent the new Mailchimp account from inadvertently mailing contacts that have already opted out, which would damage sender reputation and inbox placement. We export unsubscribes, bounces (hard and soft), and spam complaints from Spotler and upload them to Mailchimp via the Suppression Lists API.

Spotler Mail+ email templates are platform-native assets with drag-and-drop layout structures that do not export as portable HTML/CSS. We extract template content (text, image URLs, and copy) from the Spotler editor and deliver it as a structured content document. The customer's admin reassembles templates in Mailchimp using its drag-and-drop builder or imports HTML with CSS re-validation for cross-client compatibility. We do not rebuild Spotler templates as Mailchimp templates as part of standard migration scope.

Spotler Mail+ form submissions and survey responses export as flat contact records with denormalized field values rather than maintaining the question-response structure as distinct objects. Form closure rules (date-triggered or quota-triggered) do not export. We do not migrate form submissions as a data object. If the customer requires form submission history in Mailchimp, we recommend setting up Mailchimp forms and embedding them on the relevant web properties post-migration to capture new submissions.

Spotler Mail+ user accounts with predefined roles and access levels are documented. Mailchimp's permission model uses account-level roles (Admin, Manager, Author, Viewer) and audience-level subscriber roles (Subscribe, Unsubscribe, Delete). We map Spotler user roles to Mailchimp account roles where applicable and flag any role-level permissions that require manual configuration post-migration in Mailchimp account settings.