Migrate from karmaCRM to Mailchimp

karmaCRM Contacts map directly to Mailchimp Subscribers. The email address serves as the dedupe key. We transfer first name, last name, phone number, address fields, custom field values, tag associations, and subscription consent status (email opt-in and date) into Mailchimp merge fields and subscriber status. Mailchimp's subscriber status (subscribed, unsubscribed, cleaned, pending) is set based on the contact's opt-in status in karmaCRM. Any karmaCRM contact with no valid email address is excluded and reported separately.

Mailchimp has no native company or account object. karmaCRM Company records (name, domain, industry, size, address, and custom fields) are mapped to Mailchimp merge fields attached to each Subscriber. The merge field names are derived from karmaCRM field labels. We apply company data to all Contacts in karmaCRM that have a company association, using the CONTACT_COMPANY merge field for the primary company name and additional merge fields (COMPANY_DOMAIN, COMPANY_INDUSTRY, COMPANY_SIZE) for supplementary data. Company-level tag associations are preserved as Mailchimp tags on each affected Subscriber.

karmaCRM Email Campaigns on Pro and Premium tiers carry audience name, subject line, send date, open rate, click rate, and bounce count metadata. We import this data as a reference document rather than live Mailchimp campaigns. The campaign HTML body does not migrate because Mailchimp campaigns require rebuilding through its builder with current branding and list segments. The metadata document lists each historical campaign with its performance metrics so the admin can reference past performance while configuring new Mailchimp Automations. Basic tier accounts (no email campaigns) skip this mapping.

karmaCRM Tags applied to Contacts and Companies map directly to Mailchimp native Tags. Tags are preserved as-is on each Subscriber during migration, and Mailchimp's tag-based segmentation is available immediately after migration without reconstruction. Mailchimp's tag model is more capable than karmaCRM's flat tag list, supporting tag-based customer journey entry conditions and tag-based automation splits.

Mailchimp has no deal or opportunity object, so karmaCRM Deal records (name, value, stage, owner, and created date) are stored as a custom merge field (DEAL_VALUE) and a plain-text note on each related Contact record. Deal stage pipeline names and pipeline-to-stage mapping are documented separately for the customer's admin. This mapping is informational; deal pipeline data cannot be operationalized within Mailchimp's feature set.

karmaCRM Tasks (assignments, due dates, priority, status) have no Mailchimp equivalent. Task records are excluded from migration. Mailchimp does not support task management features. We document task count and the list of contacts with open tasks so the admin can recreate task reminders as Mailchimp Automation triggers if needed. Calendar event records (karmaCRM Events) are similarly excluded because Mailchimp provides no calendar feature.

karmaCRM User accounts (team members with roles and permissions) do not map directly to Mailchimp Subscribers because Mailchimp Subscribers are external contacts, not internal team users. If a karmaCRM User account has a valid external email address and should receive marketing emails, we migrate that User as a Subscriber with a custom merge field (IS_TEAM_MEMBER__C) flagged true. Otherwise, Users are excluded from the subscriber migration and documented separately for the customer's admin to manage team access in Mailchimp.

karmaCRM Attachments linked to Contacts and Companies cannot be exported through the karmaCRM API. The platform does not expose a programmatic attachment export path in its documented endpoints or knowledge base. Attachments are flagged as out of scope with a recommendation to download files manually from the karmaCRM UI before account closure. Mailchimp supports image attachments within campaign content, not as contact-level files, so any file attachments from karmaCRM must be re-uploaded manually to Mailchimp if needed as campaign assets.