Migrate from LeadTrac to Pipedrive

LeadTrac leads map 1:1 to Pipedrive People. The primary contact fields (name, email, phone) transfer directly. LeadTrac lead status values are preserved as a custom field since Pipedrive People have no native status attribute — your team decides whether to use Pipedrive's Leads Inbox for unworked records instead.

LeadTrac clients represent business entities and map to Pipedrive Organizations. The company name, domain, address, and industry fields transfer as-is. When a LeadTrac lead has an associated client record, the Person record in Pipedrive links to the Organization via the org_id field after Organizations are migrated first.

LeadTrac does not have a native Deal object — instead it tracks engagement progress on leads. We infer a Pipedrive Deal from any LeadTrac lead with a status value indicating active pursuit (proposal sent, negotiation, etc.). The Deal is created with the associated Person as the primary contact and the linked Organization if one exists.

LeadTrac appointments map to Pipedrive Activities with type set to 'meeting'. The original scheduled date, time, duration, and attendee list transfer as activity fields. The activity links to the associated Person or Organization record in Pipedrive. We exclude cancelled or no-show appointments unless you specifically request them.

LeadTrac call logs migrate as Pipedrive Activities with type 'call'. The call direction (inbound/outbound), duration, and outcome fields map to Pipedrive's subfields. Owner is resolved by email match to a Pipedrive user. Call recordings stored in LeadTrac are not transferred — that requires a separate media migration step.

Email logs from LeadTrac become Pipedrive Activities with type 'email'. Subject line, body content, and timestamp transfer as activity details. Pipedrive does not sync email threads natively on Lite plans — you may need the email sync integration on Growth or above for ongoing email tracking post-migration.

LeadTrac notes attached to leads or clients become Pipedrive Notes. The note body and its original create timestamp transfer directly, preserving the author and timing of each entry. When a single LeadTrac note references multiple records, we create separate Note objects in Pipedrive, each linked to the corresponding Person or Organization record.

LeadTrac campaigns are source-tracking tags attached to leads. Pipedrive lacks a native Campaign object comparable to HubSpot or Salesforce, so we preserve campaign attribution as a custom field named 'Lead_Source_Campaign__c' on Person records. This field stores the original campaign name, enabling reporting, segmentation, and list targeting in Pipedrive's analytics tools.

LeadTrac stores completed agreements and populated PDFs. These re-upload to Pipedrive as Files attached to the Person or Organization record they were associated with in LeadTrac. DocuSign envelope metadata (envelope ID, status, signed date) saves as a custom field since Pipedrive does not expose DocuSign envelope objects natively.

LeadTrac owner email addresses are matched against Pipedrive users by email. Unmatched owners are flagged before migration — your team either creates the Pipedrive user first or assigns their records to a fallback owner. No record lands without a Pipedrive owner.

LeadTrac custom properties on leads become Pipedrive custom fields on Person. Each custom property gets a hash-keyed field in Pipedrive — we create the field during migration setup and store values against the generated key. Pick-list values in LeadTrac map to Pipedrive options in the corresponding field type.

LeadTrac custom properties on clients migrate as Pipedrive custom fields on Organization. The same hash-key creation workflow applies: we create each field in Pipedrive using the LeadTrac property name as the label, set the appropriate type (date, number, text, pick-list, or multi-select), and write values against the generated hash key. Multi-select pick-lists become multi-option fields, preserving all selected options.