Migrate from Legrand Cloud CRM to HubSpot

Legrand Accounts map directly to HubSpot Companies. HubSpot's Company object holds the company name, domain, industry, phone, address, and employee count. The Legrand Account's primary contact links to the HubSpot Company via the contact's primary association property. Multi-address accounts require address field mapping to HubSpot's address compound field.

Legrand Contacts migrate to HubSpot Contacts. The Contact record carries name, email, phone, job title, and the link to the primary Company. Legrand allows multiple contacts per account — HubSpot supports the same model. Each Legrand contact email is checked against HubSpot's existing contacts to prevent duplicate creation during migration.

Legrand's Sales Pipeline module contains named pipelines with configurable stages. Each Legrand pipeline becomes a HubSpot Deal Pipeline. The stage values from Legrand map to HubSpot Deal stage names under the target pipeline. We preserve stage order and probability values where Legrand exposes them, or use defaults if the source stage probabilities are not configurable.

Legrand opportunities (deals tied to a pipeline) map to HubSpot Deals. The Deal carries deal name, amount, close date, owner, and stage value. The HubSpot Deal is associated to the primary Contact and Company via the standard association model. Deal associations to multiple contacts map to HubSpot's deal-contact association list.

Legrand's Service Desk module — with its ticket boards, custom fields, and asset linking — maps to HubSpot Tickets. Each Legrand support ticket becomes a HubSpot Ticket object. Ticket status, priority, and custom field values map to HubSpot's ticket properties. Asset links from Legrand migrate as a custom ticket property referencing the asset name or ID.

Legrand's optional Jobs module has no direct HubSpot equivalent. Depending on how Jobs are used (service jobs, installations, recurring work), we recommend mapping them to either a HubSpot custom object or to Deals with a custom job-type property. The migration plan surfaces this decision before the full run.

HubSpot's engagement model covers calls, emails, meetings, and notes. Legrand's activity log entries (call logs, email logs, calendar events, tasks) map to their corresponding HubSpot engagement type. Each engagement preserves the original timestamp, owner, and the linked Contact or Company record.

Legrand documents stored against contacts or accounts migrate to HubSpot Files. The original file name and content type are preserved. Files are re-uploaded to HubSpot's file storage and linked back to the associated Contact or Company record via the file association model.

Legrand custom fields added to Account, Contact, Deal, or Service Desk modules create HubSpot custom properties. HubSpot auto-generates API names using underscores and lowercase. For pick-list custom fields in Legrand, we create HubSpot pick-list properties with the same value set. For date, numeric, and text custom fields, HubSpot property types are matched to preserve data type fidelity.

Legrand user accounts (owners of contacts, deals, and tickets) are matched to HubSpot users by email address. We resolve the owner lookup before migration and flag any Legrand user without a matching HubSpot user email. Unmatched owners are assigned to a fallback HubSpot user or left as a custom property value for manual resolution.

Legrand's Lead Inbox receives incoming leads before they are converted to Contacts or assigned to a Pipeline. Leads from the Inbox that have not yet been worked map to HubSpot Contacts with lifecyclestage set to 'lead'. Once a lead is assigned to a pipeline in Legrand, it routes to a HubSpot Deal and the contact lifecycle stage updates accordingly.

Legrand's Campaign module (email campaigns linked to MailChimp and Constant Contact) maps to HubSpot Campaigns. Campaign name, type, status, and member associations migrate to HubSpot's Campaign object. Note that HubSpot's campaign membership is tied to Contacts rather than Accounts, so the association model differs slightly from Legrand's implementation.

Legrand Sales Quotes (the add-on module) map to HubSpot Quotes where the Quotes feature is enabled. Quote name, line items, totals, and status migrate. Legrand's integration with accounting systems for real-time stock data has no HubSpot equivalent — the stock availability field is not migrated unless a custom property is used to store the last-fetched value.

Legrand's deep accounting integration with QuickBooks Online and XERO stores financial data and sync state in Legrand. HubSpot does not have a native accounting module. We do not migrate accounting data. Clients must maintain the QuickBooks or XERO connection in Legrand for historical reporting or establish a new integration between HubSpot and their accounting tool post-migration.