Migrate from Wiise to Odoo ERP

Wiise Customer master records map to Odoo res.partner with partner_type set to 'contact' or 'invoiceaddr' depending on the address role. Customer name, address, contact details, payment terms, and credit limits migrate directly. Wiise custom fields on Customer map to Odoo ir.model.fields custom fields (char, selection, date, float) created in the destination database before import. Credit limit precision is preserved; any values exceeding Odoo's standard decimal precision are flagged in the pre-flight report.

Wiise Vendor cards map to Odoo res.partner with partner_type = 'supplier'. Purchase terms, currency settings, and vendor-specific dimensional tags migrate. Odoo vendors are in the same table as customers but filtered by supplier flag, so the import uses a partner_category split (Customer vs Vendor) rather than separate tables. Wiise vendor dimensional tags for cost-centre require mapping to Odoo analytic.account records, which are a separate object in Odoo's dimensional model.

Wiise Items (stock items, non-stock items, and services) map to Odoo product.product. Item unit cost, inventory posting groups, and warehouse location assignments migrate. Stock vs non-stock vs service type is determined by the item's product type field in Wiise and sets product.type in Odoo (product, consumable, service). Wiise's 2 decimal-place limit on custom decimal fields means any Item-level custom fields storing exchange rates or precise unit costs are rounded before import; we flag each instance in the pre-flight mapping report.

Wiise account codes and names migrate directly to Odoo account.account. The mapping is straightforward for standard balance sheet and P&L accounts. Wiise dimensional tags (cost-centre, department, location) attached to postings require a separate mapping to Odoo analytic.account, which is Odoo's equivalent of a cost-centre or project-level reporting dimension. We create the analytic accounts in Odoo during configuration and link them to account.move lines via analytic_distribution during the journal entry import.

Outstanding purchase invoices migrate as Odoo account.move records with move_type = 'in_invoice' and state = 'draft' for open items. We preserve invoice date, due date, remaining amount, and currency. Full invoice line history migrates on request but Odoo recommends importing open balances as opening journal entries for cleaner reconciliation at go-live. Wiise's vendor-specific dimensional tags on AP lines require mapping to Odoo analytic.account distribution on each move line.

Outstanding sales invoices migrate as Odoo account.move with move_type = 'out_invoice' and state = 'draft' for open items. Customer invoice date, due date, remaining amount, and currency are preserved. As with AP, Odoo recommends absorbing open AR as opening journal entries rather than full historical invoice line imports to avoid Odoo generating duplicate follow-up communications on already-sent invoices.

Wiise Jobs (task-level work breakdown, resource assignments, and billing) map to Odoo project.project. Job tasks migrate to project.task. Wiise job-specific dimensions migrate as Odoo analytic.account records linked to the project, preserving cost-centre reporting within the project context. If the customer uses Wiise job billing, we map billing rules to Odoo project billing configurations, though time and material tracking requires Odoo's Timesheets app to be installed and configured.

Wiise Fixed Asset records (acquisition date, cost, depreciation method, book value, location) map to Odoo account.asset.asset. Depreciation schedules are preserved as account.asset.depreciation.line records in Odoo, maintaining the original straight-line or declining-balance method from Wiise. Assets still under depreciation at migration date are flagged with their remaining book value and next depreciation date so Odoo's scheduled action can pick up the correct posting amount at month-end.

Wiise Employee records (name, position, department, employment status, HR metadata) migrate to Odoo hr.employee. Both active and terminated employees transfer, with terminated employees marked as inactive in Odoo. Wiise custom fields on employee records map to Odoo custom fields on hr.employee. The mapping preserves employee department as an hr.department lookup, which Odoo uses for org-chart reporting.

Wiise warehouse locations map to Odoo stock.location with location_type set according to the location role (internal, supplier, customer, inventory loss). Item-location quantity records migrate to stock.quant, preserving on-hand quantities per warehouse per item. Odoo's location hierarchy (parent_path) is rebuilt from Wiise's location structure during import to maintain the physical warehouse bin relationships.

Wiise multi-company entities under one subscription are exported as separate company units. In Odoo, multi-company is handled by creating distinct company records within a single database (if Odoo Enterprise is used with the multi-company module) or by provisioning separate Odoo databases per legal entity. We scope which entities migrate during discovery and export each as an independent dataset, mapping entity names to Odoo res.company records. Intercompany balancing entries are included as journal entries in the relevant company.

Wiise custom fields across 15 page types (Customer, Vendor, Item, Sales Header/Lines, Purchase Header/Lines, Job, Contact, Fixed Asset, Service Item) migrate to Odoo custom fields on the equivalent model. We pre-create the Odoo custom field definitions (field type, required/optional, default value) before importing any data. The 2 decimal-place precision limitation on Wiise custom decimal fields is flagged for each field so the customer can decide whether to store the value as a float or as a char field in Odoo to preserve full precision.