Migrate from Verenia to Mailchimp

Verenia Contact records map to Mailchimp Members within a target Audience. Standard fields (first name, last name, email, phone) map directly to Mailchimp merge fields FNAME, LNAME, EMAIL, and PHONE. The original Verenia Contact ID is preserved as a custom merge field verenia_contact_id__c for cross-referencing. If contacts share duplicate emails across multiple Verenia records, we flag duplicates during discovery and the customer decides whether to merge or keep separate Member records.

Mailchimp does not have a dedicated Account or Company object. Verenia Company name, industry, website, and billing address map to custom merge fields on the Member record (COMPANY, INDUSTRY, WEBSITE, BILLINGCITY, BILLINGSTATE, BILLINGZIP). We create these merge fields in the target Audience before importing Members. Company-to-contact relationships are preserved by ensuring the Company merge field is set on each related Member record.

Verenia Quotes do not have a direct Mailchimp equivalent. We extract Quote number, Quote date, total amount, and status (Draft, Sent, Accepted, Lost) as custom merge fields on the associated Member record (QUOTE_NUM, QUOTE_DATE, QUOTE_TOTAL, QUOTE_STATUS). If multiple quotes exist per contact, we tag the Member with the most recent quote status (e.g., tag: Quote-Accepted) and store the quote amount in the QUOTE_TOTAL merge field. The full quote line-item detail cannot be represented in Mailchimp and is documented as a separate reference table.

Verenia Order records map similarly to Quotes. Order number, order date, total amount, and fulfillment status migrate as merge fields on the Member (ORDER_NUM, ORDER_DATE, ORDER_TOTAL, ORDER_STATUS). Tags are applied to represent fulfillment state (e.g., Order-Pending, Order-Shipped, Order-Completed). Mailchimp does not support line-item detail or product-level order records, so order product breakdown is preserved in a supplemental CSV reference file delivered alongside the migration.

Verenia User records map to Mailchimp Team Members if the destination Mailchimp account supports team collaboration. We match by email address. Verenia Owner assignment on Contacts and Companies maps to a custom merge field ORIGINAL_OWNER on the Member record. Note that Mailchimp Team Member roles (Admin, Author, Manager, Viewer) do not correspond to Verenia's user roles and are configured independently in Mailchimp.

Verenia Products are catalog items with pricing rules and bundle structures. Mailchimp has no product catalog. We extract the product name, SKU, and list price as merge fields on Members who are associated with that product (PRODUCT_NAME, PRODUCT_SKU). For cases where a contact is associated with multiple products, we apply tags (e.g., Product-ProductA, Product-ProductB). Complex pricing tiers and bundle compatibility rules cannot transfer and are documented in a Product Configuration Reference delivered to the customer.

Verenia Product Configurations encoded guided-selling rules, bundle structures, and compatibility constraints. These are proprietary to Verenia's CPQ logic and have no equivalent in Mailchimp. We extract configuration metadata as tags on the Member record (e.g., Bundle-TypeA, Config-Override) and summarize the original configuration logic in a written Configuration Reference document. The customer's admin reviews this document to determine whether any rules warrant manual rebuild in Mailchimp's Customer Journey Builder.

Verenia exported Attachments (Quote PDFs, order confirmations, configuration screenshots) cannot be programmatically imported into Mailchimp's content library via the API in the same structured way as member records. We extract the attachment files from the export archive, normalize file names, and deliver them as a structured folder bundle. The customer uploads files to Mailchimp's Content Studio manually or via the API as a supplemental step. We provide a mapping file linking each attachment to the related Member record by Verenia ID.