Migrate from Lime CRM to Mailchimp

Lime CRM Contacts map directly to Mailchimp Subscribers. We extract first name, last name, email address, phone number, and all custom field values from the Lime CRM Contact record. Email address becomes the Subscriber hash for Mailchimp's audience identity. Custom Lime CRM fields map to Mailchimp merge fields (FNAME, LNAME, PHONE, and any custom field name) or to Tags if the field represents a categorical value rather than a scalar attribute. Contacts without a valid email address are flagged in the reconciliation report and held for the customer's admin to resolve before audience import.

Lime CRM Tags on Contacts map directly to Mailchimp Tags on the corresponding Subscriber. We preserve the full tag taxonomy from Lime CRM as a flat tag list per Subscriber. If the customer's Lime CRM uses a hierarchical tag structure (for example, a Region prefix and a Role suffix), we either preserve the full concatenated tag or work with the customer's admin during scoping to decide on a flattened naming convention that Mailchimp's tag UI can manage effectively.

Lime CRM Companies are not a native Mailchimp object, so we resolve the Company reference on each Contact and inject it as a Mailchimp Tag (for example, Tag = CompanyAcmeCorp) or as a merge field (COMPANY = 'Acme Corp') depending on whether the customer wants to use company data for audience segmentation. We flag this decision during scoping because tag-based segmentation performs differently from merge-field filtering in Mailchimp Customer Journeys. If the customer has more than 50 unique Companies, we recommend using a merge field rather than creating 50+ individual tags.

Mailchimp has no deal, opportunity, or pipeline object, so Lime CRM Deals cannot be migrated as live records. We export Deals to a structured CSV archive (Deal name, stage, value, owner, expected close date, company, contact) and deliver it alongside the Mailchimp audience migration. The customer's admin can import this CSV into a separate CRM, a spreadsheet, or use it to rebuild pipeline context in a parallel Lime CRM instance. We do not attempt to represent Deal stage as a Mailchimp tag because the tag limit per subscriber (applied at scale) becomes operationally unmanageable.

Lime CRM Activities (calls, emails, meetings, tasks, notes) linked to Contacts have no Mailchimp equivalent. Campaign activity (opens, clicks, bounces, unsubscribes) is owned by Mailchimp and does not need migration. We export Activities to a structured CSV archive (activity type, timestamp, subject, linked contact email, owner) and deliver it as a separate file. The customer's admin can import this into a separate CRM or a data warehouse. Note that Lime CRM exports email conversations as individual message files rather than threaded records, so we reassemble them by sender and timestamp before generating the activity archive.

Lime CRM Tickets represent support or service records with status, priority, assignee, and conversation history. Mailchimp does not have a service desk or ticket object. We export Tickets to a structured CSV archive (ticket ID, subject, status, priority, assignee, contact email, created date, last modified date) and deliver it alongside the audience migration. If the customer uses a separate helpdesk (Zendesk, Freshdesk, HubSpot Service Hub), we can recommend a CSV import pattern for that platform.

Lime CRM Custom Limetypes (configurable objects specific to the customer's industry variant) have no direct Mailchimp equivalent. We analyse each active Limetype during scoping, assess whether any of its fields map to subscriber attributes or tags, and apply one of three strategies: scalar fields become Mailchimp merge fields, categorical fields become Tags, and relational or transactional Limetypes become a separate CSV archive. We document every Limetype in the migration scope so the customer's admin knows which custom data exists and where it lives post-migration.

Lime CRM Attachments linked to Contacts (documents, files, images) do not migrate into Mailchimp because Mailchimp does not store file attachments per subscriber. We generate a CSV reference file listing each attachment (filename, Lime CRM record ID, linked contact email, file size, upload date) with a recommendation to store files in a cloud storage platform (Google Drive, SharePoint, Dropbox) and link to them from the CSV. For migrations where the customer has fewer than 500 attachments, we can package them as a zip archive and deliver it alongside the Mailchimp audience export.

Lime CRM Users and Deal Owners do not map to Mailchimp because Mailchimp does not have a user management or ownership model equivalent to a CRM. We resolve Owner email addresses from Lime CRM during scoping to validate owner-to-contact relationships, and we flag which Contacts had a specific owner so the customer can recreate that context in Mailchimp (for example, via Tags like Owner_Jane_Doe or a separate CRM). The owner data does not appear in the Mailchimp subscriber record itself.