Migrate from Workbooks to Mailchimp

Workbooks People records map to Mailchimp Members within a single Audience. The email address is the required Mailchimp member identifier and dedupe key. First name and last name map to the FNAME and LNAME merge fields. We preserve the Organisation link as a merge field (COMPANY) and optionally as a Mailchimp tag derived from the Organisation name for segmentation. Phone numbers map to the PHONE merge field if present in Workbooks.

Workbooks Organisations do not have a direct Mailchimp equivalent because Mailchimp Audiences contain Members without a native company object. We extract the Organisation name and map it to a COMPANY merge field on the Member record. For segmentation use cases, we also apply the Organisation name as a tag on each Member so that audience filtering by company is possible in Mailchimp's reporting and campaign builder.

Workbooks custom fields defined on the People record type map to Mailchimp merge fields. Text fields become TEXT merge fields with a 255-character limit; we flag any Workbooks text fields exceeding this length during scoping. Date fields become DATE merge fields. Number fields become NUMBER merge fields. Checkbox fields become CHECKBOX merge fields. Dropdown fields map to either a TEXT merge field or, if the Mailchimp plan supports it, a GROUP category for categorical segmentation. The customer specifies the merge field names during scoping.

Workbooks Lead records with an email address map directly to Mailchimp Members. Lead status and lead source from Workbooks become merge fields (LEAD_STATUS, LEAD_SOURCE) or tags for segmentation in Mailchimp. Unconverted Leads (those not yet associated with a Person record) are included in the migration to preserve the full contact universe. Any Lead without a valid email address is held in a reconciliation report for the customer's admin to address before import.

Workbooks Campaign records hold marketing initiative metadata (name, status, start/end dates, associated members). Mailchimp Campaigns are the actual email sends. We do not migrate Workbooks Campaign records as data objects because they have no Mailchimp equivalent. We deliver a written inventory of Workbooks Campaign names, statuses, and associated member counts as a reference for rebuilding campaign structure in Mailchimp.

Workbooks email engagement history (logged emails linked to People or Organisations) has no Mailchimp equivalent. Mailchimp tracks sent and delivered emails at the campaign level, not as individual activity records on contact profiles. We do not migrate email engagement history; the customer's Mailchimp account begins tracking email engagement from the date of migration forward.

Workbooks Opportunities represent deals in a pipeline with stage, probability, and value. Mailchimp has no pipeline, deal, or opportunity object. Opportunities, their stage history, probability weights, and expected close dates do not migrate. We flag this as an excluded scope item and recommend that the customer evaluate whether a separate CRM is needed for pipeline management if Opportunities data is critical to their business.

Workbooks Cases represent support tickets with status, priority, and activity log. Mailchimp has no case or ticketing object. Case records, their status and priority values, and case activity history do not migrate. We flag Cases as an excluded scope item.

Quotations, Invoices, and Orders are available on Workbooks Business tier and above. Mailchimp has no quoting, invoicing, or order management capability. These objects do not migrate regardless of Workbooks subscription tier. We confirm the source tier during scoping and flag the absence of these objects if the Business tier is not active.