Migrate from Saleshiker to Pipedrive

Saleshiker Leads map directly to Pipedrive Person records. We preserve first name, last name, email, phone, lead status, source attribution, owner assignment, and all custom properties. Lifecycle stage values from Saleshiker's lead object map to Pipedrive's person state fields via a customer-confirmed value mapping table at import time.

Saleshiker Contacts map to Pipedrive Person records with the same field preservation as Leads. If a customer has both Lead and Contact records representing the same individual, we deduplicate by email during the transform phase and merge into a single Person record with activity history combined.

Saleshiker Organizations map to Pipedrive Organizations. We preserve company name, domain, address fields, industry, employee count, and owner. Organization is created before Person import so that the Pipedrive organization_id lookup relationship is satisfied at the moment of Person insert.

Saleshiker Deals map to Pipedrive Deals. The deal title, value, expected close date, owner, and stage migrate directly. Pipeline stages in Saleshiker map to Pipedrive pipeline stage labels via a customer-confirmed mapping table before import. Closed-Lost and Closed-Won status from Saleshiker carry over as Pipedrive stage states.

Saleshiker's pipeline structure (named pipelines with ordered stages) maps to Pipedrive Pipelines. We create the target Pipedrive pipeline and configure each stage label to match the equivalent Saleshiker stage. Stage ordering and probability values are preserved per the customer's stage matrix. Multiple Saleshiker pipelines create multiple Pipedrive pipelines if the Pipedrive plan supports it.

Saleshiker Products (name, SKU, price, description) map to Pipedrive Products. The SKU maps to the Pipedrive product code field. Standard pricing migrates to the Pipedrive list price; if the customer uses custom pricing per deal, that is handled as line item configuration in the Deal mapping.

Saleshiker Quotes with line items split into a Pipedrive Deal header with associated Product entries. Quote status (Draft, Sent, Accepted, Rejected) maps to Pipedrive deal stage or a custom deal status field. If Pipedrive's optional Products in Deals feature is not enabled, we store quote line items as a custom text field in the Deal record with a structured inventory document.

Saleshiker Invoices migrate as Deal records with invoice header data (invoice number, issue date, due date, totals) and line items stored in a custom field structure. Payment status (Paid, Unpaid, Overdue, AR/AP flags) maps to custom fields on the Deal since Pipedrive Essential does not have a native Accounts Receivable module. Full AR/AP accounting state does not migrate as it depends on Saleshiker's internal ledger.

Saleshiker Tasks (title, due date, status, assignee, related-to linkage) map to Pipedrive Activities. We preserve the due date, assignee, title, and the related-to record linkage (Person, Organization, or Deal). Task completion status maps to Pipedrive Activity done flag. Sub-tasks within Saleshiker migrate as individual Activity records linked to a parent Activity.

Saleshiker Events (title, start/end datetime, type, assignee, recurrence patterns if applicable) map to Pipedrive Activities with type set to Meeting. Location and attendee information migrate to the Pipedrive Activity description or custom fields. Recurring event patterns are documented as a single Activity migration entry with the recurrence schedule noted in the handoff inventory for manual Pipedrive setup.

Saleshiker file attachments stored per record (Lead, Contact, Organization, Deal) are downloaded from Saleshiker's storage and re-uploaded to Pipedrive's file management. File metadata (name, type, size, upload date) is preserved. The Pipedrive file is linked to the target record (Person, Organization, or Deal) via the file's linked_persons, linked_organizations, or linked_deals fields.

Saleshiker Email Campaign records (template name, send date, open/click statistics) migrate as Activity records with a descriptive note containing the campaign name, send date, and summary engagement stats. Detailed engagement logs (individual open events, click events) do not migrate as Pipedrive does not store per-contact email engagement history at that granularity; we deliver a campaign stats summary document.