Migrate from Relic ERP to Odoo ERP

Relic ERP Contact records map to Odoo res.partner with type='contact'. Name fields map directly; email maps to email, phone to phone, mobile to mobile. Address data maps to partner addresses via the res.partner address fields (street, city, state_id, country_id, zip). We apply deduplication by email during import. If Relic ERP distinguishes between person contacts and organizational contacts, person contacts map to type=contact and organizational records map to type=company (separate object mapping below).

Relic ERP Company or Account records map to Odoo res.partner with type=company. The company name maps to name, website to website, and industry classification to industry_id (Odoo's industry field). Any associated address data from the Relic ERP Company record maps to the company's contact address. Company contacts are created before person contacts so that the child_contact relationship to the parent company is satisfied at insert time.

Relic ERP Deal or Opportunity records map to Odoo crm.lead (Odoo's CRM lead/opportunity object). The deal name maps to name, deal value maps to expected_revenue, stage maps to stage_id (Odoo CRM stage), and owner maps to user_id. If Relic ERP has a separate pipeline concept, it maps to Odoo's crm.lead.team_id and pipeline_id fields. We set the lead_type to 'opportunity' for qualified deals. Lost reason and closed-won reason map to Odoo's lost_reason field if used.

Relic ERP Product or Item records map to Odoo product.template. The product name maps to name, SKU to default_code, and description to description. We determine the product type (service vs consumable vs stockable) from a Relic ERP product type field and set Odoo's type accordingly. If Relic ERP uses a separate price field, it maps to list_price. Barcode maps to barcode if present. Product categories map to product.category.

Relic ERP inventory records map to Odoo stock.quant for on-hand quantity tracking, linked to the product.template via product_id and to the stock.location via location_id. We identify the target Odoo warehouse from the Relic ERP inventory location, creating stock.location records if they do not exist. Initial stock levels are loaded as stock.quant records; ongoing transactions require mapping to stock.move or stock.picking depending on the transaction type.

Relic ERP Purchase Order records map to Odoo purchase.order. Vendor reference maps to partner_id (res.partner), order date maps to date_order, and PO number maps to name. PO lines map to purchase.order.line with product_id, product_qty, and price_unit resolved from the product.template mapping. If Relic ERP tracks PO status separately, it maps to state (draft, sent, purchase, done, cancel).

Relic ERP Invoice records map to Odoo account.move with move_type='out_invoice' for customer invoices and 'in_invoice' for vendor bills. Invoice number maps to ref, date to invoice_date, and amount to amount_total. Line items map to account.move.line with account_id resolved from the product-to-account mapping defined during schema scoping. Odoo's sequence-based naming for invoices is applied; original invoice numbers are preserved in the ref field.

Relic ERP Task or Project records map to Odoo project.project and project.task. Task name maps to name, description maps to description, due date maps to date_deadline, and assignee maps to user_id. If Relic ERP has a hierarchical task structure (parent task), we map it to Odoo's parent_id on project.task. Stage/status maps to stage_id within the Odoo project. Projects with no tasks create an empty project.project record; tasks without a parent project are placed in the default project or a migration holding project.

Relic ERP activity records (calls, emails, meetings, notes) map to Odoo mail.message linked to the relevant res.partner, crm.lead, or project.task via model and res_id. Email content maps to body (HTML), subject to subject, and date to date. Call duration and disposition are stored as custom message fields if present in the source. Meeting records with a time/date map to Odoo's calendar.event if the calendar module is installed; otherwise they land as mail.message records. We preserve the original activity timestamp for chronological accuracy.

Relic ERP custom objects or custom fields on standard objects require pre-migration compatibility review against the target Odoo version. We pre-create Odoo ir.model entries for each Relic ERP custom object, including all custom field definitions (char, float, integer, selection, many2one, one2many, many2many variants) using Odoo's fields metadata API. Custom field values migrate as typed data. Custom modules that define custom ORM methods or server actions require code review to port to Python Odoo module format; we flag these in the scope document and do not migrate them as data.

Relic ERP User or Employee records map to Odoo res.users. We match by email address as the dedupe key. Active/inactive status migrates directly. Groups and role assignments from Relic ERP map to Odoo res.groups membership; we resolve Odoo group ids from a role-mapping table defined during schema scoping. Any HubSpot or external system owner references are resolved to res.users by email lookup prior to record migration.

Relic ERP tax rates and fiscal configurations map to Odoo account.tax records. Tax name maps to name, rate (percentage) maps to amount, and tax type (inclusive/exclusive) maps to price_include. We create account.tax.group records to group taxes by jurisdiction if Relic ERP uses regional tax codes. VAT and GST codes map to description fields on account.tax. Fiscal positions (tax mapping by partner region) map to account.fiscal.position if the source has multi-jurisdiction tax handling.