Migrate from SalesSeek to Pipedrive

SalesSeek Organizations map directly to Pipedrive Organizations with a 1:1 field transfer. The organization's name, address fields (street, city, region, country, postal_code), phone, website, industry, and custom properties migrate to the corresponding Pipedrive Organization fields. The SalesSeek organization ID is preserved in a custom field ss_original_id__c for audit and cross-referencing. Organization is created before any Person import so that the Organization-Person link is satisfied at the moment of Person insert.

SalesSeek People map to Pipedrive Persons. Name, email, phone, title, lifecycle stage, and owner assignment transfer directly. The Person-Organization linkage migrates by resolving the SalesSeek person's linked organization_id to the destination Pipedrive Organization ID. Any Person without a linked Organization defaults to a reconciliation queue for the customer's admin to attach post-migration. Email serves as the dedupe key during import.

SalesSeek Deals map to Pipedrive Deals with deal name, monetary value (formatted as integer or decimal depending on SalesSeek field type), expected close date, stage, and probability preserved. The linked Organization and Person references resolve to their destination Pipedrive IDs at migration time. Deal status (open, won, lost) maps to Pipedrive's status field. Custom fields on Deals migrate as custom fields on the Pipedrive Deal object.

SalesSeek pipeline stages are configurable enumerations with labels, sequence order, and probability percentages. We export the stage definition including stage order, label text, and probability value, then configure the corresponding Pipedrive pipeline stages with matching labels and probabilities before Deal import. Pipedrive stage probability defaults to 0% for new stages so explicit migration of the probability value prevents misleading pipeline forecasting in the first weeks after cutover.

SalesSeek supports multiple pipeline visualizations with different stage sets per pipeline. Each SalesSeek pipeline maps to a separate Pipedrive Pipeline. We configure Pipedrive pipelines with the matching stage sequence before Deal migration so that each Deal lands in the correct pipeline and stage. Pipedrive's per-pipeline settings (default currency, weighted probability calculation, Actor filter) are set during configuration to match the original SalesSeek behavior.

SalesSeek custom fields on Organizations, People, and Deals can be text, number, date, or dropdown types. Text, number, and date fields map to Pipedrive custom fields of the equivalent type. Dropdown fields (SalesSeek enumerated options) require explicit mapping: each SalesSeek dropdown option value is mapped to a corresponding Pipedrive add_option value before the field is created in Pipedrive. We generate a custom field mapping spreadsheet during scoping that lists each field name, type, and options for customer review before migration begins. Any dropdown with unmapped options results in a validation error rather than silent data loss.

SalesSeek Groups are collections of records used for filtering and sharing. Groups map to Pipedrive Lists, which support static membership (manual add/remove) and dynamic filters. We export group membership by querying all records that belong to each Group and re-create the membership as Pipedrive List entries. Lists are created before record import so that the List-Person and List-Organization links can be established during the bulk import phase.

SalesSeek's Filter system segments records into saved views. The API does not support updating or deleting filters — only creating new ones — and filters not associated with a Group are periodically cleaned up by the platform. We identify all active filters during scoping and export their criteria definitions. Each filter is recreated as a Pipedrive saved filter with equivalent filter conditions. Note: any SalesSeek filters that were already orphaned from a Group before migration scoping may have been deleted by SalesSeek's cleanup process; we document this gap in the filter inventory delivered to the customer.

SalesSeek Tasks represent to-do items assigned to users with due dates, status, and description. They map to Pipedrive Activities of type task. We export completed and open tasks, map the task title to the Pipedrive activity subject, the due date to the Pipedrive due_date field, and the assignee to the Pipedrive user_id by resolving the SalesSeek owner's email to the destination Pipedrive user. The activity is linked to the associated Person, Organization, or Deal via the Pipedrive deal_id and person_id references.

SalesSeek tracks engagement activities including calls, meetings, and notes. We export activity records with type, date, associated contacts, and content. The activity schema differs between platforms so we apply type-based mapping: call activities become Pipedrive Activities of type call, meetings become type meeting, and freeform text entries become Pipedrive Notes linked to the parent record. The original activity timestamp is preserved as the Pipedrive due_date or active_time field for timeline ordering.

File attachments associated with SalesSeek Organizations, People, or Deals can be exported by downloading from the source and re-uploading to the destination. We preserve the linked record association by recording the original SalesSeek record ID and type alongside the file URL, then re-attach the file to the corresponding Pipedrive record using the destination API. Pipedrive's attachment API supports adding files to Persons, Organizations, Deals, and Activities. Note: attachments stored outside SalesSeek (e.g., in linked external storage) require the customer to provide access during the migration window.

SalesSeek Tags label records for categorization. Tags export as a list of tag names per record. We import them as Pipedrive Labels, which apply to Persons, Organizations, Deals, and Activities. The tag name becomes the label name in Pipedrive. No transformation is required beyond character encoding normalization if special characters were used in SalesSeek tag names.

SalesSeek users who own records must map to Pipedrive users. We resolve owners by email match against the destination Pipedrive user table. Any SalesSeek Owner without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Unassigned records default to a migration owner designated during scoping. Pipedrive's API returns a 403 if the migration attempts to set an OwnerId to a user who does not exist, so user provisioning must complete before Deal and Person imports begin.