Migrate from Legrand Cloud CRM to Salesforce Sales Cloud

Legrand Company records map directly to Salesforce Account. The CompanyName becomes Account Name; address fields map to BillingAddress and ShippingAddress. Company Type (if configured) maps to Industry or a custom Account Type picklist. Account is the first object we import because Contacts, Opportunities, and most activity records have a required lookup to it. The Legrand CompanyID is preserved in a custom field lcrm_company_id__c for reconciliation.

Legrand Contact records map to Salesforce Contact with AccountId resolved from the parent Company lookup. Name, email, phone, role, and address fields map directly. We map Legrand's Role field to Salesforce Title. If a Legrand Contact has no parent Company, we create a placeholder Account or place the Contact in a holding queue for the customer admin to resolve before migration continues.

Legrand's Lead Inbox module maps to Salesforce Lead. Lead source, status, owner assignment, and any custom fields migrate directly. We preserve Legrand lead scores and lead status values in custom Lead fields lcrm_lead_score__c and lcrm_lead_status__c so that the customer's sales process continuity is auditable after cutover.

Legrand Opportunity records map to Salesforce Opportunity. Stage, value, expected close date, owner, and pipeline assignment migrate. Legrand pipeline stage names map to Salesforce StageName via a translation table we configure in the destination org's Sales Process before migration. Closed-Lost and Closed-Won statuses preserve any Legrand close notes in custom Opportunity fields.

Each Legrand pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists only the relevant stage values. Stage probability percentages migrate from Legrand to Salesforce StageProbability. The customer chooses whether to preserve Legrand's exact stage vocabulary or adopt Salesforce's standard stage names during scoping.

Legrand Sales Quotes (add-on at $16/user/month on On-Premise; built-in on Cloud tiers above Starter) map to Salesforce Quote, which is available from Professional tier. Quote headers, line items, revision history, and conversion status migrate. Quote-to-Order linkage (if Legrand Quotes have been converted to Orders) maps to Salesforce Opportunity as a custom field. The customer must enable Quotes in Salesforce Setup before we begin this pass.

Legrand Service Desk tickets map to Salesforce Case if the destination org includes Service Cloud or if the customer enables Cases in Sales Cloud. Ticket board, status, age, and custom fields migrate. Linked Asset references become Case Asset lookups. Internal agent comments do not export via Legrand's standard Excel export and require a separate supplemental report run by the customer's admin before migration cutover; we flag this in the discovery output and treat comment history as a partial transfer.

Legrand Asset records (serial number, linked customer, service history, custom fields) map to Salesforce Asset. The Asset-to-Ticket linkage migrates as a Case Asset lookup if Cases are in scope. Asset status and type fields map to Salesforce Asset Status and Asset Type picklists.

Legrand Documents export as individual files per record rather than a contiguous folder structure. We script a bulk-rename pass to preserve the Legrand record ID in the filename so that files can be associated to the correct parent Salesforce record (Account, Contact, Opportunity, or Case) during import. The folder hierarchy is not preserved by Legrand's export; we reconstruct it by mapping document names to their parent record metadata. Files migrate to Salesforce ContentVersion with ContentDocumentLink records pointing to the parent.

Legrand's Outlook and Gmail integration stores email threads and calendar entries per contact. Emails export as individual text files per activity. We separate email bodies from attachments and map them to Salesforce EmailMessage records linked to the parent Contact or Lead. Calendar entries map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendee resolution links EventRelation records to the migrated Contact or Lead IDs.

Legrand Campaign records (name, type, status, target member count) map to Salesforce Campaign. Campaign member associations export as a separate sheet in Legrand and merge into Salesforce CampaignMember during import. We preserve member status and any campaign-specific custom fields.

Legrand per-module custom fields map to Salesforce custom fields (with __c suffix) on the equivalent standard or custom object. We audit the customer's Legrand custom field schema during discovery, map each field to a typed Salesforce field (text, picklist, number, date, checkbox, etc.), and create the Salesforce fields in a Sandbox org before production migration. Legrand's field-level validation rules do not exist as a configurable object and are not migratable; we document them for the customer's admin to re-implement in Salesforce validation rules post-migration.

The optional Jobs module on Legrand Cloud CRM exports records with status, assigned user, and linked customer. We map Job status to a Salesforce custom object Job__c or to the standard Project object if the customer has Salesforce Field Service or a project management add-on. The mapping is decided during scoping based on the destination org's installed packages.

Legrand Owner records map to Salesforce User by email match. Any Legrand Owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId is required on Opportunity and is validated during the import phase.