Migrate from CRUMP CRM to Mailchimp

CRUMP CRM Contacts export from the Dynamics 365 web API as Contact records. Each Contact maps to a Mailchimp subscriber record within an Audience. Standard fields (firstname, lastname, email, phone, address) map directly to Mailchimp merge fields FNAME, LNAME, EMAIL, PHONE, and address fields. We preserve the original Contact createdon and modifiedon timestamps as merge fields mc_created_date and mc_modified_date for historical reference. Any unsubscribed or bounced contacts in CRUMP CRM are exported as a Mailchimp suppression list and imported before the main audience to ensure opt-out compliance.

CRUMP CRM Accounts represent company records linked to Contacts via a lookup relationship. Mailchimp has no formal Account or Company object, so Account names migrate as an AUDIENCE TAG (for segmentation by company) or as a custom COMPANY merge field on each contact record. We apply one strategy per migration based on contact volume and the customer's segmentation needs. Parent Account hierarchies are flattened to a single tag per contact; sub-account names are appended as a secondary tag if the customer requires that level of detail.

Deals in CRUMP CRM correspond to Opportunities in Dynamics 365 with pipeline stages, values, close dates, and line items. Mailchimp has no deal or pipeline object. We exclude Deals from the migration scope and document every active Deal in a written summary that includes the deal name, stage, value, close date, and linked Contact so the customer's admin can import it into a new CRM tool or maintain it in a spreadsheet. We do not attempt to recreate deal data as Mailchimp tags because the semantics are fundamentally different.

Helpdesk tickets in CRUMP CRM are Cases in Dynamics 365 with status, priority, description, and linked Contact. Mailchimp has no case or ticket object. We export the full ticket list as a structured CSV with columns for ticket_id, subject, status, priority, contact_name, contact_email, created_date, and resolution_date, and deliver it as a reference document for the customer to import into a dedicated helpdesk tool or evaluate alongside Mailchimp's own support ticketing if applicable.

Projects in CRUMP CRM are a distinct module from CRM Deals and include status, dates, assigned team members, and task-level detail. Mailchimp has no project management object. We export project records as a structured CSV for the customer to evaluate against project management alternatives (Notion, Asana, Trello, Monday.com) or to import into a tool the team already uses. Project records are flagged separately from Deals in the migration documentation so the customer can treat them as a distinct data set.

CRUMP CRM User accounts with Owner references on Contacts map to Mailchimp Admin users if the user is intended to send campaigns, or to a SALES_OWNER merge field on contact records if the owner attribution is relevant for segmentation and reporting in Mailchimp. We flag any inactive CRUMP CRM users for exclusion to avoid creating ghost Mailchimp accounts. Active users with no Mailchimp access requirement are documented as excluded from the Mailchimp admin roster.

CRUMP CRM custom entities created on Dynamics 365 vary per deployment. Each custom object is enumerated during the audit phase and evaluated for Mailchimp compatibility. Simple custom fields (text, number, date, phone) map to Mailchimp merge fields. Multi-value custom fields and lookup relationships are exported as CSV reference data for the customer to decide whether to import as Mailchimp tags, groups, or to hold in a separate CRM tool. We do not create relational data structures in Mailchimp because it does not support custom objects with lookup relationships.

CRUMP CRM records engagement history (calls, emails, meetings, notes, tasks) as separate activity records linked to Contacts. Mailchimp tracks campaign-level email performance (sends, opens, clicks, unsubscribes) rather than individual conversation records. We export engagement data as a structured CSV per activity type for the customer's admin to reference, but individual engagement records do not migrate into Mailchimp because there is no corresponding object. We recommend that teams requiring full conversation history adopt a dedicated CRM alongside Mailchimp post-migration.