Migrate from SmartDesk to Pipedrive

SmartDesk Leads map directly to Pipedrive Leads. Lead Source and Lead Status stored as custom fields in SmartDesk map to Pipedrive custom fields that must be pre-created before migration. Early-stage prospects with no qualification data remain as Pipedrive Leads and can be converted to Persons and Deals when the customer qualifies them. We preserve the original Lead creation date and owner email for audit.

SmartDesk Contacts map to Pipedrive Persons. Name, email, phone, address, and lifecycle stage migrate directly. Custom contact properties migrate to Pipedrive custom fields on the Person object. SmartDesk lifecycle stage is preserved in a custom field sd_original_lifecycle__c. Persons are linked to Organizations after the Organization import completes.

SmartDesk Accounts (or Companies) map 1:1 to Pipedrive Organizations. Industry classification, employee count, website, and any custom account properties migrate as custom fields. We create Organizations first in the migration sequence so that the Organization lookup on Persons is satisfied at insert time. Domain-based deduplication logic applies to prevent duplicate Organizations.

SmartDesk Deals map directly to Pipedrive Deals. Deal name, value, expected close date, and owner migrate. Pipeline and stage assignment requires a reconciliation pass: SmartDesk allows fully custom stage names with no standard set, so we enumerate the SmartDesk pipeline stages and map each to a corresponding Pipedrive pipeline stage by name or sequence. If no matching stage exists, we create the stage in Pipedrive before import and flag the mapping for customer review.

SmartDesk Pipelines map to Pipedrive Pipelines. Each SmartDesk Pipeline becomes a Pipedrive Pipeline with its stages created in the same sequence order. Stage probability values migrate to Pipedrive stage probability fields. Pipedrive's pipeline model allows multiple pipelines per account, matching SmartDesk's multi-pipeline capability, but the stage structure must be explicitly mapped rather than auto-created.

SmartDesk Tasks map to Pipedrive Activities. Assignee, due date, status, description, and linkage to the parent Contact or Deal preserve through the migration. We resolve SmartDesk task owners by email match against Pipedrive users before inserting. Tasks with no assignee default to the migration user and are flagged for reassignment review post-migration.

SmartDesk Activity records (calls, emails, meetings, notes logged against Contacts or Deals) map to Pipedrive Activity records of the corresponding type. Activity type, timestamp, body content, and related contact or deal linkage migrate. Some activity metadata stored in SmartDesk custom fields may require pre-created Pipedrive custom fields to capture fully. Historical activity volume can be significant; we chunk large activity sets into batches of 1,000 records per API call.

SmartDesk Users and Owners map to Pipedrive Users by email address. We extract every distinct owner referenced across Leads, Contacts, Accounts, Deals, and Activities and match by email. Any SmartDesk owner without a corresponding Pipedrive user is held in a reconciliation queue for the customer to provision before record import resumes. This step gates the entire migration; no records import until owner resolution is complete.

SmartDesk Unlimited Custom Fields migrate to Pipedrive custom fields on the corresponding objects (Leads, Persons, Organizations, Deals). Pipedrive requires custom fields to be pre-created in the destination account before data can be written to them via API. We provide a custom field manifest listing every source custom field name, object, and data type so the customer can configure destination fields before migration begins. Field type mapping applies: SmartDesk text fields map to Pipedrive text, SmartDesk numeric fields to Pipedrive numeric, SmartDesk date fields to Pipedrive date.

File attachments associated with Contacts, Accounts, Deals, or Tasks in SmartDesk are downloaded, validated by file type, and re-uploaded to Pipedrive as linked files. We preserve original filenames and attach each file to the corresponding record in Pipedrive via the file upload API. Very large files (over 50 MB) are flagged for the customer to host externally and provide a URL reference instead.