Migrate from DinamikCRM to Mailchimp

DinamikCRM Contact records map directly to Mailchimp Audience members. Email address serves as the primary subscriber key. First name and last name map to FNAME and LNAME merge fields. Phone number maps to PHONE merge field. We extract email opt-in status from DinamikCRM's communication preferences or custom fields and set the corresponding Mailchimp status (subscribed, unsubscribed, or pending if double opt-in is configured). Contacts without an email address are held in a reconciliation queue for manual review.

DinamikCRM Company records do not have a direct Mailchimp equivalent. Company name maps to a COMPANY merge field on the Audience, and Company industry or size maps to additional Merge Fields. We configure these Merge Fields in Mailchimp before import and populate them during Contact migration. If the customer uses Company as a segmentation dimension (e.g., send only to contacts from companies in a specific industry), we recommend tagging contacts by Company during migration rather than relying solely on Merge Fields.

DinamikCRM Lead records with email addresses migrate as Audience members with status set to subscribed or pending depending on the lead source and consent status. We map DinamikCRM lead score (if present) to a custom LEADSCORE merge field. Lead status (New, Contacted, Qualified) migrates as a STATUS merge field for segmentation use in Mailchimp. Leads without email are flagged for manual review.

DinamikCRM tag assignments on Contacts and Leads migrate as Mailchimp Tags on the corresponding Audience members. We extract all tag associations per contact during the export phase and apply them as Tags in Mailchimp during import. Tag names are preserved as-is. If DinamikCRM uses a tagging hierarchy, we flatten it to a single tag namespace (e.g., Region-North instead of nested Region:North tags) unless the customer requests a specific format.

DinamikCRM Activity records (calls, emails, meetings, tasks) have no Mailchimp equivalent. Mailchimp tracks engagement at the subscriber level (opens, clicks, unsubscribes, bounces) against campaigns rather than storing discrete activity records. We do not migrate Activity history. If the customer requires historical engagement context, we recommend exporting DinamikCRM Activities as a CSV and using it as a reference document for rebuilding customer context manually in Mailchimp notes or as internal records.

DinamikCRM Deal records with values, stages, and owners do not map to any Mailchimp object. Mailchimp does not support Deal or Opportunity records. We do not migrate Deal data. If the customer needs Deal context for segmentation (e.g., current customer vs. prospect), we recommend tagging contacts by Deal status (e.g., Tag: DealStatus-Won, DealStatus-Lost) during migration scoping, which can be implemented as a Tag based on Deal records extracted from DinamikCRM.

DinamikCRM Appointment records including date, time, attendee, and status have no Mailchimp equivalent. Mailchimp tracks campaign sends and engagement but not calendar-based scheduling. We do not migrate Appointment data. If appointment history is business-critical, we recommend exporting Appointments as a CSV for manual reference.

DinamikCRM Invoice records with line items, totals, and status have no Mailchimp equivalent. Mailchimp is an email marketing platform, not a billing or financial system. We do not migrate Invoice data. If the customer uses invoice history for segmentation (e.g., past customer vs. never purchased), we recommend mapping invoice status to Mailchimp Tags during migration scoping.

DinamikCRM DESK module tickets with status, priority, assignee, and conversation threads have no Mailchimp equivalent. We do not migrate ticket data. If the customer needs support context for segmentation, we recommend tagging contacts by ticket status (e.g., Tag: SupportStatus-Open, Tag: SupportStatus-Closed) based on exported ticket data.

DinamikCRM custom modules vary per customer account. During scoping, we enumerate active custom modules and their field schemas via the DinamikCRM API discovery phase. Custom fields that map to Mailchimp-supported types (text, number, date, phone, address) become Merge Fields. Fields that map to categorical data become Tags. Highly complex custom module structures with nested relationships are flagged as non-migratable and documented in the migration scope for the customer to handle manually post-migration.