Migrate from Legrand Cloud CRM to Microsoft Dynamics 365 Sales

Legrand Companies map directly to Microsoft Dynamics 365 Sales Accounts. The Company Name maps to Account Name; physical address fields (street, city, state, postal code, country) map to the corresponding Address composite on Account. Company Type (Customer, Prospect, Partner) maps to Account Type or a custom field depending on the customer's use of the standard Type picklist. We ingest Accounts first in every migration pass so that Contact imports can resolve the AccountId lookup at insert time rather than in a second patching pass.

Legrand Contacts map to Microsoft Dynamics 365 Sales Contacts with the parent AccountId resolved via the Contact's Company linkage in the Legrand export. Full name, email address, phone, mobile, job title, and role fields migrate directly. If the Legrand Contact has no linked Company, we create a placeholder Account and flag the contact for the customer's admin to reconcile the linkage post-migration. Duplicate detection runs on email address as the dedupe key after each import batch.

Legrand Leads in the Lead Inbox module map to Microsoft Dynamics 365 Sales Leads. Lead source, status, owner assignment, and any custom lead fields migrate directly. The Legrand Lead Status vocabulary is mapped to the Dynamics 365 Lead Status picklist (New, Contacted, Qualified, Unqualified) or preserved as a custom field if the customer's Legrand vocabulary is non-standard. Owner resolution runs by email match against the destination User table before import begins.

Legrand Opportunities (Pipeline records) map to Microsoft Dynamics 365 Sales Opportunities. Stage, estimated value, expected close date, and owner assignment migrate directly. Pipeline stage names from Legrand are preserved as text labels in a custom field if the Microsoft Dynamics 365 Sales Process stage vocabulary differs, and we configure a custom Sales Process and Record Type per Legrand pipeline during the schema pass. Closed-Lost and Closed-Won status migrate with the relevant date fields preserved.

Legrand Sales Quotes (add-on module on On-Premise; built-in on Cloud) map to Microsoft Dynamics 365 Sales Quote records. Quote line items, revision history, and conversion status (Draft, Sent, Accepted, Lost) migrate as QuoteLineItems and a custom revision number field. The Quote-to-Opportunity linkage migrates as a text reference field on Quote since the native LinkToEntity relationship requires an active Opportunity in Dynamics 365; we reconnect it during the post-migration reconciliation pass.

Legrand Service Desk Tickets map to Microsoft Dynamics 365 Sales Cases or Customer Service Cases depending on the destination license. Board assignment and status map to Case Record Type and Status respectively. Custom ticket fields migrate as custom Case fields. The Asset-to-Ticket linkage migrates as a text reference in a custom field until the Asset entity is provisioned in Dynamics 365. Internal agent comments do not appear in Legrand's standard Excel export; we run a separate comments extraction pass before cutover and merge the results into Case notes or a custom internal_comments__c field, flagging this as a partial-transfer item in the migration report.

Legrand Documents export as individual files per record rather than a contiguous folder archive. We run a bulk-rename pass to tag each file with the source record identifier (ContactID or AccountID prefix) before importing into Dynamics 365. Files are re-attached to the parent record using the regarding field on Note (for text-based documents) or as Attachments on the standard object (for binary files). The original folder hierarchy is not preserved by the Legrand export; we reconstruct it from document metadata where available.

Legrand's email and calendar integration exports activity records as individual text files per engagement. Email bodies migrate as Salesforce EmailMessage records linked to Tasks; call logs migrate as Tasks with TaskSubtype=Call; meeting records migrate as Events with start and end times preserved. We separate attachment files from email body text so that attachments land as ContentDocument records linked to the EmailMessage rather than as inline text. Activity ordering is preserved by setting ActivityDate to the original Legrand timestamp.

Legrand Campaigns map directly to Microsoft Dynamics 365 Sales Campaigns. Campaign name, type (Email, Event, Webinar, Trade Show), status, and target member count migrate as Campaign fields. Campaign member associations export as a separate sheet in the Legrand Excel export; we merge them into Dynamics 365 CampaignMember records during the import pass, resolving the Campaign and Contact/Lead references at insert time.

Legrand per-module custom fields migrate to Dynamics 365 custom fields on the equivalent entity (Account, Contact, Lead, Opportunity, Quote, Case). We pre-create the destination schema during the discovery pass, mapping each Legrand field type to the nearest Dynamics 365 type (text to Text, number to Number, date to DateTime, checkbox to Boolean, dropdown to Picklist). Custom fields with picklist-style values require a value mapping pass before import. The custom field audit is delivered as a written schema map included in the migration documentation package.