Migrate from ClinchPad to Freshsales

ClinchPad Lead records that contain deal data split into three Freshsales objects: a Contact record (derived from the lead name and contact fields), an Account record (created from the company name if present), and a Deal record linked to both. We use the company name as the Account dedupe key. Leads without deal data land in Freshsales as Lead records, which are available in Freshsales Growth and above. The original ClinchPad deal value, expected close date, and pipeline stage are preserved on the Deal record. Source attribution from ClinchPad maps to the Freshsales Lead or Contact source field.

ClinchPad Lead records with no associated deal become Freshsales Lead records directly. Email, phone, company, and any custom text field values map to the corresponding Freshsales Lead fields. The customer decides during scoping whether all Leads should enter Freshsales as Leads (pending qualification) or whether some should convert immediately to Contacts and Accounts. Any ClinchPad tags on the lead map to the Freshsales Contact label field if the record converts during migration.

ClinchPad deal values map to Freshsales Deal with deal_name (derived from the contact or company name), amount, expected_close_date, owner_id (resolved via user mapping), and stage_name (mapped from the ClinchPad pipeline column). The deal status (active, won, lost) is inferred from the ClinchPad pipeline stage name. Stage probability percentages are set in Freshsales deal stage configuration rather than on individual records.

Each ClinchPad Kanban column maps to a Freshsales deal stage with the same name and sequence order. We create the stage configuration during schema setup before record import. If ClinchPad stages include Closed-Won and Closed-Lost, these map to Freshsales deal stages with the appropriate status field values. Stage probability defaults can be set per stage or left to Freshsales defaults and adjusted post-migration.

Notes attached to ClinchPad Lead or Deal records migrate as Freshsales timeline Note entries. We extract the note body, author name, and timestamp from the CSV export where available. Each note is linked to the parent Contact, Account, or Deal record in Freshsales. Note deduplication uses the note body hash as a secondary check when multiple notes share the same timestamp.

Files attached to ClinchPad leads are stored externally via Wufoo forms, Dropbox links, or direct uploads. The CSV export contains filenames and attachment URLs but not file bodies. We request customer-provided access to the source attachment store during scoping, download the files, and re-attach them to the corresponding Freshsales Contact, Account, or Deal record using the Freshsales file upload API. Filename conflicts are resolved by appending the ClinchPad record ID.

ClinchPad tags on leads migrate to the Freshsales Contact or Lead label field. If the customer uses tags for segmentation or lead scoring, we recommend creating a custom multi-select picklist field in Freshsales to preserve tag granularity beyond the native label field. Tag strategy is confirmed during scoping before schema deployment.

ClinchPad custom text fields on leads export as text columns in the CSV. We create matching custom properties in Freshsales before migration, using the same field name where possible and applying the text field type. Note that Freshsales may require manual type configuration (text vs. number vs. date) in the admin settings before import; we flag this during schema setup and provide a checklist for the customer's admin to complete before production migration.

ClinchPad users map by email to Freshsales User records. We extract all distinct owners referenced on Leads and Deals and resolve by email against the Freshsales User table during migration. Any ClinchPad user without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before the production migration phase begins. Role-based access control does not carry over from ClinchPad (it has none) and is assigned post-migration in Freshsales Admin Settings.

ClinchPad does not expose a structured activity log, call log, or task object via any documented export mechanism. We cannot migrate engagement history beyond notes and file attachments. This is not a migration gap — it is a platform gap. Activity tracking starts fresh in Freshsales from the day of cutover. Freshsales Growth and above provide built-in activity logging (calls, emails, meetings, tasks) on Contact and Deal records.