Migrate from Legrand Cloud CRM to HighLevel

Legrand Companies map to GoHighLevel Companies. We export the Companies module first because Contacts have a required parent-account linkage. Company name, address fields, type, and owner assignment transfer directly. GoHighLevel's Company import requires the API or CSV upload with the Company Name as the dedupe key; we set the import order so Company records are confirmed before any Contact batch begins.

Legrand Contacts map to GoHighLevel Contacts. The parent-company linkage (CompanyID or company name) resolves to the GoHighLevel Company record via lookup at migration time. We preserve full name, email, phone, role, and any custom contact fields by pre-creating matching GoHighLevel Contact custom fields before the import pass. Tags in GoHighLevel replace Legrand's contact category labels if the customer uses a tagging taxonomy.

Legrand Opportunities map to GoHighLevel Opportunities. Stage, deal value, expected close date, and owner assignment transfer directly. GoHighLevel pipeline stages must be pre-created in the destination account before import; we configure the pipeline with stages named to match Legrand's stage vocabulary or map them to the customer's preferred GoHighLevel stage names. Owner resolution uses email matching against GoHighLevel Users.

Each Legrand Opportunity stage becomes a GoHighLevel Pipeline Status value. Probability percentages from Legrand transfer as metadata on the status; GoHighLevel does not enforce stage probability the way Salesforce does, but we populate the field for any reporting the customer builds. Stages are created before any Opportunity import so the import can reference valid status IDs.

Legrand's Lead Inbox module stores unqualified prospects. We split leads by status at migration time: leads with a status indicating they progressed to a sales-qualified stage map to GoHighLevel Opportunities, while unqualified inbound leads map to GoHighLevel Contacts tagged with a lead source field. Custom lead fields from the Inbox module require matching GoHighLevel Contact custom fields pre-created before import.

Legrand's Jobs module (Cloud Professional and above) tracks flat-rate or hourly services. We map Job status to GoHighLevel Opportunity stage or a custom Job status field depending on the customer's usage. If the customer tracks jobs as a distinct record type from sales pipeline opportunities, we create a GoHighLevel Custom Object with status and linked customer fields. Job billing data (hours, rate) migrates as custom numeric fields on the mapped object.

Legrand Service Desk tickets map to GoHighLevel Contacts with a note capturing ticket details (board, status, custom fields, linked asset). Internal agent comments do not appear in Legrand's standard Excel export and require a separate comments report pass. We flag this in the discovery phase and include the internal comments as a supplemental data pass with a flag in GoHighLevel noting the comment origin. GoHighLevel does not have a native ticketing board equivalent; the customer rebuilds the board view using Pipeline status and custom fields.

Legrand Asset Tracking (add-on module) maps to a GoHighLevel Custom Object named Assets with fields for serial number, linked customer, service history, and any custom asset fields. The Asset-to-Ticket linkage in Legrand becomes a text reference field in GoHighLevel because GoHighLevel Custom Objects do not natively support cross-object lookup the way Legrand's Asset-to-Ticket link does.

Legrand Documents export as individual files per record rather than a folder archive. We script a bulk-rename pass to add the parent record identifier to each filename so files can be associated to the correct Contact during import. GoHighLevel stores files as attachments on the relevant record; we upload them via the API after the parent Contact or Company record exists. Folder hierarchy is reconstructed from the document metadata rather than imported directly.

Legrand email threads and calendar events export as individual text files per activity rather than threaded conversations. We separate email bodies from attachments, map email body content to GoHighLevel Notes on the Contact record, and link attachments separately. Calendar events from the Legrand Calendar module migrate as GoHighLevel Tasks with the appointment time preserved in the task due date field and a note body capturing the event description.

Legrand custom fields per module require individual mapping to GoHighLevel Contact custom fields or Opportunity custom fields. We audit the customer's Legrand custom field schema during discovery, then pre-create the equivalent GoHighLevel fields before any data import. GoHighLevel does not allow field type changes after creation; we confirm the field type with the customer before creating. Fields that exist on both Contact and Opportunity in Legrand must be created twice in GoHighLevel under each object type.