Migrate from ClientTether.com to Mailchimp

ClientTether Contact records map directly to Mailchimp audience members. Email address is the dedupe key. We extract first name, last name, email, phone, tags, and any custom field values that correspond to Mailchimp standard or merge fields. Contacts without a valid email address are held in a reconciliation report because Mailchimp requires an email address for audience membership.

ClientTether Leads map to Mailchimp audience members with the same structure as Contacts. Lead source attribution migrates as a custom merge field (LEADSOURCE__c equivalent in Mailchimp). We preserve the lead source ID or form ID as a reference value for attribution reconstruction in Mailchimp segments.

ClientTether Account records (representing franchisee entities, franchise owners, or brand accounts) have no direct Mailchimp equivalent because Mailchimp has no Account-level hierarchy. We export the account hierarchy as a flat tag structure (e.g., BRAND_AcmeCorp, FRANCHISEOWNER_JaneDoe, FSO_CentralRegion) and create Mailchimp segments from these tag combinations. Segments are more flexible than static lists for ongoing franchise territory segmentation.

ClientTether Tags migrate to Mailchimp Tags one-to-one. Tags used for automation trigger conditions are exported with their assignments so the customer can see which tags drive segmentation logic. Mailchimp Tags are additive labels on audience members and can be used as filter conditions in segments or Customer Journeys.

ClientTether Email Sequences (time-triggered drip campaigns) map to Mailchimp Campaigns. Each sequence step becomes a scheduled campaign send with the original delay interval preserved as a send-time offset from enrollment. Mailchimp Standard plan allows multiple steps in an automation flow; Essentials plan is limited. We flag any sequence with more than 4 steps for upgrade assessment because Mailchimp Essentials caps automation complexity. Sequence enrollment status migrates as a custom field to allow segmentation of contacts who completed or dropped out of the sequence.

ClientTether Pipelines (deal stages, pipeline assignments) have no Mailchimp equivalent. Mailchimp does not store deal stage data or pipeline assignments. We flag every Pipeline and its stages during discovery and document them as out-of-scope for manual replacement in a CRM tool if the customer needs pipeline management post-migration.

ClientTether Proposals (template-based documents with pricing and terms) have no Mailchimp equivalent. Mailchimp is an email marketing platform, not a proposal or quoting tool. We export proposal records as a CSV reference file for the customer's records but do not import them into Mailchimp. Proposals should be managed in a separate tool (ClientTether, PandaDoc, Better Proposals, or a CRM) post-migration.

ClientTether Work Orders (operational execution records linked to proposals) have no Mailchimp equivalent. Mailchimp does not store operational or fulfillment data. We export Work Order records as a reference CSV. Work order management should continue in a field service or operations tool post-migration.

ClientTether Call Logs (inbound and outbound call records with duration, disposition, and recording URL) do not migrate to Mailchimp. Mailchimp tracks email engagement activity (opens, clicks, unsubscribes) but has no call log storage. Call history should remain in ClientTether (read-only archive), a dedicated call logging tool, or be exported as a reference CSV for the customer's records.

ClientTether Custom Fields on Contacts and Leads map to Mailchimp Merge Fields. We enumerate all custom field types during discovery (text, number, date, picklist, checkbox) and map them to Mailchimp merge field types (text, number, date, phone, address, or birthday). Picklist values become predefined merge field options. Merge field names are normalized to Mailchimp's 10-character API name limit and the 255-character value limit.