Migrate from Spotler CRM to Pipedrive

Spotler CRM Contacts map directly to Pipedrive Persons. Email address serves as the primary dedupe key. Standard fields (name, email, phone, address) migrate 1:1. Custom properties on the Contact record migrate to custom fields on the Person; we create these fields in Pipedrive Settings with matching types (text, numeric, date, dropdown) before the import batch runs. Spotler contact owner resolves to Pipedrive user by email match.

Spotler CRM Companies map to Pipedrive Organizations. Company name becomes the Organization name field. Domain, industry, size, and address fields migrate 1:1. We export Company records first and import them before Persons so that the Organization ID exists at the time of Person insert. If a Spotler Contact has no linked Company, we create a placeholder Organization to preserve the Person record without breaking Pipedrive's relationship model.

Spotler CRM Opportunities map to Pipedrive Deals. The Spotler pipeline stage name maps to a Pipedrive stage name within a designated Pipeline. We collect all Spotler pipeline and stage names during scoping and pre-create matching Pipedrive Pipelines and Stages before migration. Deal value, expected close date, and owner migrate directly. Spotler custom Opportunity fields become Pipedrive Deal custom fields created beforehand.

Each Spotler CRM pipeline with its stage names becomes a Pipedrive Pipeline with named Stages. Stage probability percentages from Spotler migrate to Pipedrive Stage probability values. If Spotler uses weighted deal values based on stage probability, we preserve these in a custom field during migration rather than overwriting Pipedrive's default stage weighting.

Spotler CRM task activities map to Pipedrive Activities with type set to task. Subject, description, due date, completed status, and assigned owner migrate. Activity is linked to the target Person, Organization, or Deal by resolving the Spotler activity's related record ID against the migrated record's new Pipedrive ID at migration time.

Spotler CRM call activities map to Pipedrive Activities with type set to call. Duration, call outcome, notes, and timestamp migrate. The activity is linked to the Person or Deal record. Call recording URLs stored in Spotler custom fields migrate as text fields on the Pipedrive Activity; Pipedrive does not host call recordings natively, so the URL remains a reference rather than an embedded file.

Spotler CRM meeting activities map to Pipedrive Activities with type set by meeting or calendar depending on Pipedrive API type. Title, start time, end time, location, attendees, and description migrate. Attendee emails resolve against migrated Person records; any unresolved attendees are noted in the migration report for manual review.

Spotler CRM note activities map to Pipedrive Activity records with type set to note, or to the Note object depending on which preserves more context. We prefer Activity when the note is tied to a Deal or Person timeline, preserving the chronological view. Content, author, and timestamp migrate. If the Spotler note contains rich formatting, we preserve it as HTML within the activity content field.

Spotler CRM custom fields on Contacts, Companies, and Opportunities are exported alongside field definitions. We pre-create each custom field in Pipedrive Settings before any data import, matching the field type (text, number, date, dropdown, user picker, Organisation picker). Dropdown values from Spotler are exported as a separate values table and re-created as option sets in Pipedrive. Any Spotler field without a Pipedrive equivalent is flagged during scoping for explicit customer decision.

Spotler CRM users (name, email, role) map to Pipedrive users. We match by email address during migration. Any Spotler user without a matching Pipedrive user is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Spotler users are mapped to inactive Pipedrive users so that historical ownership data is preserved.

Spotler CRM tags on Contacts migrate as Pipedrive Person Tags. We export tag names per contact and recreate them as tags in Pipedrive during import. Tags on Companies migrate as Organization Tags. Spotler static lists are not a native Pipedrive object; we map list membership to a tag pattern and note this as a configuration decision during scoping.