Migrate from SalesTown CRM to Pipedrive

SalesTown Contact records map to Pipedrive People (Person object). Standard fields including name, phone, and email migrate directly. Custom properties on SalesTown Contacts map to Pipedrive custom fields on the Person object. Owner assignment migrates by resolving the SalesTown owner email to a Pipedrive User record. Contacts that represent companies rather than individuals are flagged during scoping for potential Organization merge during transform.

SalesTown Leads are the primary acquisition object and map to Pipedrive Leads. Smart distribution rules, lead scoring, and segmentation values migrate as Pipedrive custom fields on the Lead object. We run a scoping check to determine whether each SalesTown Lead should become a Pipedrive Lead or Person record based on qualification status at migration time, since Pipedrive supports both object types with different lifecycle positions.

SalesTown Company records map to Pipedrive Organizations. The Company field schema is not publicly documented in SalesTown CRM, so we inspect the CSV export during discovery, map available fields to Organization Name, address, and custom fields, and flag any unmapped fields for post-migration admin review. Organization is created before any Person import so that the Organization lookup is satisfied at Person insert.

SalesTown Deals carrying amount, stage, owner, and expected close date map directly to Pipedrive Deals. Closed-won and closed-lost reasons from SalesTown custom properties become Pipedrive Deal lost_reason fields. Owner references migrate by resolving the SalesTown user email to the Pipedrive User ID established during the user migration phase.

SalesTown Pipelines with customizable Stages map to Pipedrive Pipelines. We export pipeline names, stage order, and stage-specific win/loss flags during discovery, recreating Pipelines in Pipedrive before any Deals load. Pipedrive Pipelines are created via API during the schema setup phase so that Deals have a valid pipeline_id reference at insert time.

Pipeline Stages carry names, probabilities, and ordering in SalesTown CRM. We map stage-to-stage explicitly by name rather than by position to handle cases where source and destination pipelines have different stage counts. Stage probability percentages migrate from SalesTown to Pipedrive stage_probability values, rounding to the nearest integer allowed by Pipedrive.

SalesTown Activities including WhatsApp messages, emails, and calls map to Pipedrive Activity records. WhatsApp thread metadata including message status and timestamp sequences are stored as flattened individual rows in the SalesTown CSV export, so we reconstruct thread relationships during transform by grouping rows by contact ID and timestamp ordering. Each reconstructed message becomes a Pipedrive Activity record linked to the corresponding Person or Organization. SalesTown email activities become Activity records with type email; call activities become Activity records with type call and call_duration preserved.

SalesTown Users map to Pipedrive Users by email address match. The SalesTown user email is used as the unique identifier for owner resolution during Deal and Lead import. Email addresses must be unique at the destination to avoid duplicate user creation. We validate that all owner email addresses from SalesTown have matching Pipedrive Users before record import begins; any unmatched owners go to a reconciliation queue for admin provisioning.

SalesTown custom templates for emails and communications have no documented schema, making automated body migration unreliable. We export available template metadata including name, subject, and any visible field placeholders, flagging template body mapping as a post-migration cleanup task for the admin. The inventory is delivered as a written handoff document listing each template requiring manual recreation in Pipedrive.

SalesTown CRM reporting and dashboard definitions are stored server-side with no documented export mechanism. We migrate the underlying data so reports can be rebuilt in Pipedrive Insights, but report configurations do not migrate. The admin receives a written inventory of every SalesTown report with its data source fields listed so that the equivalent Pipedrive report can be configured post-migration.