Migrate from OneHash CRM to Odoo CRM

OneHash Lead DocType maps directly to Odoo crm.lead with type=lead. We map lead_name to name, status to stage_id (with a stage-name map built from Odoo's default CRM stages), source to source_id, and notes to description. Custom fields on the Lead DocType migrate to custom crm.lead fields (ir.model.fields with model=crm.lead) created before import. Lead-to-Contact conversion linkage is preserved as a tag or note so the relationship is auditable in Odoo even though Odoo handles the conversion differently.

OneHash Contact records map to Odoo res.partner where is_company=False. We map first_name and last_name to firstname and lastname, email to email, phone to phone, and organization linkage to parent_id (pointing to the Customer partner record). Contact addresses nested within the Contact DocType in OneHash extract to separate res.partner address records linked via type (invoice, delivery, contact). OneHash contact custom fields map to res.partner custom fields.

OneHash Customer (organization-level) DocType maps to Odoo res.partner where is_company=True. The customer name maps to name, billing and shipping addresses map to child partner records with type=invoice or type=delivery, and any linked Contacts attach via child_ids. OneHash Customer custom fields (industry, annual_revenue, company_size) map to res.partner custom fields on the company partner.

OneHash Opportunity DocType maps to Odoo crm.lead with type=opportunity. The opportunity amount maps to planned_revenue, probability to probability (0-100 integer), stage to stage_id (via a stage-name map), party information to partner_id (res.partner lookup resolved after the Customer/Contact migration phase), and pipeline assignment to team_id. The pipeline stage ordering migrates via a stage-sequence map applied after the crm.lead import completes.

OneHash Quotation DocType maps to Odoo sale.order in state=draft (Odoo treats quotations as draft sale orders). Quotation line items (Items with pricing, tax templates, and quantities) map to sale.order.line with Product2 references resolved after the product catalog migration phase. Tax templates from OneHash map to Odoo account.tax. The quotation-to-opportunity linkage is preserved in sale.order.description as a reference tag since Odoo does not natively store the opportunity link on sale.order; this is documented in the migration inventory for the customer's admin to configure via Odoo's CRM link if needed.

OneHash Sales Order DocType maps to Odoo sale.order in state=sale (confirmed order). Order item rows map to sale.order.line with quantity, price_unit, discount, and tax resolved. OneHash order status flags (delivery status, billing status) have no direct Odoo equivalents on sale.order; we preserve these as custom fields so the customer's admin can map them to stock.picking state or account.move state post-migration if needed.

OneHash Item DocType maps to Odoo product.product. Standard fields (item_name to name, item_code to default_code, unit_of_measure to uom_id) migrate directly. Custom Item fields specific to the business (weight, dimensions, supplier, HS codes) map to product.product custom fields created before import. OneHash pricing data (price_list rates) maps to product.pricelist.item entries against the standard Odoo pricelist.

OneHash Project DocType maps to Odoo project.project. Project name, description, start and end dates, and status (open vs completed) migrate directly. Tasks within the project map to project.task with parent_id hierarchy preserved. Task assignees (Employee DocType references) map to project.task user_id via the Odoo User resolution pass. Open vs completed status is preserved; task comments map to project.task description notes.

OneHash Employee DocType maps to Odoo hr.employee. Designation maps to job_id (linked to hr.job), department to department_id (linked to hr.department), and compensation records to hr.contract on the employee. We preserve org-chart parent_id relationships and effective-dated contract records as a separate mapping layer. Employee custom fields migrate to hr.employee custom fields created in the destination Odoo database before import.

OneHash Chart of Accounts DocType maps to Odoo account.account. Account names, types (asset, liability, equity, income, expense), and parent-child hierarchy (parent_account) migrate directly. Account numbers are preserved in code where the destination supports them. This migration scope is scoped to the account master records only; Odoo requires chart of accounts initialization via the setup wizard which the customer's accountant completes; the migration provides the account list for manual entry or CSV import via Odoo's accounting setup.

OneHash custom DocTypes (ERPNext-style documents created via Customize Form) require schema discovery before mapping. We introspect each custom DocType's field definitions via the OneHash API during the discovery pass, then pre-create matching Odoo models (ir.model), fields (ir.model.fields), and menu items in the destination Odoo database. Custom DocType relationships to standard DocTypes (e.g., a custom field on Lead linking to a custom Customer extension) map to Odoo many2one or many2many fields created alongside the standard object mapping.

Documents attached to any OneHash DocType migrate as ir.attachment records in Odoo. We extract the binary blob, preserve the original filename, and link via res_model and res_id to the migrated parent record (crm.lead, res.partner, sale.order, etc.). Large attachments (over 10 MB) require chunked download from OneHash and chunked upload to Odoo. File storage backend in the destination Odoo instance (file on disk, S3, database) is confirmed during scoping so that the migration pipeline is configured correctly before attachments are processed.