Migrate from Spotler Mail+ to Pipedrive

Spotler Mail+ contacts map directly to Pipedrive People. Standard fields (name, email, phone, address) migrate 1:1. We use the email address as the dedupe key and resolve the Pipedrive Person ID for subsequent lookups from custom fields and tag assignments. Any contacts with multiple email addresses in Spotler are mapped to Pipedrive's multi-email field structure.

Spotler Mail+ contact tags map to Pipedrive Labels on the Person record. Tags are stored as comma-separated values in Spotler and are denormalized during extract. Each distinct tag value becomes a Pipedrive Label entry. Tags used for behavioral classification (product interest, lifecycle stage, source) carry meaning that Pipedrive Labels preserve for segmentation in the CRM view.

Spotler Mail+ lead scoring values stored as contact properties map to a Pipedrive custom number field (e.g., lead_score__c). Numeric scores transfer directly. We create the destination custom field before import and map the Spotler field name to the Pipedrive field API name. If Spotler uses multiple scoring dimensions (behavioural score, demographic score), each maps to a separate custom number field.

Spotler Mail+ custom fields (text, numeric, currency, list, date, permission) map to Pipedrive custom fields of matching type. Text fields map to Pipedrive text fields, numeric to number fields, currency to Pipedrive number fields with currency formatting, list fields to Pipedrive dropdown or multiselect depending on whether the Spotler field is single-select or multi-select. Permission fields migrate as boolean or dropdown depending on the value set.

Mailing interaction data within the 24-month Spotler anonymization window migrates as Pipedrive Activity records. Each sent mailing becomes a Task or Note entry on the Person record with the subject, send date, open flag, click count, and delivery status denormalized into the task body or custom fields. Records older than 24 months return empty from Spotler and are excluded from migration scope. This window constraint is communicated before scoping begins.

Spotler Mail+ form submissions export as flat records linked to contacts. We denormalize each submission into a Note on the Person record with the form name, submission date, and key field values in the note body. Survey responses with multiple questions migrate as structured note content for manual reference. Survey closure rules and quota triggers do not export and are documented separately for admin rebuild.

Spotler Mail+ segment membership (the resulting contact sets from behavioral selections, exclusions, and refinements) is extracted as the flat contact list at export time. The segmentation rules themselves do not export as executable logic. We deliver a written inventory of each segment's criteria (selection conditions, exclusion lists, refinements) so the customer can recreate equivalent Pipedrive Leads lists or filtered Person views in Pipedrive's segmentation UI.

Spotler Mail+ user accounts (name, email, role) extract for mapping to Pipedrive User records. We match by email address. Any Spotler user without a matching Pipedrive User is placed in a reconciliation queue for the customer's admin to provision before migration. Role definitions (Spotler predefined roles) map to Pipedrive permission sets, though Pipedrive's role model is not a direct 1:1 equivalent.

Email templates are platform-native assets stored in Spotler Mail+. The drag-and-drop editor layout does not export as a portable format. We extract template content as HTML/CSS text assets and image URLs for manual reassembly in Pipedrive's email template editor. This is a documented handoff item, not a data migration.

Spotler Mail+ automated campaign logic, triggers, drip sequences, and behavioural actions are platform-native and cannot be exported as executable rules. We do not migrate automations as code. We deliver a written inventory of every active Spotler workflow with its trigger, conditions, actions, and a recommended Pipedrive Automation equivalent (or a separate automation tool if the workflow scope exceeds Pipedrive's trigger options).