Migrate from Onpipeline to Mailchimp

Onpipeline Contacts map directly to Mailchimp Audience Members. We map First Name, Last Name, and Email address to the standard Mailchimp merge fields (FNAME, LNAME, EMAIL). Custom properties on Onpipeline Contacts (phone, address, custom fields) map to Mailchimp merge fields of the appropriate type, subject to the 255-character TEXT field limit in Mailchimp. Long-text custom fields are truncated and flagged. The Contact's opt-in status in Onpipeline maps to the Member's subscribed/unsubscribed/bounced status in Mailchimp.

Onpipeline Companies do not have a direct Mailchimp equivalent because Mailchimp has no company or account object. We create custom merge fields on the Audience (COMPANY_NAME, COMPANY_PHONE, COMPANY_WEBSITE, COMPANY_ADDRESS) and populate them for each Member who has a linked Company in Onpipeline. The Company-to-Contact linkage is not preserved as a relational structure; it is flattened into per-member field values. If the customer needs company-level segmentation, we recommend creating Mailchimp Tags from the Company name so that segments can filter by company attribution.

Onpipeline Deals have no Mailchimp equivalent. Mailchimp is an email marketing platform without deal management, pipeline stages, deal values, or opportunity tracking. We do not migrate Deal records. We flag the Deal stage distribution in the migration inventory so that the customer's team can document pipeline values for manual re-entry or reporting outside Mailchimp. The deal-to-contact linkage is lost as a structural relationship; it can be approximated by tagging Members with the deal stage or deal value at migration time if the customer requests it during scoping.

Pipeline Stages and stage probabilities are sales process metadata with no Mailchimp equivalent. We capture the pipeline stage hierarchy from Onpipeline and document it in the migration inventory as a reference for the customer's admin to maintain outside Mailchimp. Stage names can be mapped to Tags on the migrated Audience Members if the customer wants to retain stage attribution for reporting purposes.

Onpipeline Activities — Events, Tasks, Notes, Calls, and email history — do not migrate to Mailchimp. Mailchimp tracks email engagement (opens, clicks, bounces, unsubscribes) natively but has no concept of a sales activity timeline, call logs, or meeting records. We extract activity timestamps per Contact during scoping and document the activity volume in the migration inventory, but the records themselves have no destination. The customer's admin may choose to export activity summaries as a CSV reference file stored outside Mailchimp.

Onpipeline Products can be mapped to Mailchimp merge fields or Tags. For product interest tracking, we recommend creating Tags named after the Product catalog entries and applying them to Members who have interacted with those products in Onpipeline (via Deals or Quotes). For SKU and price data, we create custom merge fields on the Audience. Inventory quantity from Onpipeline has no Mailchimp equivalent and is not migrated.

Onpipeline Quotes with e-signature status, line items, and totals have no Mailchimp equivalent. We capture the quote count and total value per Contact as a custom field (QUOTE_TOTAL) for reference, but the quote records themselves — including line items, pricing tiers, and e-signature status — do not migrate. The customer's admin should export quote PDFs from Onpipeline before account closure.

Invoice headers, line items, and payment status from Onpipeline do not migrate. Mailchimp has no invoice or billing record storage. We note the invoice total paid per Contact as a merge field (LIFETIME_VALUE) if the customer requests it during scoping, but recurring invoice configurations and payment history are outside Mailchimp's scope. Onpipeline invoice PDFs should be exported before account closure.

Onpipeline Tags applied to Contacts, Companies, and Deals map directly to Mailchimp Tags on the Audience Member. Multi-tag assignments per record are preserved. Tags are one of the most transferable data assets in this migration because Mailchimp's tagging model is compatible with Onpipeline's. We recommend tagging Members with deal-stage names and company associations to partially reconstruct the CRM context in Mailchimp segments.

Onpipeline custom fields on Contacts and Companies map to Mailchimp merge fields. We extract the custom field schema during scoping, create equivalent merge fields in the destination Audience (TEXT, NUMBER, DATE, ADDRESS, PHONE), and map values during migration. TEXT merge fields have a 255-character limit; long-text Onpipeline custom fields are truncated and flagged in the migration report. Boolean fields map to TEXT merge fields with 'Yes'/'No' values. Picklist fields map to MAILCHIMP INTEREST CATEGORY or TEXT merge fields depending on segmentation needs.