Migrate from LeadSmart Channel Cloud to Odoo CRM

LeadSmart Accounts map to Odoo res.partner records with partner_type = 'contact' and is_company = True. The manufacturer-distributor-dealer hierarchy uses parent_id to model the manufacturer-to-distributor and distributor-to-dealer relationships, preserving the multi-level hierarchy. We use the Account Name as the company name and map Industry and Account Type to custom partner_tag fields in Odoo. Dedupe is by company name and domain.

LeadSmart Contacts map to Odoo res.partner records with partner_type = 'contact' and is_company = False, linked to their parent Company record via parent_id. LeadSmart's industry-specific custom fields (distributor relationship type, dealer classification) map to Odoo custom Char or Selection fields on the contact form. We resolve parent_id before contact import so that Account-Contact relationships are satisfied at insert time.

LeadSmart Leads map to Odoo CRM crm.lead records with type = 'lead'. The LeadSmart lead status maps to Odoo stage_id (Prospecting, Qualification, etc.), and LeadSmart's Lead Source maps to Odoo's source_id. Any custom lead scoring fields from LeadSmart map to Odoo custom fields on crm.lead. Active LeadSmart Leads are imported first; converted Leads (if any were converted before migration) are handled as described in the Contact mapping.

LeadSmart Opportunities map to Odoo CRM crm.lead with type = 'opportunity'. The Opportunity name becomes the crm.lead name field. LeadSmart's pipeline stage and probability map to Odoo stage_id and probability. Closed-Won and Closed-Lost dates migrate. The Opportunity Partner (if assigned) maps to Odoo's partner_id on the opportunity record. Record type mapping is handled via Odoo's team_id and stage_id configuration before migration.

LeadSmart Opportunity Stage values map to Odoo crm.stage records within the relevant sales team. We preserve stage probability percentages as stage_requirements or probability fields on each stage. If LeadSmart uses custom stage naming (e.g., channel-specific names like 'Dealer Review' or 'Distributor Approval'), we create matching Odoo stage records with the same sequence order so that existing pipeline reporting translates directly.

LeadSmart Tasks migrate to Odoo mail.activity records linked to the parent crm.lead (for leads and opportunities) or res.partner (for contacts). Activity type (task, call, email) maps to Odoo's activity_type_id, and the LeadSmart activity date becomes the Odoo date_deadline. Completed status, priority, and description transfer to custom fields on the mail.activity record.

LeadSmart Events (meetings) migrate to Odoo calendar.event records. Start and end datetime, location, and meeting subject transfer directly. Attendees (LeadSmart contacts or leads associated with the event) map to calendar.event attendee records (partner_ids) by resolving the LeadSmart contact or lead to the corresponding Odoo res.partner or crm.lead.

LeadSmart Campaigns map to Odoo utm.source records (for campaign tracking attribution) combined with crm.tag records for campaign membership. Campaign Member status (Sent, Open, Clicked, Converted) is preserved in a custom field on the related Lead or Contact record rather than as a native Odoo object, since Odoo's CRM does not have a native Campaign Member equivalent.

LeadSmart Partner Portal external users (reps, brokers, dealers, distributors with external login access) map to Odoo res.partner contact records with a partner_type classification tag and country, region, and partner_grade custom fields. Odoo does not have a Partner Portal equivalent with external user login and sharing rules, so we map the partner relationship to contact records and flag that portal login access requires a separate authentication configuration in Odoo (potentially via Odoo Website partner portals or a custom partner portal module). We do not migrate the Partner Portal sharing rules themselves as Odoo handles access differently.

LeadSmart internal User records map to Odoo res.users by email match. We resolve every LeadSmart Owner referenced on Contact, Account, and Opportunity records to the corresponding Odoo user before record import so that OwnerId references are satisfied. LeadSmart Partner Portal external users do not map to Odoo res.users (they map to res.partner contacts as described above). Users without a matching Odoo account are held in a reconciliation queue for the customer's admin to provision.

LeadSmart Files and Attachments linked to Leads, Contacts, Accounts, and Opportunities migrate as Odoo ir.attachment records with res_model pointing to the target model (crm.lead or res.partner) and res_id pointing to the target record ID. Binary file content transfers via base64 encoding. We resolve parent record IDs before attachment import so that linkage is preserved. Large binary attachments may require chunked transfer with Odoo's XML-RPC file handling.

LeadSmart Genius Feed AI-generated customer issue and growth opportunity records are stored in a proprietary format tied to LeadSmart's recommendation engine. These do not have equivalents in Odoo CRM's data model and the underlying AI logic does not transfer. We document these as excluded from scope with explicit customer sign-off before migration begins. The underlying Lead, Contact, and Opportunity data that Genius Feed references migrates normally.

Genius GPT stores AI-generated sales strategy recommendations in a proprietary format tied to LeadSmart's internal recommendation engine. These records are not portable and are documented as excluded from scope with customer sign-off before migration begins. We flag that Odoo's AI capabilities (available in Odoo Enterprise) provide different recommendation models and must be reconfigured independently by the customer's Odoo administrator.

LeadSmart adds industry-specific custom fields to standard Salesforce objects for distributor and manufacturer relationships. We inventory all custom fields during scoping, map them to Odoo custom fields on the equivalent model (crm.lead for lead/opportunity fields, res.partner for contact/account fields), and pre-create the destination schema before data import. Custom field types are mapped: Salesforce Text becomes Odoo Char, Salesforce Number becomes Odoo Float or Integer, Salesforce Date becomes Odoo Date, Salesforce Picklist becomes Odoo Selection. Fields with no Odoo equivalent are flagged for post-migration review.