Migrate from Crust CRM to Mailchimp

Crust CRM Contact records map to Mailchimp audience members via email address as the primary key. Standard fields (firstname, lastname, email, phone, address) map to Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE, ADDRESS). We handle the Crust CRM lifecycle stage or status property by either mapping to a Mailchimp tag or a custom audience field, depending on whether the customer plans to use Mailchimp tags for segmentation post-migration. Opt-in status from Crust CRM maps to the Mailchimp member status: subscribed, unsubscribed, or pending (for double opt-in flows).

Crust CRM Company records do not have a direct Mailchimp equivalent. We map company name to a custom merge field (COMPANY) and apply the company name as a tag on all members linked to that company during scoping. This preserves company-level grouping for segmentation without creating a separate company object. If the customer requires company-level reporting in Mailchimp, we create one audience per company as an alternative structure, which the customer chooses during scoping.

Crust CRM Deals map to no Mailchimp object. Mailchimp has no deal, opportunity, or pipeline stage concept. We do not migrate Deal records as code or structured data. We export Deal records as a CSV inventory delivered to the customer for their admin to evaluate: deals can be archived in Crust CRM before export, re-entered in a sales-focused tool post-migration, or managed as notes on the corresponding audience member in Mailchimp. We document this decision point during scoping.

Where Crust CRM stores Leads as a distinct object from Contacts, we migrate them as Mailchimp audience members with status = pending, preserving the lead score or lead status as a custom merge field. This maintains the audit trail for lead-sourced contacts without requiring separate management in Mailchimp.

Crust CRM email engagement records contain sender, recipient, subject, body, and timestamp. Mailchimp's campaign history tracks which members received which campaigns, not the content of individual emails. We do not migrate individual email engagement records as Mailchimp campaigns. We deliver a written summary of email engagement volume and the most recent engagement date per contact as a custom merge field that the customer can use for re-engagement targeting.

Crust CRM calls, meetings, tasks, and notes have no Mailchimp equivalent. Mailchimp does not store call logs, meeting records, or internal task lists. We do not migrate these as objects. We preserve the last activity date per contact as a custom merge field (LASTACTIVITY) so that the customer's team can reference recency without rebuilding a full activity log. For teams that require activity history, we recommend a separate CRM alongside Mailchimp post-migration.

Crust CRM's configurable modules may include custom field types beyond standard CRM objects. We audit the custom object schema during discovery, map supported field types (text, number, date, dropdown) to Mailchimp custom merge fields, and flag any field types that Mailchimp does not support (multi-select, complex relationships, file attachments). Unsupported custom fields are documented in the field mapping spreadsheet for the customer's admin to evaluate against Mailchimp's supported merge field types.

Crust CRM Users and owner assignments on contacts and deals have no Mailchimp equivalent. Mailchimp uses account-level user management, not record-level owner assignments. We do not migrate Crust CRM Users. Owner assignment data is preserved as a merge field (ORIGINAL_OWNER) on the audience member record for audit and reference. The customer's Mailchimp account users are provisioned independently of migration.