Migrate from FastTrack to Pipedrive

FastTrack Person records map directly to Pipedrive People. The Person's primary company link resolves to a Pipedrive Organization lookup — if no matching Organization exists, FlitStack creates a placeholder or maps to a configurable default. Custom properties on Person migrate to Pipedrive custom fields on the Person entity.

FastTrack Company maps to Pipedrive Organization. Parent-company hierarchies in FastTrack translate to the Parent Organization field in Pipedrive. FastTrack company domains, industry classifications, employee counts, and annual revenue map to equivalent Pipedrive Organization fields. Custom company properties migrate as custom fields on the Organization.

FastTrack Deal records map to Pipedrive Deals with stage, value, expected close date, and owner preserved. Pipedrive requires Deals to be associated with a Pipeline — FlitStack maps FastTrack pipeline assignment to a corresponding Pipedrive Pipeline (creating it if absent). Stage names translate via a value-mapping table per pipeline.

FastTrack Pipeline maps 1:1 to Pipedrive Pipeline. Each FastTrack pipeline stage becomes a Pipedrive stage within the mapped pipeline. Stage order, probability, and rotten days settings transfer. Pipedrive's per-stage probability replaces FastTrack's optional probability field if present. Stage names and ordering are preserved to maintain consistent pipeline visualization in Pipedrive's Kanban view.

FastTrack call activities map to Pipedrive Activities with type='call'. Original call duration, outcome, and owner attribution preserve as activity metadata. Call subjects and notes attach to the parent Person or Deal record in Pipedrive. The marked-as-done status reflects FastTrack's call completion state. Call direction (inbound/outbound) maps via a custom field if tracked in FastTrack.

FastTrack email activities map to Pipedrive Activities with type='email'. Email subjects, bodies, and timestamps preserve. Pipedrive stores email body as text — HTML email content from FastTrack gets stripped to plain text during migration. Email attachments migrate separately as Pipedrive Files attached to the activity record.

FastTrack meeting activities map to Pipedrive Activities with type='meeting'. Original start/end timestamps, location, and meeting title transfer. FlitStack associates meeting activities with the relevant Person and Deal records based on FastTrack's association data. Meeting participants from FastTrack create Person-Activity links in Pipedrive.

FastTrack notes migrate as Pipedrive Notes attached to the relevant entity (Person, Organization, or Deal). Rich-text formatting in FastTrack notes converts to Pipedrive's plain-text note format. Note create dates preserve as Pipedrive's creation timestamp. Any embedded file references in FastTrack notes create Pipedrive file attachments on the same parent entity.

FastTrack products map to Pipedrive Products with name, code, unit price, and description. Product images and file attachments re-upload to Pipedrive Files. Pipedrive Products can be linked to Deals via deal products — FlitStack reconstructs this linkage from FastTrack's deal-product associations.

FastTrack custom objects with their own fields map to Pipedrive Products or become custom field sets on existing entities depending on structure. Pipedrive has no native custom object equivalent to Salesforce or HubSpot — FlitStack maps FastTrack custom object records to Pipedrive Products plus custom fields, or flags for manual decision where no clean mapping exists.

FastTrack user records resolve to Pipedrive users by email address match. FlitStack builds a user lookup table before migration. Unmatched FastTrack owners get flagged — you can assign them to a fallback Pipedrive user or invite them before the migration runs.

FastTrack file attachments on records re-upload to Pipedrive Files attached to the same parent entity. Pipedrive enforces file size limits per plan tier (typically 250MB per file on higher plans). FlitStack logs files that exceed Pipedrive's size threshold for manual retrieval and creates a manifest of oversized files with their source record references.