Migrate from Zilliant CPQ to Mailchimp

Discovery and contact audit

We audit the Zilliant CPQ source environment across Accounts, Contacts, BDA attribute definitions, and product-to-contact relationships. We identify which BDA fields are String, Boolean, Decimal, or List type and flag List-type fields for localization review. We count distinct Account and Contact records, identify contacts with multiple BDA attributes, and assess whether the customer wants Quote header data, Sales Agreement dates, or Product references as contact attributes. The discovery output is a written scope document and a Mailchimp merge field specification.

BDA field mapping and Mailchimp merge field setup

We map each Zilliant CPQ BDA attribute to a Mailchimp merge field before import. String fields map to text merge fields, Boolean to checkbox or text flags, Decimal to numeric fields. List-type BDA fields map to dropdown or radio merge fields with the C4C code values as options. We create merge fields in the Mailchimp Audience directly via the Mailchimp API before any contact import begins. If the customer has existing Mailchimp merge fields, we coordinate to avoid conflicts.

Account and Contact extraction

We extract Zilliant CPQ Accounts as the primary import batch and Contacts as the secondary batch. For each Contact, we resolve the parent Account reference to populate the EMAIL, FNAME, LNAME, PHONE, COMPANY (account name), and any mapped BDA merge fields. We resolve PartnerRoleRecord associations as tags on the Contact if the customer wants partner role context preserved in Mailchimp. ERP_ID column data is extracted if the customer wants to maintain ERP cross-reference as a contact attribute for downstream integration.

Delta attribute enrichment and tagging

We enrich each Contact record with optional delta attributes from Zilliant CPQ: most recent Quote date (if agreed), Sales Agreement effective date range (if active), or product-of-interest tags derived from Quote line items. We create Mailchimp Tags for product references, account segments, and any B2B-relevant classification the customer wants for segmentation in Mailchimp campaigns.

Mailchimp Audience import and reconciliation

We import the extracted Contacts into the Mailchimp Audience using Mailchimp's bulk import API with batch chunking and duplicate-resolution on email address. We reconcile import row counts against Zilliant CPQ export counts and flag any contacts rejected due to missing required fields (primarily email address). Bounced, unsubscribed, and non-marketing-flagged contacts are flagged separately for the customer's compliance review.

Catalog delivery and rebuild handoff

We deliver the written catalog of Zilliant CPQ objects with no Mailchimp equivalent (Products, Quotes, Sales Agreements, Price Lists, Guided Selling Rules, Groovy scripts, ERP cross-references). We also deliver the Groovy script inventory as exported text for the customer's technical team to assess for manual rebuild or retirement. We do not rebuild Mailchimp Customer Journeys or automations as part of the migration scope; those are documented as a separate rebuild task. We support a one-week hypercare window for contact reconciliation issues raised post-import.