Migrate from LeadMaster to Odoo CRM

LeadMaster Leads map to Odoo crm.lead with type set to lead. The LeadCenter export fields (contact_name, email_from, phone, lead_source, lifecycle status, owner) map to Odoo's name, email_from, phone, source_id, team_id, and user_id respectively. Smart Queue filter criteria that define sub-segments of leads are documented as Odoo sales team filters or domain expressions for the customer to reproduce in Odoo Views. Owner assignment resolves via email match against res.users before import begins.

LeadMaster Accounts map to Odoo res.partner with company_type set to company. The primary contact link from the LeadMaster Account becomes a child res.partner contact of type contact under the company partner. Standard address fields (street, city, state, zip, country) map directly. Custom fields on the LeadMaster Account that have no Odoo equivalent fall back to a custom res.partner field created during schema setup or stored as a structured note attachment.

LeadMaster Opportunities map to Odoo crm.lead with type set to opportunity and a linked partner_id from the mapped Account. Stage, amount (planned_revenue), close date (date_deadline), and owner migrate directly. Custom pipeline stages on the LeadMaster side map to Odoo crm.stage values configured per sales team before migration. The split between what was a Lead versus an Opportunity in LeadMaster is preserved through the type field in Odoo.

Each LeadMaster Smart Queue or pipeline filter becomes an Odoo sales team (crm.team) with its own crm.stage list. Stage names and probabilities migrate as Odoo stage records attached to the team. If LeadMaster had multiple named pipelines, each maps to a separate crm.team in Odoo with its own stage sequence. We configure this during schema setup before any crm.lead records are imported.

LeadMaster Cases map to Odoo helpdesk.ticket if the Odoo Helpdesk app is active on the destination instance. Case number becomes ticket ticket_number or id; status, priority, and description map to stage_id, priority, and description respectively. The associated LeadMaster Account maps to the ticket's partner_id via res.partner lookup. Conversation threads attached to Cases migrate as message records on the helpdesk.ticket. If the Helpdesk app is not installed at migration time, Cases are held and the customer decides whether to install Helpdesk or skip Case migration.

LeadMaster user accounts, roles, and permission levels map to Odoo res.users by email match. Active/inactive status preserves. Any LeadMaster owner not found in Odoo's res.users table goes to a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId references on crm.lead, helpdesk.ticket, and ir.attachment cannot be resolved until this step is complete.

Logged calls, emails, meetings, and tasks from LeadMaster migrate as Odoo mail.message records on the crm.lead or res.partner, with message_type set to email, call, meeting, or notification respectively. Notes with no parent engagement type migrate as Odoo Note records via mail.message with note_flag set. Activity dates and subject lines preserve ordering in the Odoo chatter timeline. Email body content migrates as mail.message HTML body; attachments on activities migrate as ir.attachment linked via mail.message.ids.

File attachments stored against leads, accounts, cases, or opportunities in LeadMaster export as binary blobs with filename and parent record reference. We re-upload them to Odoo ir.attachment linked to the mapped res.partner, crm.lead, or helpdesk.ticket via res_model and res_id. Large-volume attachment exports may require chunked upload handling due to Odoo attachment size limits (default 25 MB per file, configurable). LeadMaster stores files in Azure; we extract them via API before migration and re-upload to Odoo.

LeadMaster marketing campaigns are documented as utm.campaign records in Odoo if the Marketing app is installed, or as crm.tag records on crm.lead if only the CRM app is active. Campaign contact associations migrate as tag mappings on the lead record. Email campaign content (templates, subject lines) exports as HTML and is provided as a file package; the customer rebuilds the campaign automation in Odoo Automated Actions or the Marketing app post-migration.

LeadMaster custom form field definitions and their submitted response data are exported during discovery. Form responses stored as lead or account data map to custom res.partner or crm.lead fields if the destination Odoo field type is compatible (text, date, selection). For non-standard field structures with no Odoo equivalent, we fall back to a structured ir.attachment JSON file or a multi-line text field that preserves the form payload. The form layout itself must be replicated in Odoo Studio by the customer's admin post-migration.

LeadMaster workflow automation (point-and-click rules for status updates, automated emails, calendar events, SMS, and record reassignment) has no export mechanism and cannot be migrated as executable logic. We document every active workflow during discovery with its trigger conditions, actions, and configured delays, and deliver a written inventory with recommended Odoo Automated Actions or Studio equivalents. The customer rebuilds these post-migration; this is a separate scope from the data migration.

LeadMaster landing pages (templates and form integrations) are documented during discovery with their field-to-lead routing logic. The page content exports as HTML, but the hosting and form-to-lead submission endpoint must be re-established in Odoo Website Builder or an external landing page tool post-migration. We provide a field-mapping table showing which Odoo form fields each LeadMaster landing page submitted to.