CRM migration

Migrate from Legrand Cloud CRM to Nutshell

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 logo

Legrand Cloud CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

55%

6 of 11

objects map 1:1 between Legrand Cloud CRM and Nutshell.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Legrand Cloud CRM logo

Legrand Cloud CRM

What's pushing teams away

  • The user interface feels dated compared to modern SaaS CRMs, and customers report that aesthetic friction contributes to lower team adoption rates over time, especially onboarding new hires who expect a HubSpot-style experience.
  • No publicly documented API for Cloud CRM means automation is limited to Zapier integrations and the built-in browser export. Power users who want programmatic data access or custom sync logic find this a hard blocker.
  • On-Premise licensing costs are a surprise after the initial per-user quote — installation, configuration, data migration, third-party integration, and training are all priced separately on top of the subscription.
  • Storage tier limits on Cloud Starter (500MB, 10,000 records, 1,000 contacts) catch growing teams off guard, and upsell to higher tiers is not clearly communicated during onboarding.
  • Export limitations force manual workarounds for attachments and email threads — files export individually rather than as a structured archive, making large migrations time-consuming without a direct API.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Legrand Cloud CRM objects map to Nutshell

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

maps to

Nutshell

Company

1:1
Fully supported

Legrand 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

maps to

Nutshell

Person

1:1
Fully supported

Legrand 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

maps to

Nutshell

Lead

1:1
Fully supported

Legrand'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

maps to

Nutshell

Deal

1:1
Fully supported

Legrand 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

maps to

Nutshell

Quote (via Deal attachment or custom object)

lossy
Mapping required

Legrand 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

maps to

Nutshell

Not migrated (separate helpdesk recommended)

lossy
Mapping required

Legrand 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

maps to

Nutshell

Not migrated (rebuilt as custom object)

lossy
Mapping required

Asset 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

maps to

Nutshell

Files (on Company, Person, or Deal)

1:1
Mapping required

Legrand 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)

maps to

Nutshell

Activities (via Nutshell API)

1:1
Mapping required

Legrand 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

maps to

Nutshell

Target List

lossy
Fully supported

Legrand 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)

maps to

Nutshell

Custom Fields (on Company, Person, Lead, Deal)

lossy
Fully supported

Legrand 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.

Gotchas + challenges

What specifically takes care here

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 logo

Legrand Cloud CRM gotchas

High

No public API for Cloud CRM migration automation

High

Storage and record tier limits gate import scope on Cloud Starter

Medium

Attachment and email exports are per-record, not bulk

Medium

On-Premise migration and implementation costs are excluded from the per-user license

Low

Service Desk internal comments do not export via standard Excel export

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • No public API for Legrand Cloud CRM extraction

    Legrand Cloud CRM has no publicly documented REST or GraphQL API for automated data extraction or import. We work around this using the browser-accessible data layer and the built-in Excel export function, which requires a manual export pass per module. Customers expecting API-based migration tooling will not find it here. We sequence the export in dependency order (Accounts first, then Contacts, then Opportunities, then subordinate objects) and validate record counts against the export log after each pass. This export-first approach extends the migration timeline compared to API-driven sources.

  • Storage and record tier limits gate migration scope on Cloud Starter

    Legrand Cloud Starter caps at 1,000 Contacts, 10,000 Records, and 500MB of storage. Any customer migrating out of Legrand Cloud CRM on Starter will have already encountered these limits if their dataset exceeded them. We scope the migration volume during discovery and flag which object counts exceed the tier. If the customer is still on Starter and needs to migrate a larger dataset, they must upgrade or trim the dataset before we proceed. This is a source-side constraint, not a destination-side one.

  • Attachment and email exports are per-record, not bulk

    Documents and email threads export from Legrand as individual files per record rather than a contiguous archive. A Contact with 12 email attachments produces 12 separate download events. We script a bulk-rename pass to preserve the ContactID filename prefix so files can be associated to the correct parent record during import into Nutshell. The folder hierarchy is not preserved by the export tool; we reconstruct it manually from the metadata. This adds 1-3 days of preparation time per 10,000 attachments.

  • Service Desk internal comments do not export via standard Excel export

    The Legrand Cloud knowledge base documents a standard Excel export path for Service Desk tickets, but internal agent comments are stored in a separate data partition and do not appear in the standard export. We advise customers to run a separate comments report before migration cutover and treat comment history as a supplemental data pass rather than a guaranteed 1:1 transfer. We document this gap in the migration inventory and recommend a separate helpdesk migration or manual re-entry for high-priority ticket threads.

  • Nutshell has no native Quotes or Assets object

    Nutshell does not have a native Quotes object or an Assets module. Sales Quotes from Legrand migrate as file attachments on the corresponding Deal record, with quote body text preserved as a Note. Assets migrate as a custom Nutshell object if the customer requires asset data continuity, or are flagged for manual re-entry. Customers who rely heavily on Legrand's quoting or asset tracking features need to account for this schema gap during Nutshell configuration before migration begins.

Migration approach

Six steps for a successful Legrand Cloud CRM to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Legrand Cloud CRM logo

Legrand Cloud CRM

Source

Strengths

  • Outlook and Gmail email integration with CRM panel inside the email client keeps sales activity logged without copy-paste friction.
  • Deep accounting integrations with QuickBooks Online, XERO, MYOB, and QuickBooks Enterprise reduce dual-entry work for finance-adjacent teams.
  • Configurable per-module custom fields and pipeline stages let businesses model their exact sales process rather than bending to a fixed template.
  • Dual deployment options (Cloud for remote teams, On-Premise for data-sovereignty requirements) serve SMBs with mixed IT postures.
  • Service Desk and Asset Tracking add-ons give B2B companies a single system for pre-sale pipeline and post-sale support without buying a separate helpdesk.

Weaknesses

  • No publicly documented API for Cloud CRM limits automation to Zapier, email integration, or manual export workflows, which creates risk for growing teams that need programmatic data access.
  • User interface is described as dated and lacking the polish of modern SaaS CRMs, which affects team adoption and onboarding speed for new employees.
  • Storage and record limits on lower Cloud tiers (500MB, 10,000 records) constrain larger migrations and require careful scoping before any data transfer begins.
  • On-Premise pricing is opaque — the published per-user rate excludes installation, migration, integration, and training, which add significant project cost beyond the subscription.
  • Knowledge base and documentation are limited to basic export and field-add instructions; deep API references, schema diagrams, and migration playbooks are not publicly available.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Legrand Cloud CRM and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Legrand Cloud CRM: Not publicly documented.

  • Data volume sensitivity

    B

    Legrand Cloud CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Legrand Cloud CRM to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Legrand Cloud CRM to Nutshell data migrations

Answers to the questions buyers ask most during Legrand Cloud CRM to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between two and four weeks for accounts under 5,000 Contacts and 2,000 Deals with no Service Desk, Asset, or large attachment history. Migrations with large attachment sets (over 50,000 files), multiple Legrand pipelines, or the optional Jobs module move to four to eight weeks because of manual export sequencing, bulk-rename scripting, and Service Desk comment extraction. The Legrand export pass itself requires coordination with the customer's Legrand admin and adds 3-5 business days to the front of the timeline.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Legrand Cloud CRM.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day