Migrate from Spotler Mail+ to HighLevel

Spotler Mail+ Contacts map directly to GoHighLevel Contacts. Standard fields (email, first name, last name, phone) map 1:1. Custom fields (text, numeric, currency, date) map to GoHighLevel custom fields of the corresponding type. We validate the destination custom field schema before import and use GoHighLevel's Contact API to insert records with upsert matching on email address as the primary key.

Spotler Mail+ Tags are contact-level label attributes that map 1:1 to GoHighLevel Contact Tags. We extract all unique tag names from the Contact export and create the tag assignments per contact during migration. Tag names with special characters are sanitized to match GoHighLevel's tag name constraints.

Spotler Mail+ lead scoring values are stored as numeric contact properties. We map these to GoHighLevel custom number fields on the Contact object. The field name is preserved from Spotler (for example, lead_score) and the numeric value transfers directly. If the customer uses multiple score dimensions (engagement score, demographic score, behavioral score), each maps to a separate custom field in GoHighLevel.

Spotler Mail+ custom fields support text, numeric, currency, list, date of birth, date, and permission field types. We map each type to the GoHighLevel equivalent: text to text, numeric to number, currency to number with decimal, list to dropdown or multi-select, date to date, and permission to a yes/no field. List fields require a GoHighLevel picklist to be pre-created with the same option values before migration. Permission fields (consent tracking) map to GoHighLevel's built-in SMS and email consent fields where applicable.

Spotler Mail+ segmentation rules (selections, exclusions, behavioral conditions) do not export as executable logic. We extract the resulting contact set for each named segmentation and create GoHighLevel Contact Lists or Tags representing that membership. For example, if Spotler has a segment 'High-Value Engaged Contacts' containing 2,300 contacts, we create a corresponding GoHighLevel Tag or List and populate it with those contacts. The segmentation rule itself must be recreated as a GoHighLevel Workflow or filter-based Smart List.

Spotler Mail+ form submissions export as flat records linked to contacts by email. Each form submission is a set of question-response pairs. We denormalize these into Contact custom fields (if the form has a fixed set of fields) or into Contact Notes (if the form has open-ended questions). Survey closure rules and quota-triggered responses do not export and are documented separately for manual rebuild. If the customer has more than 50 form types, we recommend using Notes with a consistent prefix per form rather than creating one custom field per form question.

Spotler Mail+ opens, clicks, delivery stats, and conversion data within the 24-month window export as CSV from the analytics dashboard. We map this to GoHighLevel Contact Activity records. Note that Spotler anonymizes interaction data after 24 months, so records older than the 24-month window will return empty in any export query regardless of method. We scope the mailing history migration to the most recent 24 months and flag any reporting gap to the customer before migration begins. Engagement timestamps are preserved in the activity record date.

Spotler Mail+ User accounts (name, email, role) map to GoHighLevel Users. We extract user records for the migration admin and reporting context, but GoHighLevel user provisioning happens in the destination account directly. We document the Spotler role assignments so that the customer's admin can map them to GoHighLevel's permission model post-migration.