Migrate from openCRX to Mailchimp

openCRX Contact records (subtype of Account) map to Mailchimp subscribers in the primary audience. We map standard fields: first name to FNAME merge field, last name to LNAME, email address to EMAIL (subscriber identifier), phone number to PHONE merge field, and postal address toaddr fields. openCRX Contact created/modified timestamps map to Mailchimp timestamps for record age context. Duplicate resolution uses email as the dedupe key.

openCRX LegalEntity stores company-level data that has no native Mailchimp equivalent. We map company name to COMPANY merge field, website to CONAME, and industry to INDUSTRY. For more granular LegalEntity attributes (revenue, employee count, DUNS number), we create additional text or number merge fields scoped per audience. LegalEntity name is also applied as a tag on each Contact to enable audience segmentation by account.

openCRX PostalAddress and PhoneNumber are stored as separate object references on Account. We flatten these into Mailchimp address merge fields (ADDR1, ADDR2, CITY, STATE, ZIP, COUNTRY) and phone merge fields. Multi-address accounts (billing vs shipping) are not natively representable in Mailchimp's single-address subscriber model; we select the primary address for import and document secondary addresses in the field inventory.

openCRX custom fields added via DataBinding PropertySet are identified during scoping and mapped to Mailchimp merge fields of the closest matching type: text fields to TEXT merge fields, number fields to NUMBER, dates to DATE, phone to PHONE, and single-select to dropdown or radio merge fields. openCRX multi-select custom attributes map to Mailchimp tags rather than merge fields since Mailchimp does not offer a native multi-select merge field. The complete list of active custom fields is documented during scoping before any field creation begins.

openCRX Products and Price Lists have no native Mailchimp equivalent for general CRM use. If the customer uses Mailchimp e-commerce integrations (Shopify, WooCommerce, BigCommerce), we can map openCRX products to Mailchimp Product Connect records to enable product-based email personalisation. For standard Mailchimp use without e-commerce, product and pricing data is documented in the inventory and optionally stored as merge fields on relevant Contact records for reference.

openCRX Opportunities (part of the contract hierarchy) have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not include opportunity, pipeline, deal-stage, or sales-cycle management. We document the Opportunity schema (fields, stages, amounts) in the inventory and flag that these records will not migrate. Customers requiring pipeline management in Mailchimp should note that Mailchimp does not offer this capability and a dedicated CRM or sales engagement tool may be needed alongside Mailchimp.

openCRX Activity records (Activity objects with time-tracking and Activity Trackers) have no Mailchimp equivalent. Mailchimp's engagement data is limited to campaign-level opens, clicks, and unsubscribes derived from email sends. Call logs, meeting records, and standalone tasks from openCRX are not represented in Mailchimp. We document the volume and schema of Activity records during scoping. Any CRM-level activity context (last contacted, next follow-up) cannot be represented in Mailchimp's flat subscriber model.

openCRX Workflow Processes are segment-scoped and not standalone exportable records. Mailchimp Customer Journeys uses a fundamentally different trigger-and-action model. Neither the workflow definitions nor the workflow execution history can be migrated. We document every openCRX Workflow definition (trigger, conditions, actions) during discovery and deliver a written map with recommended Mailchimp Customer Journey equivalents for the customer's admin to rebuild post-migration.