Migrate from SalezShark to Pipedrive

SalezShark Lead records map directly to Pipedrive Lead. The lead status, source, owner assignment, and auto-assignment rules from SalezShark migrate as custom fields on the Pipedrive Lead (lead_status_raw, conversion_score). SalezShark's Lead conversion process creates a Contact-Account-Opportunity chain; we preserve the original Lead record as a Pipedrive Lead with a custom field linked_to_account__c for audit traceability rather than auto-converting at migration time, giving the customer's team control over when conversion happens.

SalezShark Contact records map to Pipedrive Person (the contact object). The email, phone, address, and name fields map to Pipedrive's standard Person fields. Custom fields on the Contact (available on SalezShark Basic+) map to custom fields on Pipedrive Person, which we pre-create before the import phase. SalezShark's built-in enrichment data (company email format, employee headcount) migrates as read-only custom fields with a provenance note so the team knows these were enriched in SalezShark and may need re-verification.

SalezShark Account records map to Pipedrive Organization. The company name, website, industry, employee count, and revenue range fields map to their Pipedrive equivalents. Organization is created before any Person or Deal import because Pipedrive requires an Organization to link to a Deal, and we link Persons to Organizations via email domain match or explicit account association where available. Any Account in SalezShark without a website URL receives a placeholder Organization in Pipedrive and is flagged in the reconciliation report.

SalezShark Opportunity records map to Pipedrive Deal. Stage, deal value, close date, and owner assignment migrate directly. SalezShark pipeline stages map to Pipedrive pipeline stages, which we configure before import. The critical constraint is that every Pipedrive Deal must have an Organization; we run an organization-resolve phase before Deal import that matches each Opportunity's linked Account to a Pipedrive Organization by name, creating the Organization first if it does not exist, and flagging any Opportunity without a linked Account for the customer to resolve manually.

SalezShark's configurable Sales Pipelines migrate to Pipedrive Pipelines, with stage names, stage order, and probability percentages preserved. Pipedrive allows multiple pipelines per user and supports stage-specific actions (won/lost status, currency, rotator assignment), which we configure during the pipeline setup phase. Stage probability percentages migrate with rounding to Pipedrive's allowed probability values.

SalezShark Custom Fields available on Basic and above are extracted as a schema definition during scoping, including field name, data type, and picklist values. Each custom field is pre-created in Pipedrive under the relevant entity (Lead, Person, Organization, Deal) with the matching data type before record import. Custom fields that exist only in SalezShark are flagged as candidate fields for the customer to create in Pipedrive's field editor before migration begins. We do not assume that a SalezShark custom field of type 'text' maps directly to a Pipedrive text field without reviewing the actual data patterns.

SalezShark Task and Activity records (calls, emails, meetings, notes) map to Pipedrive Activity records with the activity type preserved (call, email, meeting, note). Status, due date, owner, and association to the relevant record (Person, Organization, Deal) migrate directly. We resolve the owner by email match against Pipedrive users. Activity records without a valid owner are flagged and held in a reconciliation queue. Note bodies migrate as Pipedrive note activities linked to the parent Person or Organization.

SalezShark User records map to Pipedrive User for owner assignment. We resolve owners by email match. Active users in SalezShark are provisioned as active users in Pipedrive before migration; inactive or archived users are mapped as inactive Pipedrive users so historical owner assignment is preserved without inflating the active seat count. Any Deal or Activity in SalezShark without a valid owner is flagged in the reconciliation report.

SalezShark Document Management files (available on Basic and above) migrate as file attachments in Pipedrive linked to the parent record (Person, Organization, or Deal). We export document metadata (file name, upload date, file size, linked record type and ID) and re-associate each file during import by matching the linked record's migration ID. Actual file content transfers through Pipedrive's file attachment API. Documents without a clear parent record linkage are bundled under the associated Organization.

SalezShark Workflow Automations (Professional tier only) store trigger-action sequences that cannot be transferred to Pipedrive's automation engine because the underlying logic models differ. We export each active automation as a written specification: trigger object, trigger conditions, filter logic, action type, and downstream target. This specification is delivered to the customer as a rebuild guide for Pipedrive Automation. Automations are not executed during migration; they are explicitly documented and handed off for the customer's admin to recreate in Pipedrive's automation builder.

SalezShark Reports and Dashboards are exported as configuration metadata preserving report filters, field selections, and date ranges. We cannot migrate report query results or regenerate reports in Pipedrive. The report configuration metadata is delivered alongside the migrated records so the customer's admin can recreate equivalent reports in Pipedrive's report builder using the migrated field names. Pipeline-specific reports are the highest priority for rebuild because pipeline stage names are preserved during migration.