Migrate from Tranquil ERP to Odoo ERP

Tranquil's account hierarchy maps to Odoo's Account chart with the full tree structure preserved. We extract parent_id, code, name, and the account type (asset, liability, equity, revenue, expense) and map them to Odoo's account.account model. Analytical accounts in Odoo are a separate dimension; we evaluate whether Tranquil's cost center or department tags serve as analytical account candidates during scoping. Fiscal position mappings for tax handling also transfer as res.fiscal.position records if defined in Tranquil.

Tranquil Customer records (name, email, phone, billing address, shipping address, payment terms, GST or tax ID) map to Odoo res.partner records with customer_rank set to 1 and the address stored in the standard contact fields. Payment terms migrate as res.payment.term records with matching day definitions. Open AR balances are preserved as account.move (invoice) records linked to the partner. Tranquil's customer-specific pricing rules map to Odoo pricelist entries on the partner if present.

Tranquil Vendor records map to Odoo res.partner with vendor_rank set to 1. Bank details, payment terms, and WHT or TDS tax configurations transfer as partner bank records (res.partner.bank) and fiscal position entries. Vendor-specific purchase prices migrate as purchase pricelist rules on the partner record. Accounts payable open balances are preserved as vendor bill (account.move with move_type=in_invoice) records.

Tranquil Item records with SKU, name, description, unit of measure, cost price, and sale price map to Odoo product.product. Multi-UoM configurations (common in Tranquil's inventory module) map to Odoo's uom.uom model with the category hierarchy preserved. Serial and batch number settings migrate as tracking=serial or tracking=lot on the product. Expiry date configuration transfers as expiration_time in days. Tranquil item categories map to Odoo product.category for hierarchical grouping.

Tranquil Purchase Orders with supplier reference, line items, quantities, unit prices, and status flags map to Odoo purchase.order. Vendor lookup resolves via the res.partner mapping. Order lines reference product.product via the item mapping. Open POs migrate with state=purchase; closed POs migrate as confirmed orders or with state=done to preserve fulfillment history. Tax rates on PO lines are mapped using Odoo's account.tax records resolved by rate and tax type.

Tranquil Sales Orders with customer reference, line items, pricing, taxes, and fulfillment status map to Odoo sale.order. Customer lookup resolves via the res.partner mapping. Order lines reference product.product. Closed or fulfilled orders migrate with state=sale or state=done. Tranquil's pricing rules and discount structures on sales orders map to Odoo's pricelist and discount fields on order lines.

Tranquil's current stock levels by warehouse, serial number, batch number, and expiry date map to Odoo stock.quant records with location resolved to the destination warehouse. Each warehouse in Tranquil becomes a stock.location in Odoo's location tree (view location with child stock locations per warehouse). Serial and batch numbers are stored as stock.lot records linked to the quant. Inventory valuation amounts are cross-checked against Odoo's stock.valuation.layer for reconciliation.

Tranquil HR Employee records (personal details, role/department, compensation, employment status) map to Odoo's hr.employee model. Department assignments map to hr.department. Effective-dated compensation fields (salary, allowances) transfer as hr.contract records linked to the employee. Employee status (active/inactive) is preserved. Odoo's HR module also requires a linked resource.calendar and user_id if the employee needs system login access.

Tranquil custom fields on Customers, Vendors, Items, and Orders are detected during discovery and mapped to Odoo custom fields on the equivalent model. We use Odoo Studio or direct ORM column creation to provision the destination field with the correct type (char, selection, float, date, many2one) before importing. Custom field values are included in the main object import CSV or JSON payload with the destination field name as the target column.

Closed purchase invoices in Tranquil that represent historical accounts payable map to Odoo account.move records with move_type=in_invoice, linked to the vendor partner and the corresponding purchase order if one exists. Payment state (paid/unpaid) is set via the reconcile field on related account.move.line records. Tax amounts are mapped to Odoo's account.tax records.

Closed sales invoices in Tranquil map to Odoo account.move records with move_type=out_invoice, linked to the customer partner. Payment state is preserved via reconciliation on account.move.line. Invoice line taxes are mapped to Odoo account.tax records by rate and type. The invoice number from Tranquil is stored in the Odoo move's ref field for traceability.

Tranquil serial and batch number registers map to Odoo stock.lot records per product. The lot name, product_id, company_id, and expiration date transfer. Lot records are imported before quant records so that the lot reference is satisfied at quant insert time. If Tranquil stores lot-specific cost or supplier information, we create a custom lot field or store it on the linked stock.move.line.