Migrate from Legrand Cloud CRM to Pipedrive

Legrand Account records map directly to Pipedrive Organization. The Account name, address fields, type, and owner assignment migrate as Organization name, address, type, and owner_id. Organization is created first in the import sequence so that subsequent Person imports can reference the parent org_id. The Legrand AccountID is preserved in a Pipedrive custom field for reconciliation.

Legrand Contact records map to Pipedrive Person. First name, last name, email, phone, role, and parent Account linkage migrate, with the parent Account resolved to a Pipedrive Organization org_id at migration time. Legrand's role field maps to a custom Person field in Pipedrive since the native Person object does not include a role/title field at the same level as Legrand.

Legrand's Lead Inbox module maps to Pipedrive Lead. Lead source, status, owner, and any custom lead fields migrate directly. Pipedrive Leads that convert to deals in the future will generate corresponding Person and Organization records automatically, which aligns with Legrand's behavior of linking incoming leads to an existing or new Account.

Legrand Opportunity records map to Pipedrive Deal. Pipeline stage names from Legrand migrate as Pipedrive stage labels within the destination pipeline. Deal value, expected close date, owner assignment, and associated Account reference all map directly, with the Legrand AccountId resolved to the Pipedrive Organization org_id during the transform phase.

Legrand's configurable pipeline stages and multiple pipeline support (on Business tier and On-Premise) map to Pipedrive Pipeline objects. Each Legrand pipeline becomes a Pipedrive pipeline with stages remapped. We preserve the stage probability percentages from Legrand as stage order weights in Pipedrive.

Legrand Sales Quotes (add-on at $16/user/month on On-Premise; included on Cloud Business) map to Pipedrive Proposals. Line items, revision history, and conversion status migrate. Pipedrive Proposals are linked to the originating Deal, and the Quote-to-Order linkage is preserved as a custom Deal field since Pipedrive does not have an explicit order-conversion object at the Essential tier.

Legrand Service Desk tickets (add-on at $15/user/month on On-Premise) map to Pipedrive Deals flagged with a custom ticket type, or to a separate custom object if the customer uses Pipedrive's Advanced Pipeline Customization add-on. Board assignment and ticket status map to Pipedrive stage and custom fields. Internal agent comments do not export via the standard Excel path and are handled as a supplemental export pass.

Legrand Asset Tracking records (add-on at $10/user/month on On-Premise) map to Pipedrive Products if the customer uses Pipedrive's product catalog feature, or to custom fields on the linked Organization record for serial number, service history, and warranty status. The Asset-to-Ticket linkage is preserved as a text reference field pointing to the migrated ticket ID.

Legrand Documents export as individual files per record rather than a folder hierarchy. We run a bulk-rename script to prefix each file with its parent Legrand record ID and type before loading into Pipedrive. Files are attached to the corresponding Pipedrive Person, Organization, or Deal via the Activity or file attachment API. The folder hierarchy is reconstructed from document metadata where available.

Legrand's Outlook and Gmail integration stores email threads and calendar entries as individual text files per activity. We separate email bodies from attachments, map email threads to Pipedrive Activities linked to the relevant Person or Organization, and map calendar entries to Pipedrive Activity records with start and end timestamps. Activity owner assignment resolves by email match to Pipedrive User.

Legrand Campaign records with name, type, status, and target member count map directly to Pipedrive Campaign. Campaign member associations migrate as a separate import pass after Person and Organization records are in place, linked by email match.

Legrand custom fields per module are audited before migration and mapped to Pipedrive custom fields on the equivalent object. Pipedrive supports custom fields on Person, Organization, Deal, Lead, and Activity from the Essential tier. Field types are mapped (text to text, number to number, date to date, dropdown to single-select picklist) and validated before the migration pass begins.