Migrate from Legrand Cloud CRM to Twenty CRM

Legrand Account records export cleanly via the built-in Excel export with standard address, type, and owner fields intact. We ingest Companies first in Twenty so that subsequent People imports can resolve the CompanyId lookup. Legrand's Account type (Customer, Prospect, Partner, Competitor) maps to Twenty's Company domain field, and the Account phone number maps to Company phone. Account addresses split into street, city, state, country, and postal code fields per Twenty's structured address schema.

Legrand Contact records map directly to Twenty People. The CSV preserves the parent Account linkage, which we resolve to the Twenty CompanyId lookup at migration time. Legrand's role and title fields map to Twenty's jobTitle and companyName (if the contact record holds a different company from the linked Account). Email uniqueness is enforced in Twenty during import so we deduplicate by email before insertion.

Legrand's Lead Inbox module maps to Twenty People with a custom field legrand_lead_source__c carrying the original lead source value. Lead status from Legrand (New, Contacted, Qualified, Disqualified) maps to Twenty's opportunities with a custom status field. Unqualified leads land as Twenty People records without an associated Opportunity; qualified leads that have moved to a pipeline stage create a linked Opportunity in Twenty.

Legrand Opportunity records map to Twenty Opportunity. The pipeline stage name from Legrand becomes a custom stage value in Twenty's Opportunity stage field, and we note that Twenty does not ship with an automated incremental numbering system for Opportunity IDs — teams expecting auto-generated deal numbers from Legrand must configure a custom numbering approach in Twenty or accept manual entry. Stage probability percentages migrate as custom fields since Twenty's standard Opportunity object does not include probability by default.

Each Legrand pipeline becomes a Twenty Opportunity with stage values defined in Settings Data Model before import. We create stage picklist values matching the Legrand stage names so that historical stage names are preserved and teams can report on the original pipeline labels in Twenty reporting.

Legrand's email and calendar integration exports as individual text files per activity rather than threaded conversations. We split email bodies into Twenty Note records (the actual content) and Task records (the activity timeline entry) linked to the parent People or Company record. Call disposition, duration, and meeting details migrate as Task records with the appropriate activity type marker. The split preserves the activity timestamp for timeline ordering.

Twenty's CSV import documentation explicitly states that file attachments are not included in exports and must be re-uploaded manually or migrated via API. Legrand exports documents as individual files per record with the ContactID filename prefix. We script a bulk-rename pass to reconstruct the parent record association from filenames, then deliver the organized file set alongside the migration so that the customer's admin can re-upload via Twenty's file attachment UI or API. The folder hierarchy is not preserved by Legrand's export; we reconstruct it from metadata where available.

Legrand Service Desk tickets (an add-on module at $15 per user per month on On-Premise) map to Twenty Task records with a custom ticket status field or to a custom ServiceTicket object if the customer has configured one. Ticket board assignment becomes a custom picklist value, and ticket age and custom fields migrate as custom fields on the target object. Internal agent comments do not export via Legrand's standard Excel export; we flag this gap and recommend a separate comments report run before migration cutover.

Legrand Sales Quotes (an add-on at $16 per user per month on On-Premise; available on Cloud with line items and revision history) map to a custom Quote object in Twenty. Quote-to-Order linkage is preserved as a custom text field. The conversion status and revision number migrate as custom fields on the Quote object since Twenty's standard Opportunity object does not include a native quote module.

Legrand Asset Tracking (an add-on at $10 per user per month on On-Premise) maps to a custom Asset object in Twenty. Serial number, linked customer, service history, and custom fields migrate as structured fields on the custom object. Asset-to-Ticket linkage is preserved as a text reference field pointing to the migrated Service Desk ticket identifier.

Legrand Campaign records export with name, type, status, and target member count. Campaign member associations export as a separate sheet. We create a custom Campaign object in Twenty and map member associations to CampaignParticipant records linked to the Campaign custom object. Campaign member status (Sent, Responded, Opted Out) migrates as a custom status field.

Legrand's optional Jobs module (Cloud CRM and add-on on On-Premise) maps to a custom Job object in Twenty with status, assigned user, and linked customer as structured fields. Job status values migrate as picklist values in Twenty's custom object definition. The Jobs module is the least common add-on and customers without it have no Jobs object to migrate.