Migrate from Opal CRM to Mailchimp

Opal CRM Leads map to Mailchimp Contacts within a single Audience. Standard fields (first name, last name, email, phone) map to Mailchimp Merge Fields (FNAME, LNAME, EMAIL, PHONE). Any custom fields on the Lead object migrate as additional merge fields. We deduplicate by email address using Mailchimp's built-in hash-based deduping and flag any records with missing email as a manual-rebuild item.

Opal CRM Company records (if present alongside Leads) map to Mailchimp merge fields or tags on the Contact. We recommend a COMPANY merge field for the primary organization name. If companies have multiple associated contacts, we create tags per company name and apply them to all migrated contacts from that company for segmentation purposes.

Opal CRM Sales Reps do not have a Mailchimp equivalent because Mailchimp has no user-assignment model for contacts. We capture the assigned Sales Rep name on each Lead as a tag (format: owner:{rep_name}) during migration. The customer's admin applies these tags manually or sets up a Mailchimp collaborator workflow if rep-based contact routing is required post-migration.

Opal CRM pipeline stages (Lead, Qualified, Proposal, Negotiation, Closed) do not map to Mailchimp objects because Mailchimp has no pipeline model. We capture the pipeline stage as a tag on each contact (format: stage:{stage_name}) and recommend the customer build Mailchimp Segments based on stage tags for targeted campaign routing. Stage order and probability do not migrate; these are documented for manual rebuild if needed.

Opal CRM email activity logs migrate as notes on the corresponding Mailchimp Contact. Each email engagement becomes a note entry with the original timestamp, subject, and direction (sent/received). Mailchimp's contact timeline displays these as historical notes rather than a structured activity log.

Opal CRM call logs migrate as notes on the corresponding Mailchimp Contact. We include call duration, disposition, and timestamp in the note body. Call recordings do not migrate; we flag this in the handover documentation for the customer's admin.

Opal CRM Tour Plans with itinerary dates, locations, and expense line items have no Mailchimp equivalent. We do not migrate Tour Plans as data records. We document the Tour Plan schema (fields present, record count) in the handover notes so the customer's admin can decide whether to export separately or rebuild using Mailchimp's customer journey automations with date-based triggers.

Opal CRM Quotations with line items and workflow approval state have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not handle sales quoting, contract generation, or approval workflows. We document the Quotation schema (field count, workflow status values) in the handover notes. The customer rebuilds quotation workflows outside Mailchimp or exports quotation data to a spreadsheet.

Opal CRM custom fields on Leads migrate to Mailchimp Merge Fields. We identify custom fields during discovery (the schema is not publicly documented, so we extract field names from the customer's manual export), create matching merge fields in the Mailchimp Audience before import, and map values during the CSV transformation. Merge field type (text, number, date, phone) is inferred from data values in the export.