Migrate from ORCA Financial to Odoo ERP

ORCA Financial stores a flat or hierarchical chart of accounts with account codes, names, and types (Asset, Liability, Equity, Revenue, Expense). We extract the full COA as a structured table, map each account code to Odoo's account.type and account.code structure, and flag any custom segments such as cost-center or department splits. Odoo enforces country-specific localization on account types, so we validate the selected country localization during Odoo setup before importing account codes.

ORCA Financial customer records include name, billing address, payment terms, and contact info. We map these to Odoo Contact records with company_type set to company, extract related individual contacts as separate Contact records linked via Parent ID, and preserve payment terms in the property_payment_term_id field. Any custom fields on the ORCA Financial customer record that have no direct Odoo equivalent are flagged as manual configuration items in the handoff document.

ORCA Financial vendor records mirror customer records in structure. We map vendor name, address, and AP terms to Odoo Contact with company_type = company and the property_supplier_rank flag set. Remittance addresses and multi-site vendor records are flagged as requiring manual review post-import because Odoo handles multi-address vendor records through contact children rather than as a single record.

ORCA Financial items include SKU, description, unit cost, and warehouse location. We map these to Odoo Product records with the product type set based on the item tracking method in ORCA Financial (storable, consumable, service). The inventory valuation method (Standard, Average, FIFO) is extracted from ORCA Financial and applied to the Odoo product's property_cost_method and property_valuation fields. Stock quantities transfer as Odoo Inventory Quant records tied to the relevant warehouse location.

ORCA Financial warehouse location records define where inventory is physically stored. We migrate location codes and addresses to Odoo Stock Location records within the parent Warehouse location tree. Bin-level location assignments inside warehouses are flagged as a manual post-migration configuration step because ORCA Financial does not consistently expose bin-level data in its exports.

Open AP records from ORCA Financial include vendor name, invoice number, amount, and due date. We export these as a reconciliation-ready table and create Odoo Vendor Bills (Account Move with move_type = entry) for open items. Historical paid invoices are migrated as closed (posted) Account Move records with payment reconciliation noted. We do not reopen closed AP records; they remain in the source ORCA Financial archive for audit purposes.

Open AR records from ORCA Financial include customer name, invoice number, amount, and due date. We export these as a reconciliation-ready table for the AR team to verify post-migration. Unapplied payments and credit memos transfer as linked Account Move records (payments and credit notes respectively) with reconciliation links preserved. We migrate open AR as draft or posted invoices depending on the source record status in ORCA Financial.

ORCA Financial user accounts include name, email, and role. We export a user roster and map role names to Odoo's access rights groups (Sales, Accounting, Inventory User, etc.). Odoo's RBAC model differs significantly from ORCA Financial's, so the mapping is a best-effort translation based on the permission descriptions extracted from ORCA Financial. Any user without a clear role equivalent is assigned to the Internal User group with minimal access pending admin review.

ORCA Financial stores binary attachments against transactions and master records. We do not migrate attachments due to inconsistent storage formats and file-size constraints. We export a manifest of document filenames, parent record types, and record IDs so the customer's administrator can manually reattach critical documents post-migration if needed.

ORCA Financial may contain custom fields or properties on any master record (customer, vendor, item) that are not part of the standard schema. We extract the full field list during discovery and flag any custom properties that do not map to a standard Odoo field. The customer decides during scoping whether to recreate these as custom fields in Odoo (using Odoo's studio or the backend ORM) before migration begins, because custom field additions must be deployed before the corresponding data import.

ORCA Financial stores pricing at the item level. We extract all active price list entries as a structured table. Odoo supports multiple Pricelist records with time-based and quantity-based rules per product. We create an Odoo Pricelist from the ORCA Financial pricing data, mapping unit prices to product.list_price and creating Pricelist Item records for tiered or volume-based pricing. The customer selects which ORCA Financial price list becomes the default during scoping.