Migrate from Link app to Pipedrive

Link App Clients map directly to Pipedrive Persons. Person.name is constructed from Client.first_name and Client.last_name. The Person.org_id link is resolved by looking up the Client.company association in the Organizations migration step. All standard contact fields (email, phone, address) transfer directly.

Link App Clients flagged as prospective clients (non-active matters) can split to Pipedrive Leads rather than Persons if the migration scope includes pre-intake leads. The split is based on a Client.status field if present, otherwise all active clients default to Person.

Link App Company records map to Pipedrive Organizations. Organization.name maps from Company.name. Address fields, industry, employee count, and website transfer directly where present. Organizations are migrated before Persons so the org_id lookup resolves correctly during Person import. If a Company has multiple branches, each branch can be represented as a separate Organization or linked via custom fields, depending on your reporting needs.

Link App Matters map to Pipedrive Deals. Matter.name becomes Deal.title, Matter.value becomes Deal.value (currency amounts transfer as-is), and Matter.status maps to the Pipedrive pipeline stage via value-mapping. Each Matter is linked to its originating Client Person via Deal.person_id. The deal's expected close date is set from Matter.open_date.

Link App matter-status labels (e.g., Intake, Active, Pending Review, Closed) map to Pipedrive pipeline stages. If Link App uses multiple pipelines, each becomes a separate Pipedrive pipeline with its own stage sequence. Stage order and probability values are preserved as custom fields if the default stage configuration differs from Link App's labels.

Link App communication logs (calls, messages, document uploads) map to Pipedrive Activities with Type set by activity kind. Original timestamps, due dates, and assigned user IDs transfer. Activities are linked to the parent Deal or Person via Pipedrive's deal_id and person_id fields.

Link App document attachments on matters are downloaded and re-uploaded to Pipedrive as file attachments linked to the corresponding Deal or Person. File size limits (Pipedrive caps at 50MB per file) are enforced; files exceeding the limit are flagged for chunked upload or alternative storage.

Link App matter notes and client notes map to Pipedrive Notes attached to the parent Person or Deal. Rich-text formatting is preserved where possible. Notes with timestamps transfer with the original create date stored in Pipedrive's created_time field. If a note references an attachment, the attachment link is maintained in the Note record.

Link App custom properties on Clients and Matters require pre-creation in Pipedrive before migration runs because Pipedrive assigns hash-based keys to custom fields. We create matching fields in Pipedrive, record the key mappings, then populate values during bulk import. Pick-list fields require value-by-value mapping where Link App options differ from Pipedrive's available values.

Link App user IDs are resolved by email match against Pipedrive Users. Unmatched owners are flagged before migration and assigned to a fallback Pipedrive user or a designated placeholder owner. Pipedrive requires at least one active user to own records — blank ownership is not permitted.

Link App communication templates are a configuration-layer construct without a Pipedrive equivalent. We export template definitions as JSON for your team to reference when rebuilding in Pipedrive Email Templates or Sequences. This is disclosed honestly as a limitation of the migration scope.

Link App workflow rules and automation triggers have no direct Pipedrive equivalent. Pipedrive Automations and Sequences use a different trigger-action model. We export workflow definitions as a rebuild reference document; the migration itself covers data only. Your team can use this export to recreate rules in Pipedrive Automations or third-party tools.