Migrate from CompanyHub CRM to Mailchimp

CompanyHub Contact records map to Mailchimp Members by email address. Standard fields (First Name, Last Name, Email) map directly to Mailchimp's required member fields. All CompanyHub custom fields on Contacts map to Mailchimp merge fields, subject to Mailchimp's Extended Field length limits of 80 characters per field and 255 characters for long-text fields. We flag any custom field exceeding these limits during scoping and discuss truncation or field splitting with the customer.

CompanyHub Companies have no direct Mailchimp equivalent. We store the Company Name, Industry, Website, and other Company fields as merge fields on the Member record, prepended with a prefix (e.g., company_companyname, company_industry). Alternatively, if the customer maintains separate audience segmentation by company, we create a Tag per Company and assign Members accordingly, subject to the 30-tag-per-subscriber performance threshold. The customer chooses the strategy during scoping.

CompanyHub Deals (pipeline records) have no equivalent in Mailchimp's object model. Mailchimp is an email service provider, not a CRM, and has no opportunity or pipeline object. We export all Deal records as a referenced CSV during migration, stored alongside the Mailchimp audience for admin reference. If the customer requires Deal data accessible within Mailchimp, we discuss storing it as merge field data on the associated Member, but this is not recommended for Deals with multiple line items or complex stage histories.

CompanyHub pipeline stage names and order are exported as part of the Deal CSV export. Pipeline stage values cannot be represented as a Mailchimp field because Mailchimp Audiences do not track deal progression. The stage history is preserved in the exported CSV with a reference to the associated Contact email.

CompanyHub Contact-level custom fields map to Mailchimp merge fields. We read the field definitions from the CompanyHub API (field name, type, and options) and create matching Mailchimp merge fields before import. Picklist-type custom fields map to Mailchimp radio or dropdown merge field types; multi-select maps to checkboxes where the number of options is within Mailchimp's supported range.

CompanyHub Custom Tables (Properties, Payments, Courses, and other domain-specific objects) have no Mailchimp equivalent. Mailchimp does not support sub-items or child record structures on Member objects beyond merge fields. We export Custom Table rows as a separate CSV keyed by the related Contact email, stored alongside the Mailchimp audience as a reference dataset. If the customer requires Custom Table data in Mailchimp, we discuss storing it as serialized merge field data or as a separate Mailchimp audience per table type.

CompanyHub Tasks have no Mailchimp equivalent. Tasks track sales follow-up reminders and internal assignments within a CRM workflow. Mailchimp has no task or reminder system. We export all Task records as a CSV with the assigned Contact email, due date, status, and description for admin reference.

CompanyHub Quotes contain line items, totals, and template references. Mailchimp has no quoting capability. We export Quote records as a CSV referenced by the associated Contact email and deal reference. If the customer uses Mailchimp Automations for post-sale onboarding sequences, we document how Quote data can trigger automation entry via API integration after migration.

CompanyHub Owners (sales reps) are mapped to Mailchimp Tags on Member records. We tag each Member with the name of the Owner (e.g., tag: owner_jane_doe) so that the customer can segment by sales rep in Mailchimp. This approach is subject to the 30-tag-per-subscriber limit. If the owner count exceeds this threshold per subscriber, we discuss an alternative using a merge field for Owner assignment.

CompanyHub email activity logs contain open/click metadata and optionally body text. Mailchimp does not expose historical email body content via API for re-import to another system. We export the email metadata (timestamp, recipient, open/click status) as a CSV referenced by Contact email. The email body text itself cannot be migrated into Mailchimp because it would duplicate content already sent via CompanyHub's email sync. If body content is critical for audit, we recommend a separate export to a document storage system.