Migrate from Legrand Cloud CRM to Mailchimp

Legrand Contact records map to Mailchimp Audience Members via email address as the primary key. We map First Name and Last Name to Mailchimp FNAME and LNAME merge fields, email to EMAIL, and phone to PHONE. If the Contact has a parent Account, we tag the Member with the Account name and optionally write the Account industry or type to a company merge field. All Contacts from Legrand export are treated as opted-in for Mailchimp import; opt-in status is preserved from a Legrand email opt custom field if one exists.

Legrand Account records do not have a direct Mailchimp equivalent. We convert Accounts into two mechanisms: a Tag applied to every Member linked to that Account (tag name = Account Name), and optional merge fields COMPANY and INDUSTRY written per Member during import. The tag strategy allows the customer to filter their Mailchimp Audience by company in Mailchimp's segment builder. Accounts without linked Contacts generate orphaned tags that the customer can suppress post-import.

Legrand Leads export from the Lead Inbox module map to Mailchimp Members with the lead status preserved as a Tag (Lead: [source] or Lead: [status]). Lead owner and lead score custom fields in Legrand migrate to merge fields LEAD_OWNER and LEAD_SCORE if the Mailchimp plan supports custom merge fields. Leads that have been converted to Contacts in Legrand before migration are already captured in the Contact pass and are deduplicated by email address during Mailchimp import.

Legrand Opportunity and Deal records have no Mailchimp equivalent. Mailchimp does not track pipeline stages, deal values, or expected close dates. We flag Opportunities during scoping as excluded from migration scope and note that the customer should evaluate whether they need a CRM alongside Mailchimp if pipeline tracking is required. We do not migrate Opportunity data as it would have nowhere to land in Mailchimp's schema.

Legrand per-module custom fields map to Mailchimp merge fields. Mailchimp supports up to 40 merge fields per Audience and supports types: text, number, date, phone, address, and URL. We audit the customer's Legrand custom field schema during discovery, map each to a Mailchimp merge field, and note any fields that exceed Mailchimp's type constraints (e.g., multi-select picklists become comma-separated text). Merge field configuration is done in Mailchimp before bulk import; we provide the configuration guide and validate during the test pass.

Legrand Campaign records export with name, type, status, and target member count. We map these as Mailchimp Campaigns with the same name and status, but the campaign content (email templates, designs, send history) does not transfer because Legrand stores campaign content differently from Mailchimp. The customer rebuilds email creative in Mailchimp's campaign builder using the migrated campaign names as a reference list. Open and click engagement history from Legrand Campaigns is not preserved in Mailchimp.

Legrand Documents module exports files as individual attachments per record, not as a structured archive. Mailchimp does not have a document storage model; attachments in Mailchimp are limited to email campaign file attachments (stored in Mailchimp's file manager, not linked to Members). We flag Documents as excluded from migration scope and advise the customer to export them separately via Legrand's file download before account closure. We do not attempt to attach Legrand documents to Mailchimp Members.

Legrand activity records (calls, emails, meetings, tasks) export as individual text files per activity rather than threaded conversations. Mailchimp does not store a contact activity timeline; engagement data is limited to campaign-level opens, clicks, and unsubscribes generated within Mailchimp. We do not migrate activity history to Mailchimp. If the customer requires activity history, they should retain it in Legrand read-only or export it to a separate system before migration cutover.

Legrand Service Desk tickets are an add-on module with no Mailchimp equivalent. Mailchimp does not support a ticketing or support-case data model. We flag Service Desk as excluded from migration scope. Internal comments within tickets do not export via Legrand's standard Excel export path, as documented in the Legrand Cloud Knowledge Base, so even the raw ticket data is not fully extractable without a custom data pass that falls outside standard migration scope.

Legrand Asset Tracking is an add-on module storing serial number, linked customer, and service history records. Mailchimp has no asset or inventory data model. We flag Assets as excluded from migration scope and note that the customer should export the asset register separately if service history is required for compliance or warranty tracking. Asset-to-Customer linkage is not portable to Mailchimp.