Migrate from Adaptive to Odoo ERP

Adaptive Customer records (name, address, contact details, tax ID) map to Odoo res.partner records with type=contact and customer_rank set to distinguish from supplier records. Linked delivery and billing addresses migrate as child res.partner records with address_type set to delivery or invoice. Tax registration numbers map to res.partner vat field. We resolve parent-company relationships via Adaptive's customer hierarchy and create top-level company partners with child contact records in Odoo.

Adaptive Supplier records mirror Customer structurally and map to Odoo res.partner with supplier_rank set and customer_rank cleared. Payment terms and bank details from Adaptive's supplier records migrate to res.partner property_supplier_payment_term_id and bank_ids fields respectively. We preserve the original supplier code as a custom field on the Odoo partner record for cross-reference during the transition period.

Adaptive stores accounts as flat rows with code, name, and type flags. Odoo uses a hierarchical account chart with account_type values (asset, liability, equity, income, expense) and a root/fiscal_position structure. We map Adaptive account type flags to Odoo account_type, recreate the account code structure in Odoo's chart of accounts wizard, and flag any legacy account codes that exceed Odoo's 64-character account code limit for manual resolution before import.

Adaptive's open AP and AR line-item documents with status flags map to Odoo account.move records of type out_invoice (AR) and in_invoice (AP). We map Adaptive invoice status flags to Odoo's draft/validated/paid state machine, explicitly setting state=posted only when Adaptive status indicates validated. Outstanding balances transfer as line amounts against the mapped account.account records for receivable and payable accounts. Odoo requires account.move to be in draft state before posting; we sequence state transitions accordingly.

Past journal entries from Adaptive carry fiscal period and date metadata that must be re-mapped to Odoo's fiscal year structure. We flag entries that span Odoo's defined fiscal year boundaries and require period re-assignment or the creation of adjusting journal entries. Entries that fall within Odoo's configured fiscal years migrate as posted account.move records with the original date preserved in the move_date field. Entries outside configured periods require a fiscal year extension in Odoo before migration can proceed.

Adaptive Stock Items (SKU, description, unit cost, current quantity) map to Odoo product.product records. We map SKU to product.product default_code, description to name and description_sale, and unit cost to standard_price. Current on-hand quantities migrate to stock.quant records linked to the product and the default Odoo warehouse location. We flag custom attributes, BOM structures, and warehouse-specific quantities that require manual configuration in Odoo's inventory module after migration.

Adaptive attached files (invoices, purchase orders, statements) referenced by path or stored as blobs migrate as Odoo ir.attachment records linked to their parent account.move via res_model and res_id. Files exceeding Odoo's default 25 MB attachment size limit are flagged for manual distribution or alternative storage. We maintain original filenames and document dates in ir.attachment name and create_date fields for traceability.

Adaptive User accounts (name, email, role assignments) map to Odoo res.users records. We map active Adaptive users to active Odoo users and flag inactive or archived users that may not have a direct equivalent. Role assignments from Adaptive do not migrate as Odoo security groups automatically; we deliver a written role mapping table for the customer's admin to assign Odoo access rights groups (Sales, Inventory, Accounting, etc.) post-migration.

Adaptive's versioned ledgers with fiscal period assignments require Odoo's fiscal year configuration to be established before journal entry migration. We create account.fiscal.year records matching Adaptive's fiscal periods, configure date_range_type for each, and set date_range on all fiscal years that contain historical transactions. This step is prerequisite to any account.move import.

Adaptive stores multi-currency balances that must map to Odoo's res.currency rate table and account.move.line with currency_id and amount_currency fields. We extract the original currency code from Adaptive, match it to an Odoo res.currency record (creating if not present), and set the applicable exchange rate at the time of each transaction. Unrealized currency gains/losses from Adaptive's ledger are flagged for Odoo admin to configure as exchange difference journals in Odoo.