Migrate from ClinchPad to Pipedrive

ClinchPad merges contact fields (first name, last name, email, phone, company, address) inside the Lead record. We extract these into Pipedrive Person fields. Every ClinchPad contact also carries a deal — we hold the Person import and defer finalization until the matching Deal is created so that the Person-Deal link resolves correctly. Contacts without a deal value in ClinchPad land in Pipedrive as Persons with no open Deal, which is a valid state. We track the original ClinchPad record ID in a custom field for reconciliation.

ClinchPad stores company name as a text field on the Lead. We create a Pipedrive Organization from this value and link it to the Person record. When the company field is blank or a personal email domain, we create a placeholder Organization or flag for the customer to merge. Pipedrive requires a Person to have either an Organization link or a 'no organization' designation — we handle the null state explicitly to avoid import validation errors.

Each ClinchPad Lead carries exactly one active deal with a deal value, expected close date, and pipeline stage. We map these directly to Pipedrive Deal fields (title, value, expected_close_date, stage_id). The Person-Deal link resolves after both records exist in Pipedrive — we run a post-import join using ClinchPad's internal record ID to attach the correct Person to each Deal. Closed-Lost and Closed-Won status from ClinchPad maps to Pipedrive deal status values.

ClinchPad's Kanban columns (user-defined names like New, Contacted, Proposal, Won, Lost) become Pipedrive pipeline stages. We preserve exact stage names and sequence order. Pipedrive requires a Pipeline to be created before stages can be assigned — we create the pipeline first using ClinchPad's board name, then populate stages in the same order as the source. Probability percentages per stage are configurable in Pipedrive and set to defaults if not specified in ClinchPad.

ClinchPad notes attached to a Lead or deal migrate as Pipedrive Notes linked to the corresponding Person or Deal via ContentDocumentLink. We preserve note body text, creation timestamp, and author name if present in the export. Note volume per record in ClinchPad is typically low, making the import straightforward. Rich text formatting is simplified to plain text if the export does not preserve HTML.

ClinchPad tags migrate as Pipedrive Labels on the Person record. Pipedrive labels are a standard feature at all paid tiers. If the customer uses tags for data classification beyond simple labels (e.g., source tracking), we recommend creating a custom single-select or multi-select field in Pipedrive rather than relying solely on labels, and we configure this during the pre-migration schema setup.

ClinchPad has a flat user model with no role permissions. We map ClinchPad users to Pipedrive Users by email match. Any ClinchPad Owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on Person and Deal records uses the resolved User ID. ClinchPad's flat model means role-based access does not carry over.

ClinchPad supports limited custom text fields on Lead records. We export these as string values and pre-create matching custom fields in Pipedrive before migration. Pipedrive custom fields support text, number, date, single-select, multi-select, and other types — we set the most appropriate Pipedrive field type during scoping. The customer may need to adjust field types manually in Pipedrive after migration if the source export does not indicate data format clearly.

ClinchPad stores files outside the lead record — as Wufoo form attachments, Dropbox references, or direct uploads. The CSV export contains filename and external URL only, not file bodies. We request access to the source attachment store during scoping, download the files, and re-attach them to the corresponding Pipedrive Person or Deal record. Filename deduplication is handled when multiple records share the same attachment name. If the external storage is inaccessible at migration time, we flag the affected records and document what is missing.

ClinchPad exposes no structured activity log (calls, emails, meetings, tasks) via any documented export mechanism. Only notes transfer. We do not fabricate activity history. This limitation is material — teams relying on ClinchPad's activity timeline should capture this information separately (for example, exporting from an integrated email client or calendar) before migration. We document the gap in the migration inventory and suggest a manual documentation approach for any activity data the customer cannot otherwise retrieve.