Migrate from Advantage HITS to Odoo CRM

Advantage HITS Contact records map to Odoo res.partner with type=contact. The partner's name splits from Advantage HITS firstname and lastname into partner's name field. Email, phone, mobile, job title, and address fields map directly. We preserve any custom contact properties as char or text fields on res.partner and create the corresponding ir.model.fields in Odoo before migration.

Advantage HITS Company records map to Odoo res.partner with type=company and company_type=company. The parent_id relationship to child Contact partners is preserved where the source defines it. Company domain maps to website, industry to industry_id (mapped to Odoo Industry list), and employee count to employee_count.

Advantage HITS Deal records map to Odoo crm.lead. The deal name becomes crm.lead name, deal amount maps to expected_revenue, close date maps to date_deadline, and owner assignment maps to user_id via email resolution. We pre-create crm.stage records before deal import so that stage assignment is satisfied as a many2one reference.

Each Advantage HITS pipeline definition (stage names, order, win/loss flags) becomes a crm.stage record in Odoo. The stage sequence, name, and is_won/is_lost flags configure in Odoo before deal import. We create a separate stage per pipeline using a naming convention (pipeline_name | stage_name) and map deal records to the correct stage by resolved pipeline+stage name crosswalk.

Advantage HITS free-text stage names require explicit crosswalk mapping because the source does not assign stable stage IDs. We export the full pipeline definition (all stage names and their order), build a lookup table keyed by pipeline_name plus stage_name, and resolve each deal's stage assignment at migration time. Any deal referencing a stage name not in the exported definition is flagged for manual stage reassignment before migration begins.

Advantage HITS engagement records (emails, calls, meetings, notes, tasks) map to Odoo mail.message records for content and mail.activity records for scheduled follow-up tracking. The res_model on mail.message points to crm.lead or res.partner; the res_id points to the migrated record ID. Activity timestamps and owner assignments migrate with 1:1 fidelity.

Advantage HITS Owner records (name, email, role, active/inactive status) map to Odoo res.users by email match. We extract every distinct owner referenced on Contact, Company, Deal, and Activity records and reconcile against the destination Odoo instance's users. Owners without a matching res.users record are held in a reconciliation queue; the customer's Odoo admin provisions the user before record import resumes.

Any user-defined fields on Advantage HITS Contacts, Companies, or Deals are enumerated from the UI field metadata panel. We create matching custom fields on the corresponding Odoo model (res.partner or crm.lead) using Odoo Studio or direct ir.model.fields API, preserving field type (char, text, integer, float, date, selection). Values migrate as text for selection fields if the picklist is not pre-built in Odoo.

Advantage HITS tags on Contacts, Companies, and Deals export as tag name lists per record. We create crm.tag records in Odoo for each unique tag name, then generate crm.lead.tag.rel records to link migrated deals to their tags. Contact and Company tag assignments migrate to res.partner.category_id (which uses crm.tag as its backend model in Odoo CRM).

File attachments linked to Contact, Company, or Deal records in Advantage HITS are downloaded using authenticated session requests, preserving original filenames and MIME types. We re-upload them to Odoo via the ir.attachment API with res_model pointing to the migrated record (crm.lead or res.partner) and res_id pointing to the new Odoo record ID. Attachments exceeding 50 MB per file are flagged for manual handling to avoid session timeout during extraction.

Advantage HITS lifecycle stage values (new, contacted, qualified, lost, won, and any customer-defined stages) map to Odoo crm.stage records with the corresponding category column. Stages with category=lost become is_won=false with is_lost=true in Odoo. Stages with category=won become is_won=true. We preserve the original Advantage HITS stage name in a char field on crm.lead for audit.

Advantage HITS does not publish a custom object API or schema, and bespoke data structures built in the UI are not programmatically enumerable. Any custom objects in the source are flagged during discovery, documented in the migration inventory, and excluded from the automated migration scope. The customer rebuilds these as Odoo custom models (ir.model, ir.model.fields) post-migration if needed.