Migrate from ClinchPad to Mailchimp

ClinchPad Lead records contain name, email, phone, company, and source fields that map directly to Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE, COMPANY). The merged Deal value (deal_value field in ClinchPad) and pipeline stage (deal_stage) are stored as custom merge fields in Mailchimp (e.g., DEALVALUE, PIPESTAGE) to enable segmentation by revenue potential or pipeline position. We verify the CSV export includes these columns during discovery because the UI export does not always surface deal fields by default.

ClinchPad Company names stored within Lead records map to the Mailchimp COMPANY merge field. If ClinchPad exposes a separate Company export, we create a Company-to-Contact relationship in Mailchimp via the CRM merge field, though Mailchimp does not support true relational data between companies and contacts as a native feature. We recommend the customer maintain a company association in a custom tag or segment if the company relationship is operationally important.

ClinchPad Deal value, expected close date, and pipeline stage have no native Mailchimp equivalent. We create custom merge fields in the Mailchimp audience (DEALVALUE, CLOSEDATE, PIPESTAGE) using Mailchimp's audience field builder, and populate them from the ClinchPad CSV export. These fields are available for segmentation and personalization but do not appear in Mailchimp's standard contact view without expanding the merge field panel.

ClinchPad Kanban pipeline stages (New, Contacted, Proposal, Won, Lost) are stored as the deal_stage value per Lead. We map these to Mailchimp tags (e.g., Pipeline-Won, Pipeline-Contacted) so that the customer's team can filter audience members by pipeline position. Tags are the closest Mailchimp equivalent to CRM pipeline stages, though they carry no deal value or probability weighting.

ClinchPad notes attached to a Lead are migrated as text entries in the Mailchimp subscriber profile. Mailchimp does not support a native chronological note timeline per contact, but notes appear in the contact's individual profile under the Notes section. We preserve the original ClinchPad note timestamp and author text if the CSV export includes these fields. Note volume per record is typically low in ClinchPad.

ClinchPad tags on Leads map directly to Mailchimp tags on audience members. We preserve the exact tag names during migration. Mailchimp tags support grouping (tag categories) if the customer's ClinchPad setup uses tag categories; otherwise tags land as flat labels.

ClinchPad Owner (the rep assigned to a Lead) has no Mailchimp equivalent because Mailchimp does not have a CRM-style owner or assignee field. We append the owner name as a tag (e.g., Owner-Sarah) or include it in a custom merge field (ORIGINALOWNER) so that the customer can identify which team member originally owned the contact in ClinchPad.

ClinchPad stores attachments as external links (Dropbox references, Wufoo uploads) rather than file bodies. The CSV export contains filenames and URLs only. We request customer-provided access to the source attachment store, extract files, and re-upload them to Mailchimp File Manager. We then attach them to the corresponding subscriber profile as a note with a download link. Direct file attachment to the Mailchimp contact record is not supported; file delivery requires embedding in a campaign or sending via a separate link.