Migrate from Legrand Cloud CRM to Odoo CRM

Legrand Account records map to Odoo res.partner with is_company = True. The company name, address fields, phone, website, and account type (Customer/Supplier/Partner) migrate directly. We use the Legrand AccountID as an external reference field (ref) in Odoo for traceability. parent_id is left null on Account records; child Contact records link to these Account partners via parent_id after the Account import completes. Legrand's account type values map to Odoo's partner_properties via a custom field or tag since Odoo does not have a native account_type comparable field.

Legrand Contact records map to Odoo res.partner with is_company = False and parent_id pointing to the Account partner created in the prior pass. Full name splits into firstname and lastname per Odoo's name_splitFields convention. Email, phone, mobile, job title, and role map to the corresponding Odoo partner fields. The Contact's parent Account reference is resolved by looking up the Legrand AccountID in the ref field we populated during the Account import pass. Any orphaned Contacts without a valid parent Account are held in a reconciliation queue for the customer to resolve.

Legrand Lead Inbox records (source=Lead) map to Odoo crm.lead with lead_type = lead. The Lead Inbox module captures name, email, phone, source, status, owner, and any custom lead fields. We map Legrand lead status values to Odoo stage names and preserve the original Legrand source value in a custom field x_legrand_source for reporting continuity. If the customer uses Legrand's lead scoring, that value migrates to a custom field x_legrand_lead_score on the crm.lead record.

Legrand Opportunity records map to Odoo crm.lead with lead_type = opportunity. Expected close date, probability (as a percentage mapped to crm.lead probability), and deal value (expected_revenue) migrate directly. Stage names from Legrand's pipeline map to Odoo stage names, and we pre-create the pipeline stages in Odoo before migration so that stage_name references resolve at import time. Owner assignment migrates by email lookup against Odoo res.users.

Each named pipeline stage in Legrand's Opportunities module becomes a crm.stage record in Odoo CRM. Stage sequence order, probability percentages, and is_won/is_lost flags are configured in Odoo before any lead or opportunity data imports. The Legrand pipeline name becomes the Odoo crm.team or a tag on the crm.lead if the customer uses multiple pipelines. We pre-register all stage mappings in a staging configuration file that is applied to the Odoo database before the production migration pass.

Legrand Sales Quotes (Cloud or On-Premise add-on at $16/user) map to Odoo sale.order records when the Odoo Sale app is active. Quote header fields (customer reference, validity date, payment terms) migrate as sale.order fields. Line items migrate as sale.order.line records with product, quantity, and price. Conversion status (draft/sent/accepted/rejected) maps to Odoo state (draft/sent/sale/lost). The Quote-to-Order linkage is preserved as a note field since the Odoo quote-to-order conversion action is a UI operation that occurs post-migration in the customer's Odoo instance.

Legrand Service Desk ticket records map to Odoo helpdesk.ticket when the Odoo Helpdesk app is active. Board assignment, ticket status, priority, age, and custom fields migrate directly. Linked Asset references from Legrand (if the Asset Tracking add-on is also active) map to maintenance.request records in Odoo with a ticket reference field. Note: Legrand's internal agent comments do not appear in the standard Excel export and require a separate comments report pass before migration cutover. We flag this as a supplemental data pass and treat it as a partial transfer, not a guaranteed 1:1.

Legrand Asset Tracking records map to Odoo maintenance.request when the Odoo Maintenance app is active. Serial number, linked customer (res.partner), and service history migrate as maintenance.request fields. Custom asset fields from Legrand map to custom fields on the maintenance.request model. The Asset-to-Ticket linkage is preserved as an x_legrand_asset_id text reference field since Odoo's Maintenance app does not natively link maintenance.requests to helpdesk.tickets without a custom field or module extension.

Legrand Campaign records (name, type, status, target member count) map to Odoo utm.campaign. Campaign member associations export as a separate sheet from Legrand and merge into Odoo's utm.membership or a custom campaign member model depending on whether the customer licenses the Odoo Marketing app. If Marketing is not active, we create a custom campaign member table (x_campaign_member) with lead/partner reference and membership status.

Legrand document files export as individual files per record rather than a contiguous folder archive. We script a bulk-rename pass to prefix each file with the parent record's Legrand ID (AccountID or ContactID) so that files can be associated to the correct res.partner or crm.lead during Odoo import. The folder hierarchy is not preserved by Legrand's export; we reconstruct it from document metadata where available. In Odoo, files attach to the parent record (res.partner or crm.lead) via ir.attachment with res_model and res_id fields set to the target model and record ID.

Legrand's Outlook and Gmail integration stores email threads and calendar entries that export as individual text files per activity rather than threaded conversations. We separate email bodies from attachments, ingest the email text as Odoo mail.message records linked to the res.partner or crm.lead, and attach files as ir.attachment. Calendar events migrate to mail.activity with activity_type_id set to the Odoo default Meeting type and ActivityDate matching the original Legrand timestamp. Meeting location and attendee list are stored as activity fields or custom fields since Odoo's native activity model does not include an attendee list without the calendar module.

Legrand custom fields per module (Accounts, Contacts, Opportunities, Lead Inbox) are audited during discovery. Each custom field is mapped to an Odoo ir.model.fields custom field on the corresponding model (res.partner or crm.lead). Field data type translation: Legrand text and textarea map to char or text; picklist maps to selection; date maps to date; number maps to float or integer; checkbox maps to boolean. We pre-create the custom field schema in Odoo before any data import so that the import pass includes the custom field columns. Custom field naming follows Odoo's x_ prefix convention for non-studio fields.

Legrand Owner (user) records referenced on Account, Contact, Opportunity, and Ticket exports are resolved by email match against Odoo res.users in the destination database. Any Legrand Owner without a matching Odoo user is placed in a reconciliation queue for the customer's admin to provision before the production migration pass continues. Owner assignment on crm.lead migrates as user_id in Odoo. This step gates the Opportunity and Ticket import phases since user_id is required on those models.