Migrate from Spotler Mail+ to Microsoft Dynamics 365 Sales

Spotler Contacts with no purchase history or marketing qualification score map to Microsoft Dynamics 365 Sales Lead. Spotler Contacts with an assigned sales rep, active deal association, or customer status map to Dynamics Contact attached to an Account. We compute the split during scoping using Spotler tag values and score thresholds defined by the customer, and store the original Spotler contact ID in a custom field for cross-system audit and reconciliation.

Spotler Tags are contact-level label attributes accessible via the REST API. We migrate them as Dynamics multi-select option set values on the Contact object, preserving the tag name string and mapping multi-value tags to the option set delimited format. Option set values are defined in the Dynamics solution before Contact import begins.

Spotler lead scoring values stored as numeric contact properties map directly to Dynamics number fields on Contact. We create a custom number field with appropriate decimal precision matching the source Spotler score range, and migrate the score value with the original Spotler timestamp as a secondary field for longitudinal reporting.

Spotler supports text, numeric, currency, list, date, and permission field types. We map each Spotler field type to its Dynamics equivalent: text to Single Line of Text, numeric to Whole Number or Decimal depending on precision, currency to Currency type with the correct ISO precision, list to Option Set, date to Date field, and permission to Two Options boolean. Import column names must match Spotler database field names exactly; we validate the field registry before migration.

Spotler Mailings are API-accessible send records with subject, sender, content, and send date. We migrate mailing metadata as Campaign records in Dynamics with the send date, open rate, click rate, and delivery status stored on custom Campaign fields. Opens and clicks migrate as CampaignActivity records if they fall within the 24-month Spotler retention window. We scope the mailing history migration to the active window and flag any pre-window records as unavailable per Spotler's anonymization policy.

Spotler segmentation rules themselves are not exportable as executable logic. We extract the resulting contact sets as static lists or marketing lists in Microsoft Dynamics 365 Sales , preserving the list name and member contacts. The segmentation rule logic is documented for the customer's admin to recreate in Dynamics Campaign or Customer Insights segmentation builder.

Spotler form submissions export as flat records rather than relational question-response data. We denormalize each form submission into Contact custom fields using a field naming convention that encodes the form name and question label, or into Note records attached to the Contact for longer-form responses. Survey closure rules do not export and are noted for manual rebuild in Dynamics Forms or a Power Apps portal.

Spotler drag-and-drop email templates do not export in a portable format. We extract the rendered HTML content, inline CSS, and embedded image URLs as a content package for manual reassembly in Dynamics Email Template editor or SharePoint. The template layout structure is documented with a screenshot reference so the customer's marketing team can recreate the visual design.

Spotler user accounts with roles and access levels map to Dynamics User records. We extract user name, email address, and role assignments by email match against the destination Dynamics org. Any Spotler user without a matching Dynamics User is held in a reconciliation queue for the customer's admin to provision before Contact import begins.