Migrate from ClinchPad to Nutshell

ClinchPad Lead records map directly to Nutshell Person records. The contact name splits into Nutshell Person's first_name and last_name fields; email, phone, and address map to the corresponding Person fields. Company name from the ClinchPad Lead creates a Company lookup in Nutshell (created first or matched by name if a matching Company exists). Any custom text fields on the ClinchPad Lead create matching custom fields on the Nutshell Person record. The ClinchPad lead source value migrates to a Nutshell Person custom field since Nutshell's standard Person model does not include a native source field.

ClinchPad's deal value, expected close date, and stage name map to Nutshell Deal's monetary_value, expected_close, and pipeline stage. Each ClinchPad Lead with an active deal generates one Nutshell Deal record linked to the Person created from that Lead. Contacts without an associated ClinchPad deal are migrated as Nutshell Persons only with no Deal record, landing in Nutshell's unqualified lead queue for follow-up.

ClinchPad's user-defined Kanban columns (New, Contacted, Proposal, Won, Lost, and any custom stages) map to Nutshell pipeline stages in the configured pipeline. We preserve exact stage names and sequence order. Nutshell allows probability and forecast settings per stage; we set these based on the ClinchPad stage name conventions or the customer's guidance during scoping.

The company name field on a ClinchPad Lead creates or matches a Nutshell Company record. If multiple ClinchPad Leads reference the same company name, they link to a single Nutshell Company, enabling Nutshell's company-centric reporting. Company-level custom fields migrate to matching Nutshell Company custom fields. This mapping resolves before Person import to satisfy the Company lookup reference on Person.

Notes attached to a ClinchPad Lead migrate to Nutshell Activity records of type note on the corresponding Person record, with the timestamp and author preserved if exposed via the CSV export. Note volume per record is typically low in ClinchPad, so this mapping handles the typical record count without chunking requirements.

ClinchPad stores attachment references outside the lead record — filenames and URLs from Wufoo forms, Dropbox links, or direct uploads. The CSV export does not include file bodies. We request access to the customer's ClinchPad attachment store (Dropbox account, Wufoo form submissions, or the ClinchPad file source) during discovery, retrieve the files, and re-attach them to the corresponding Nutshell Person or Deal record. Filename deduplication is handled when multiple records reference files with identical names.

ClinchPad tags migrate to Nutshell tags on the Person or Deal record. If the customer has a high volume of tags with no consistent taxonomy, we create a custom multi-select picklist field on the Nutshell Person record to preserve tag detail without cluttering the standard tag field.

ClinchPad users map to Nutshell Users by email match. ClinchPad's flat user model (no granular role permissions) maps to Nutshell User records with the user's name and email carried over. Role-based access control does not carry over because ClinchPad does not expose a role hierarchy in its export. Any ClinchPad user not yet provisioned in Nutshell is held in a reconciliation queue for the customer's admin to create before record import proceeds.

ClinchPad custom text fields on leads migrate to Nutshell Person custom fields with text type. We create the destination custom field in Nutshell before migration, matching the field label and preserving any non-empty values from ClinchPad. Field type conversion is straightforward since ClinchPad only supports text custom fields. The customer may need to adjust field visibility and required settings in Nutshell post-migration.