Migrate from Spin CRM to Pipedrive

Spin CRM Leads map directly to Pipedrive Leads. Standard fields (name, email, phone, status, owner) map to their Pipedrive equivalents. The Spin CRM lead status property maps to Pipedrive's lead_status field. Any custom fields discovered at export are flagged and re-exported if column headers are missing from the initial CSV.

Spin CRM Contacts map to Pipedrive Person records. Email serves as the primary dedupe key. The company_name field in Spin CRM is cross-referenced against the Companies export to resolve the org_id lookup in Pipedrive before Contact import begins.

Spin CRM Company records map to Pipedrive Organization. We export Companies first and resolve the Organization ID before importing Contacts so that the org_id lookup is satisfied at insert time. Company address, industry, and custom properties migrate as Organization custom fields.

Spin CRM Deals map to Pipedrive Deals with stage mapped from the source dealstage property to the corresponding Pipedrive stage name. Deal value, expected close date, owner, and linked Contact and Company references migrate directly. The Spin CRM pipeline is fully customizable, so we capture the full stage sequence during scoping and replicate it in Pipedrive before Deal import.

Spin CRM's customizable stage sequence becomes a Pipedrive Pipeline. We extract the complete list of stages (name, order, probability if set) from Spin CRM during scoping and configure the matching Pipeline and stage values in Pipedrive via the pipeline API or UI before Deals are imported.

Spin CRM custom fields on Leads, Contacts, and Deals are not automatically provisioned in Pipedrive. We identify every custom field from the CSV column headers and from customer-provided documentation, then pre-create the matching Pipedrive custom fields (with correct type: text, number, date, dropdown, checkbox) before the import phase begins. Fields are created via Pipedrive's field management UI or API.

Spin CRM owner references on Leads, Contacts, Companies, and Deals are resolved by email match against Pipedrive User records. Any Spin CRM owner without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Spin CRM task and calendar records migrate to Pipedrive Activity objects. Call, meeting, and task subtypes map to the corresponding Pipedrive Activity type values. Activity timestamps are preserved as the activity_date in Pipedrive to maintain the chronological timeline. Email content migrates to Pipedrive Activity records linked to the Person or Deal.

Spin CRM notes migrate to Pipedrive Note records attached to the parent Person, Organization, or Deal via the foreign_key and foreign_type fields. Note body content migrates as plain text. Notes are imported after their parent records exist to satisfy the lookup relationship.

Spin CRM forecast data is derived from deal values and stage-level probability percentages. We extract the deal value and stage assignment from Spin CRM and set the matching probability in Pipedrive per stage during pipeline configuration. No separate forecast object migrates; the Pipedrive pipeline stage probabilities reproduce the Spin CRM forecast model.