Migrate from Capsule CRM to Pipedrive

Capsule Party records with type=person map directly to Pipedrive Person. We resolve the Party's associated Organisation (if any) and write the Person-Organization link using Pipedrive's org_id field after Organisation records are created. The Capsule party name splits into first_name and last_name using whitespace detection; single-word names land in last_name with first_name left blank. Email, phone, website, address, and timezone fields map 1:1 to their Pipedrive equivalents.

Capsule Party records with type=organisation map to Pipedrive Organization. Organisation name becomes the Pipedrive name field. Address, phone, website, and industry fields map 1:1. We create Organisation records before Person records so that the org_id link is resolved at the time of Person insert, avoiding orphaned Person records without an Organisation reference.

Capsule Opportunities map to Pipedrive Deals with pipeline name mapped to Pipedrive pipeline and stage name mapped to Pipedrive stage. Expected close date, currency, value, probability (if set), owner, and notes migrate directly. Capsule's opportunity_background field migrates as a Pipedrive Deal note. If the Capsule Opportunity has a linked Party, we resolve the Person or Organisation ID and write the deal_id-person_id or deal_id-org_id link after Person and Organisation creation is complete.

Each Capsule pipeline becomes a Pipedrive pipeline with its stages carried forward as Pipedrive stages. Stage probability percentages migrate from Capsule to Pipedrive stage probability. If Capsule's pipeline has more than three stages, we create all stages in Pipedrive; the customer configures stage colours and ordering post-migration. Stage probability is written as an integer percentage in Pipedrive's stage definition.

Capsule Cases migrate to Pipedrive Tickets if the destination Pipedrive account has the Tickets feature enabled (Advanced plan and above). Case status, priority, assignee, and description map to Ticket status, priority, assignee, and subject. Case Kase_category and Kase_resolution migrate as custom fields in Pipedrive. If the destination Pipedrive account does not include the Tickets feature, Cases are migrated as Deals with a custom Case-type flag field to preserve the data without requiring a plan upgrade.

Capsule Project objects have no direct Pipedrive equivalent. Project name migrates as a Pipedrive Deal name with project_type flag, and Project milestones become Pipedrive Tasks linked to the Deal via the deal_id field. Project due dates map to task due_date; milestone completion status maps to task_status. Project-level custom fields migrate as Deal custom fields. The customer should confirm during scoping whether Projects represent sales milestones (suitable for Deal-Task flattening) or delivery milestones (which require a separate project management tool post-migration).

Capsule's custom fields are created via a data-tag system and require a separate /fields/definitions API call per entity type (party, opportunity, case) to resolve field type, options for list fields, and display order. We query all field definitions before pulling record data, resolve list field option labels, apply the correct type casting (text, number, date, list) to raw values, and create matching custom fields in Pipedrive before writing records. List fields with defined options migrate as Pipedrive drop-down custom fields; free-text fields migrate as text custom fields.

Capsule Activities log against Parties. Each activity type (call, email, meeting, note) migrates to the corresponding Pipedrive Activity type. Activity description, timestamp, direction (for calls), and attendee list migrate directly. We resolve the related Party or Opportunity reference at migration time and write the activity link to the correct Person or Deal record. Activity attachments migrate as Pipedrive file attachments linked to the activity record.

Capsule Tasks carry due dates, assignees, status, and optional links to Parties or Opportunities. We preserve assignee mapping by resolving Capsule owner email to Pipedrive user ID. Tasks without an associated Party or Opportunity are imported as standalone Tasks with no linked entity. Completed task status maps to Pipedrive done=1; open tasks map to done=0. Overdue status is computed from the due date against the migration timestamp.

Capsule's flat tag model applies across Parties, Opportunities, and Cases. Tags migrate 1:1 to Pipedrive Labels, which apply across Deals, Persons, and Organisations. We preserve the tag name as the label name. If the Capsule account uses tags for multiple semantic purposes (e.g., both lead source and industry classification), we recommend the customer review label naming post-migration because Pipedrive Labels apply across all entity types with no separate namespaces.

Capsule Users are assigned as owners of Parties, Opportunities, Cases, and Tasks. We map Capsule users to corresponding Pipedrive users by email address match. Any Capsule user without a matching Pipedrive user account is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Capsule users migrate as inactive Pipedrive users so that historical ownership assignments are preserved without granting active system access.