CRM migration
Field-level mapping, validation, and rollback between Legrand Cloud CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Legrand Cloud CRM
Source
Nutshell
Destination
Compatibility
6 of 11
objects map 1:1 between Legrand Cloud CRM and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from Legrand Cloud CRM to Nutshell is a transition from a dual-mode platform with no documented Cloud API to a SaaS-native CRM with documented API access. Legrand Cloud CRM exports records via a built-in Excel export and the browser-accessible data layer; Nutshell receives data through its REST API. The structural challenge is Legrand's lack of a public API, which forces us to work from exported spreadsheets rather than a direct data pull. We sequence the migration in dependency order (Accounts first, then Contacts with parent Account linkage resolved, then Opportunities, then Engagements), and we flag custom fields per module before import so that Nutshell's custom field schema is ready before any record lands. Workflows, Sequences, Service Desk add-ons, Asset Tracking, and Jobs modules do not migrate as automation code; we deliver a written inventory for the customer's admin to rebuild in Nutshell.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Legrand Cloud CRM object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Legrand Cloud CRM
Account
Nutshell
Company
1:1Legrand Accounts export cleanly via the built-in Excel export with standard address, type, and owner fields intact. We ingest Companies first in Nutshell so subsequent Person imports can reference the parent Company via the company_id field. The Account Name maps to Nutshell's name field, and Account type maps to a Nutshell custom text field if the customer requires type classification.
Legrand Cloud CRM
Contact
Nutshell
Person
1:1Legrand Contacts export with full name, email, phone, role, and parent Account linkage preserved in the CSV. We map the parent Account to Nutshell's company_id on the Person record during import. Nutshell's Person object supports name, email, phone, and custom fields. The Legrand Contact role field maps to a custom text field in Nutshell because Nutshell does not have a native role field on Person.
Legrand Cloud CRM
Lead Inbox
Nutshell
Lead
1:1Legrand's Lead Inbox module feeds into the same Contact object in Cloud CRM; we separate these records as distinct Leads in Nutshell during migration. Lead source, status, and owner fields map to Nutshell's lead_source, status, and assigned_to fields. Custom lead fields require manual field-level mapping during the Nutshell custom field schema setup phase before Lead import begins.
Legrand Cloud CRM
Opportunity
Nutshell
Deal
1:1Legrand Opportunities export with stage, value, expected close date, and owner assignment. We map Opportunity stage names to Nutshell pipeline stage values during the import transform. If Legrand uses custom stage labels that differ from Nutshell defaults, we create custom stage names in Nutshell before migration. Deal value and expected close date migrate as monetary_amount and close_date respectively.
Legrand Cloud CRM
Sales Quotes
Nutshell
Quote (via Deal attachment or custom object)
lossyLegrand Sales Quotes are an add-on module on On-Premise and export with line items, revision history, and conversion status. Nutshell does not have a native Quotes object; we migrate quote PDFs as file attachments on the corresponding Deal record and capture the quote body text as a Note on the Deal. The Quote-to-Order linkage does not transfer automatically; we document it for the customer's admin to rebuild in Nutshell.
Legrand Cloud CRM
Service Desk Tickets
Nutshell
Not migrated (separate helpdesk recommended)
lossyLegrand Service Desk is an add-on module with ticket boards, custom fields, and asset linking. Internal agent comments do not export via the standard Excel export, which means comment history cannot be guaranteed as a 1:1 transfer. We do not migrate Service Desk tickets as a standard object because Nutshell does not have a native service desk module. We deliver a written inventory of open tickets and a recommended helpdesk pairing (Zendesk, HubSpot Service Hub) for the customer's admin to evaluate.
Legrand Cloud CRM
Assets
Nutshell
Not migrated (rebuilt as custom object)
lossyAsset Tracking is a Legrand add-on module with serial number, linked customer, service history, and custom fields. Nutshell does not have a native Assets module. We migrate Asset records as a custom object in Nutshell if the customer requires asset data continuity, or we flag the asset inventory for manual re-entry if the record count is small. The Asset-to-Ticket linkage does not transfer; we document it as a rebuild item.
Legrand Cloud CRM
Documents
Nutshell
Files (on Company, Person, or Deal)
1:1Legrand Documents export as individual files per record rather than a contiguous folder hierarchy. We script a bulk-rename pass to preserve the ContactID or AccountID filename prefix so files can be associated to the correct parent record during Nutshell import. Folder structure is not preserved by the Legrand export tool; we reconstruct it manually from the metadata where filename patterns allow. Files attach to the corresponding Company, Person, or Deal record in Nutshell via the Files API.
Legrand Cloud CRM
Activities (Calendar/Emails)
Nutshell
Activities (via Nutshell API)
1:1Legrand email and calendar data from Outlook and Google integration export as individual text files per activity rather than threaded conversations. We separate email bodies from attachments, then push email content as Nutshell activities linked to the corresponding Person or Company record. Calendar entries migrate as activity records with date, duration, and type preserved. Attachment files re-attach to the parent activity record after the parent Person or Company is confirmed in Nutshell.
Legrand Cloud CRM
Campaign
Nutshell
Target List
lossyLegrand Campaign records export with name, type, status, and target member count. Campaign member associations export as a separate sheet. We map Legrand Campaigns to Nutshell Target Lists for email marketing purposes. If the customer uses Nutshell's marketing features, we deliver the campaign member list as a CSV for import into the corresponding Target List. Campaign member status and UTM source data migrate as custom fields on the Target List records.
Legrand Cloud CRM
Custom Fields (per module)
Nutshell
Custom Fields (on Company, Person, Lead, Deal)
lossyLegrand supports custom fields per module. Nutshell supports custom fields on Company, Person, and Lead objects. We audit the customer's Legrand custom field schema during discovery, then pre-create matching Nutshell custom fields with equivalent types (Text, Long Text, Currency, Date) before any record import. Custom fields that reference Legrand-specific objects (Assets, Service Desk) map to the corresponding custom object in Nutshell where applicable.
| Legrand Cloud CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Account | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Lead Inbox | Lead1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Sales Quotes | Quote (via Deal attachment or custom object)lossy | Mapping required | |
| Service Desk Tickets | Not migrated (separate helpdesk recommended)lossy | Mapping required | |
| Assets | Not migrated (rebuilt as custom object)lossy | Mapping required | |
| Documents | Files (on Company, Person, or Deal)1:1 | Mapping required | |
| Activities (Calendar/Emails) | Activities (via Nutshell API)1:1 | Mapping required | |
| Campaign | Target Listlossy | Fully supported | |
| Custom Fields (per module) | Custom Fields (on Company, Person, Lead, Deal)lossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Legrand Cloud CRM gotchas
No public API for Cloud CRM migration automation
Storage and record tier limits gate import scope on Cloud Starter
Attachment and email exports are per-record, not bulk
On-Premise migration and implementation costs are excluded from the per-user license
Service Desk internal comments do not export via standard Excel export
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Discovery and tier audit
We audit the source Legrand Cloud CRM portal for object counts (Accounts, Contacts, Opportunities, Leads, Quotes, Service Desk tickets, Assets, Documents, Activities), custom field schema per module, pipeline structure, and storage tier in use. We confirm whether the customer is on Cloud Starter, Cloud Business, or On-Premise, as tier determines export limitations. We also review Nutshell plan selection (Starter, Pro, Advanced) based on the customer's user count and feature requirements. The discovery output is a written scope with record counts per object and a custom field inventory for both platforms.
Manual export pass and data extraction
Because Legrand Cloud CRM has no public API, we coordinate with the customer's Legrand admin to run the built-in Excel export per module in dependency order: Accounts first, then Contacts, then Opportunities, then Lead Inbox, then subordinate objects. We provide a written export checklist specifying which fields to include and how to handle the parent Account linkage. For attachments and email files, we script a bulk-rename pass to preserve record IDs in the filename prefix. Service Desk tickets and internal comments are extracted via a separate comments report pass.
Nutshell custom field and pipeline configuration
We configure Nutshell's custom field schema before any record import. Based on the custom field inventory from discovery, we create matching custom fields on Nutshell's Company, Person, and Lead objects with equivalent field types. We also configure pipeline stage names to match the Legrand pipeline structure where possible. If the customer uses Legrand Sales Quotes, we configure the Nutshell Deals to accept quote file attachments. If Assets are in scope, we provision a custom Assets object in Nutshell before migration.
Test migration and reconciliation
We run a test migration into a Nutshell sandbox environment using a representative data sample (typically 10% of total records per object). The customer's admin reconciles record counts and spot-checks 20-30 records against the Legrand source. We validate that Company-to-Person linkage is intact, that Deal stage mapping is correct, and that custom field values transferred accurately. Any mapping corrections happen in this phase, not in production. Owner reconciliation identifies any Legrand users without a corresponding Nutshell user account.
Production migration in dependency order
We run production migration in record-dependency order: Companies first (from Legrand Accounts), then Persons (with company_id resolved to the imported Company), then Leads (from Legrand Lead Inbox), then Deals (with company_id and assigned_to resolved), then Activities (emails, calls, meetings as Nutshell activity records), then Documents (as file attachments), then Quotes (as file attachments on Deals), then any custom object records. Each phase emits a row-count reconciliation report before the next phase begins. We freeze Legrand writes during the production migration window to prevent delta records from being missed.
Cutover, validation, and automation rebuild handoff
After final delta migration of any records modified during the cutover window, we deliver the migration completion report including record counts per object, any records that could not be migrated with reason codes, and a list of unmigrated Service Desk internal comments. We deliver a written automation inventory document listing Legrand workflows, Service Desk boards, and any Jobs module records for the customer's admin to rebuild in Nutshell. We do not rebuild workflows, automations, or sequences as Nutshell equivalents inside the migration scope. We support a 5-business-day hypercare window for reconciliation issues raised by the customer's team.
Platform deep dives
Legrand Cloud CRM
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Legrand Cloud CRM and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Legrand Cloud CRM: Not publicly documented.
Data volume sensitivity
Legrand Cloud CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Legrand Cloud CRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Legrand Cloud CRM to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Legrand Cloud CRM
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.