Migrate from Sellsation CRM to Pipedrive

Sellsation Customers are the primary account-level records, storing company name, address, industry, and revenue data linked to Contact Persons and Sales Projects. We map them 1:1 to Pipedrive Organizations, preserving the company name as organization_name, address fields as standard location fields, and any custom fields on the Customer record as Pipedrive custom organization fields. We create the Organization in Pipedrive before importing any linked Persons so that the Organization lookup is satisfied at the moment of Person insert.

Sellsation Contact Persons are individual contacts linked to a Customer with full activity history including calls, meetings, and notes. We map them 1:1 to Pipedrive Persons, preserving the linked Customer as an Organization lookup, name fields, email, phone, and any custom contact fields. Activity history is linked via the Person record after both are created in Pipedrive.

Sellsation Sales Projects are deal/opportunity records tracked through pipeline stages with automated potential analysis. We map them 1:1 to Pipedrive Deals, preserving pipeline stage names, deal values (amount), expected close dates, and phase change history as Activities. The traffic-light stagnation flag (red/yellow/green) from Sellsation does not have a Pipedrive native equivalent; we store it as a custom picklist field deal_stagnation_flag__c so the customer's Pipedrive admin can build a workflow or dashboard view around it after migration.

Sellsation's guided pipeline stages map to Pipedrive Pipeline stages. We enumerate every distinct stage name in the source CRM during scoping and create a matching Pipedrive Pipeline with those stage values in the same order. Stage probabilities migrate as stage_order weights. If the Sellsation account uses multiple pipelines, each becomes a separate Pipedrive Pipeline.

Sellsation Activities include calls, appointments, notes, and tasks attached to Contact Persons or Sales Projects. We export the full activity timeline including timestamps, user assignments, and linked records. These map to Pipedrive Activities (Activity type field distinguishes call, meeting, note, task). Activity-to-Person and Activity-to-Deal links are resolved using the Contact Person and Sales Project lookups created earlier in the migration sequence. Long-standing activity histories (10-20x contact volume) are chunked by date range to avoid import timeout.

Sellsation multi-level campaigns combine emails, letters, conditional stage movements, and automated task creation. Pipedrive Campaigns are separate records for tracking campaign-level performance metrics but do not replicate Sellsation's conditional branching or stage-movement automation. We migrate campaign enrollment data and campaign-level custom fields as Pipedrive Campaign records. The automation logic is documented in the handoff inventory for the customer's admin to rebuild using Pipedrive Workflows.

Sellsation Tasks are assigned to users with due dates and linked to Contact Persons or Sales Projects. We preserve task status (open/closed), due date, assignment, and linking during migration. Completed tasks migrate with their status; open tasks migrate as open Pipedrive Activities.

Sellsation calendar appointments with date, time, duration, and attendees are linked to Contact Persons. We export appointment records with attendee lists and any attached notes, mapping them to Pipedrive Activities of type meeting with start time, end time, and location preserved. Attendees are linked via the Person lookup in Pipedrive.

Sellsation supports custom fields on primary objects. During scoping we enumerate every custom field on Customer, Contact Person, Sales Project, and Activity records. We map each to a Pipedrive custom field of equivalent type (text, numeric, date, picklist). Picklist-type custom fields require us to pre-populate the Pipedrive picklist options with values from Sellsation before import. If Sellsation custom fields use formula dependencies or cross-object lookups, we flag these for manual review because Pipedrive custom fields do not support cross-object formulas natively.

Sellsation's geo map feature generates territory heatmaps but stores the underlying data as internal map state rather than standard geographic coordinates. We export the linked Sales Project location data as standard address fields on the corresponding Pipedrive Deal or Organization. The native heatmap visualization cannot be replicated in Pipedrive; geographic context is preserved through the address fields so the customer can use Pipedrive's map view or a third-party mapping integration post-migration.