Migrate from Spotler Mail+ to HubSpot

Spotler contacts map 1:1 to HubSpot contacts. Standard fields (firstname, lastname, email, phone, jobtitle, address) move directly. Custom Spotler contact properties migrate as HubSpot custom properties. Contacts without an email address are flagged for review before migration — HubSpot requires an email for most automation triggers.

Spotler tags are stored as comma‑separated strings on each contact record. We map each distinct tag to a HubSpot custom property of Text type, preserving the original tag list. Optionally, we generate HubSpot static lists for each tag value, allowing segmentation logic to be applied using HubSpot's native list model without needing to parse raw tag text.

Spotler contact scoring migrates as a custom Number property on the HubSpot contact. If your team uses HubSpot's native lead scoring, we map Spotler scores into that field. If Spotler uses multiple score dimensions, each maps to a separate HubSpot custom property.

Spotler subscription statuses (subscribed, unsubscribed, pending, bounced) map directly to HubSpot subscription type values for each contact. The value mapping preserves the opt‑in/opt‑out state and the exact timestamp of the last status change, ensuring HubSpot respects unsubscribe preferences in outbound email campaigns. Pending and bounced states are also carried over as separate subscription type options to maintain accurate contact communication rights.

Spotler tracks opens, clicks, and bounces per contact per mailing. We store aggregate counts as custom number properties on the HubSpot contact (e.g., Total_Emails_Opened__c, Total_Clicks__c). If granular per-mailing history is critical, individual sends can be created as HubSpot engagement records with the mailing name, date, and outcome as properties.

Spotler companies map 1:1 to HubSpot companies, moving standard fields such as name, domain, industry, phone, address, employee count, and annual revenue directly. Spotler custom company fields are migrated as HubSpot custom properties on the Company object, type‑aligned (text, number, date, checkbox, dropdown). Required HubSpot properties are provisioned in advance so foreign‑key lookups and associations resolve correctly during the migration run.

Spotler links a contact to one primary company. This maps to HubSpot's contact-company association. HubSpot natively supports associating a contact with multiple companies via the 'associated company' property and the Company Contacts relationship — we set the Spotler primary company as the HubSpot primary association.

Spotler form submissions store field values and timestamps. We map submissions to HubSpot contacts with the form field data recorded as contact properties. If Spotler forms correspond to HubSpot forms, we create HubSpot forms and link submissions to the correct form ID — otherwise, submission data is preserved as custom contact properties.

Spotler audience segments (selections) are named groups with filter rules. We create HubSpot lists and populate them based on Spotler contact field values or tags that define membership. Dynamic list logic (Spotler's filter conditions) must be rebuilt in HubSpot's list filter builder — we provide a Spotler audience definition export as a rebuild reference.

Spotler owner IDs resolve to HubSpot users by email address match. We generate a pre-flight owner resolution report before migration — any Spotler owner without a corresponding HubSpot user is flagged for your team to either invite them to HubSpot or assign their records to a fallback owner.

Any Spotler custom contact or company fields migrate as HubSpot custom properties. We map the Spotler field type (text, number, date, checkbox, dropdown) to the corresponding HubSpot property type. Spotler dropdown values map as HubSpot dropdown option values. Required HubSpot properties are created before migration so foreign-key lookups resolve correctly.

Spotler workflows, automation rules, and email sequences do not transfer to HubSpot. HubSpot's automation model (Workflows, Sequences, Playbooks) must be rebuilt. We export Spotler workflow definitions with triggers, conditions, and actions as a structured reference document for your HubSpot admin.