Migrate from OplaCRM to Mailchimp

OplaCRM Contacts migrate to Mailchimp Audience Members. Email address serves as the primary dedupe key. First name, last name, phone, and address fields map directly to Mailchimp's standard contact fields. The contact-to-account link is preserved as a Mailchimp merge field (ACCOUNTNAME) or as a Group membership if the customer chooses account-based grouping. Opt-in and opt-out status migrates to Mailchimp's SUBSCRIBED, UNSUBSCRIBED, and CLEANED statuses based on OplaCRM's contact state flags.

OplaCRM Accounts map to Mailchimp Groups or Tags depending on the customer's segmentation strategy. Groups are hierarchical and suit multi-brand or multi-segment audiences; Tags are flat and suit behavioral or source-based labeling. We discuss the strategy during scoping. The Account's industry, region, or size fields can map to additional Group categories. Account-level addresses map to Mailchimp contact address fields for contacts that belong to that account.

OplaCRM CustomFieldValueDto key-value pairs per contact translate to Mailchimp merge fields. We pre-create merge fields in Mailchimp with type-mapped types (text, number, date, phone) before import. Field names that collide with Mailchimp's reserved merge field names (EMAIL, FNAME, LNAME, etc.) receive an 'opla_' prefix and are surfaced in the pre-flight mapping table for the customer to rename or accept before import. Some custom field types (dropdowns, multi-selects) map to Mailchimp radio or checkbox merge fields respectively.

OplaCRM tag arrays per contact migrate to Mailchimp Tags directly. We split any comma-delimited tag strings into individual tag entries to match Mailchimp's tag-per-label model. Tags survive re-import if the customer runs multiple migration passes. Tags used for account-based classification also become Mailchimp Tags; the customer decides whether to mirror these as Groups or Tags during scoping.

OplaCRM Users referenced as contact owners map to Mailchimp admin users if the owner is a sending user, or to a CONTACT_OWNER merge field on the contact record if the owner is informational. Owner email matching against Mailchimp's user table determines which path applies. Gamification owner data (streaks, goals, leaderboard positions) has no Mailchimp equivalent and does not transfer.

OplaCRM Products map to Mailchimp product catalog entries if the customer uses Mailchimp's e-commerce connected store feature. Product name, SKU, and pricing migrate as product record fields. Without Mailchimp e-commerce connected store enabled, Products do not transfer to a standard Mailchimp object and are flagged as a post-migration decision.

OplaCRM Opportunities (deal records with stage, close date, close reason, and win/loss status) have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not maintain a deal or pipeline data model. We do not migrate Opportunities. We flag the count and stage distribution in the pre-flight handoff so the customer's team can decide whether to export Opportunity data to a spreadsheet, a dedicated CRM, or an external reporting tool for ongoing reference.

OplaCRM's locked boolean flag prevents editing on Accounts, Contacts, and Opportunities. Mailchimp has no record-level locking mechanism. We do not replicate the lock flag. We set locked OplaCRM contacts to UNSUBSCRIBED status in Mailchimp to prevent accidental sends, and surface the full list of locked records in the pre-flight handoff for the customer to review and manually restore subscription status post-migration if appropriate.

OplaCRM's composite healthscore aggregates relationship signals per account using an opaque algorithm with no documented scoring logic. Mailchimp has no native healthscore concept. We do not transfer healthscore values. We flag the presence of healthscore data in the pre-flight report and note that if the customer needs account health monitoring in Mailchimp, it requires a third-party integration (e.g., Salesforce Mailchimp app, a data warehouse + BI tool, or a custom Mailchimp Plus add-on) outside standard migration scope.

OplaCRM contact records with an unsubscribed or bounced status flag migrate to Mailchimp's suppression list rather than the active audience. This prevents accidental re-send to contacts who opted out in OplaCRM. We extract unsubscribed and bounced contacts separately, import them to the Suppression List section of the Mailchimp Audience settings, and confirm the suppression count before activating the audience for sends.