Migrate from Spotler Mail+ to monday CRM

Spotler Mail+ contacts map to Monday.com CRM people items. Standard fields (email, first name, last name, phone, address) map to typed columns in the Contacts board. We apply Monday's email column validation on import. Custom fields of type text, numeric, currency, list, and date migrate to Monday custom columns of equivalent type. The Spotler contact ID is stored in a custom text column for audit traceability and to support reconciliation against the source export.

Spotler tags (multi-value contact attributes) map to Monday CRM multi-select columns on the Contacts board. Each unique tag becomes a selectable option in the Monday column. Where the customer's tag taxonomy is complex (over 100 unique tags), we discuss using Monday labels as an alternative labelling layer to keep the column UI clean. The tag-to-column mapping is documented in the migration spec for the customer's admin to validate post-migration.

Spotler lead scoring values stored as numeric contact properties map directly to Monday CRM number columns on the Contacts board. Score thresholds that the customer uses to define lead quality tiers are preserved as reference data in a custom text column documenting the scoring model, so the admin can rebuild segmentation logic in Monday automations post-migration.

Spotler Mail+ list fields (single-selection contact properties with predefined options) map to Monday CRM Status columns or Dropdown columns depending on whether the list represents a workflow stage or a classification. We match the option labels exactly and flag any Spotler list values that do not have a Monday column equivalent. Multi-select list fields map to Monday multi-select columns.

Spotler Mail+ date fields (date of birth, custom date properties) map to Monday CRM Date columns. We preserve the date value and timezone where present. Date fields with no value export as empty in Spotler and remain empty in Monday; we flag these as requiring manual population post-migration if they are required columns in the target board.

Spotler audience segmentations (named contact sets built from selections, exclusions, and behavioral filters) do not have a direct Monday CRM equivalent. We create Monday custom objects (via the Monday developer API) representing each Spotler segmentation with a name, description, rule summary, and member count. The contact-to-segment membership is stored as a custom object relationship or as multi-select tag columns on the contact item, depending on the customer's preferred segmentation UI in Monday. The segmentation rule logic itself is documented in the migration spec for manual rebuild.

Spotler Mail+ form submissions and survey responses export as flat records linked to contacts, with the question-response structure denormalised. We create Monday custom objects for each form, storing field names and responses as sub-items or related records attached to the originating contact item. Survey closure rules (date-triggered or quota-triggered) do not export from Spotler and are documented for the customer's admin to rebuild as Monday form integrations or automation triggers.

Spotler mailing campaign records (subject, send date, sender name, send volume) can be exported and mapped to Monday CRM custom objects linked to contacts via a custom relationship column. Click and open rates are available from Spotler exports within the 24-month window; post-24-month interaction data is anonymised and cannot be recovered. We scope the mailing history migration to the 24-month pre-anonymisation window and flag this boundary explicitly before migration begins. Email content and template bodies are exported as HTML assets for manual reassembly in the customer's chosen email tool.

Spotler Mail+ user accounts (names, emails, role assignments) are extracted for mapping to Monday.com team members. Role definitions from Spotler (admin, editor, viewer) map to Monday's permission levels within the workspace. We resolve users by email match and flag any Spotler users without a corresponding Monday.com account for the customer's admin to provision before record migration.

Spotler Mail+ workflow automations (triggers, drip sequences, behavioral campaign actions) are platform-native and cannot be exported as executable rules. We deliver a written inventory of every active Spotler automation including its trigger, conditions, actions, and target audience, with a recommended Monday.com automation equivalent documented for each. The customer's admin rebuilds these in Monday's automation builder post-migration.