Migrate from ClinchPad to Microsoft Dynamics 365 Sales

ClinchPad merges contact details (name, email, phone, company) with a deal into a single flat Lead record. We split each ClinchPad Lead into three destination records: an Account (using the company name or domain), a Contact linked to that Account, and an Opportunity linked to the Contact with the original deal value and expected close date. For leads without a company name, we create a standalone Contact without an Account. We flag any ClinchPad Lead with no associated deal as a Dynamics 365 Lead rather than a Contact-Opportunity pair, so it enters the lead queue for follow-up qualification.

The deal portion of each ClinchPad Lead maps to a Microsoft Dynamics 365 Sales Opportunity. We resolve the parent Contact and Account references before inserting the Opportunity so that the AccountId and ContactId lookups are satisfied at import time. The deal value maps to Amount, expected close date maps to EstimatedCloseDate, and the ClinchPad pipeline stage maps to the nearest Dynamics 365 StageName value in the configured Sales Process.

Each ClinchPad Kanban column (stage) becomes a StageName value in a Microsoft Dynamics 365 Sales Process that we create during schema design. Stage probability percentages from ClinchPad map to StageProbability on each Stage. Stage sequence order is preserved so the pipeline funnel in Dynamics 365 matches the ClinchPad visual board.

If ClinchPad has multiple pipeline boards (available on Silver tier and above), each becomes a separate Dynamics 365 Record Type on Opportunity, paired with its own Sales Process containing the relevant stage values. This keeps pipeline data scoped per business line.

ClinchPad notes attached to a Lead or deal migrate as Dynamics 365 Note records. We link each Note to the parent Contact or Opportunity via the relevant object lookup (ContactId or OpportunityId). Note timestamps are preserved from the ClinchPad export. Note volume per record is typically low in ClinchPad, so bulk insert via Dataverse API handles the import efficiently.

ClinchPad stores files as external references (Dropbox links, Wufoo attachments, or direct uploads). The CSV export does not include file bodies. We request customer-provided access to the source attachment store during scoping and re-upload files to SharePoint or Dynamics 365 native file storage, linking them to the corresponding Contact or Opportunity record via the regarding_objectid field. We handle filename deduplication when multiple records share the same attachment name.

ClinchPad lead tags migrate as a text field on the Contact or Lead record in Dynamics 365. If the customer uses tags for segmentation, we create a multi-select picklist custom field to preserve the multiple-tag-per-record behavior. Dynamics 365 does not have a native tagging model at the Contact level, so a custom field is the standard approach.

ClinchPad flat users map to Dynamics 365 User records. We match by email address during the import. ClinchPad does not expose a role or permission model in export, so role-based access control does not carry over — the customer's Dynamics 365 admin configures Security Roles post-migration based on the user's job function. Inactive ClinchPad users map to inactive Dynamics 365 Users to preserve historical assignment without generating login access.

ClinchPad custom text fields on Leads migrate as Dynamics 365 custom fields on the Contact or Lead entity. We export the field names and values from the ClinchPad CSV, then create matching custom fields in Dynamics 365 during schema design. Note that ClinchPad only supports text-type custom fields, so all migrated custom fields arrive as Text type and the customer's Dynamics 365 admin configures the appropriate field type (Picklist, Date, Number) post-migration based on the intended use.