Migrate from ClinchPad to Salesforce Sales Cloud

ClinchPad Lead records contain contact fields (name, email, phone, company, address) alongside deal data. We extract the contact fields and map them to Salesforce Contact fields: FirstName, LastName, Email, Phone, and MailingAddress. The original ClinchPad lead ID is preserved in a custom field clinchpad_lead_id__c for reconciliation.

The deal value, expected close date, and pipeline stage from each ClinchPad Lead map to a Salesforce Opportunity: Amount, CloseDate, and StageName. We create the Opportunity in the same step as the Contact, linking via AccountId. Any Contact without a deal value lands in Salesforce as a Contact without an Opportunity, which is the expected state for pre-opportunity prospects.

ClinchPad stores company name inside the Lead record. We create a Salesforce Account using the company name as the Account Name, with the original ClinchPad lead ID stored in a custom field for cross-reference. Account is created before Contact and Opportunity so that the AccountId lookup is satisfied at the moment of record insert.

ClinchPad's user-defined Kanban stages (New, Contacted, Proposal, Won, Lost, and any custom stages) map directly to Salesforce Opportunity Stage values. We preserve exact stage names and sequence order. Probability percentages are set from ClinchPad's stage-level data if available, otherwise we use Salesforce default probabilities. The customer chooses whether to use a single Sales Process or separate Sales Processes per stage group.

ClinchPad's multiple pipeline views (available on Silver and above) map to Salesforce Opportunity Record Types with corresponding Sales Processes. Each Record Type gets its own Page Layout so that stage values remain scoped per pipeline. If the customer has only one pipeline, we use the default Opportunity Record Type without additional configuration.

Notes attached to a ClinchPad Lead migrate as Salesforce Note records. We preserve the note body text, author if exposed via export, and timestamp. Notes are linked to the parent Contact and Opportunity via ContentDocumentLink. ClinchPad note volume per record is typically low, which limits the reconciliation scope.

ClinchPad stores attachments as external references — Wufoo form attachments, Dropbox links, or direct uploads — with filenames and URLs in the export. We request customer access to the source attachment store during discovery. Files are re-uploaded to Salesforce Files (ContentDocument and ContentVersion), linked to the corresponding Contact or Opportunity via ContentDocumentLink, and the original source URL is stored in a custom field attachment_source_url__c for audit.

ClinchPad tags on Leads migrate as a custom text field tag__c on the Contact object. If the customer has more than 20 distinct tags, we recommend a multi-select picklist for better filtering. Salesforce does not have a native tagging system equivalent to HubSpot or Pipedrive, so the tag strategy is decided during scoping and the custom field is created before migration.

ClinchPad users are matched to Salesforce Users by email address. Owners assigned to ClinchPad Leads map to the Salesforce OwnerId field on Contact and Opportunity. Any ClinchPad user without a matching Salesforce User is held in a reconciliation queue — the customer's Salesforce admin provisions the User before record import resumes. Role-based access control from ClinchPad does not carry over because ClinchPad has no granular permissions to model.

ClinchPad supports limited custom text fields on Leads. We export these as text strings and create matching custom fields on the appropriate Salesforce object (Contact, Account, or Opportunity) before migration. Field type decisions — text, picklist, number, date — are made during scoping based on the data content. Salesforce field-level security and page layout assignments for custom fields are documented for the admin to configure post-migration.

ClinchPad records the lead source field if populated. We map this directly to Salesforce LeadSource on both Lead and Contact. If ClinchPad uses custom source values not present in Salesforce's standard picklist, we either add them to the picklist or map them to a custom field.

ClinchPad Lead records include a source field identifying where the lead originated. We map this to a custom field account_origin__c on the Account for reporting purposes. Customers who relied on source data for campaign attribution preserve this information in Salesforce for pipeline attribution analysis.