Migrate from Maximum Software to Odoo ERP

Maximum Software Customer records map to Odoo Contact with the company type flag set. The customer name, email, phone, and address fields migrate directly. We set the Is a Company flag to true so that individual contacts can be created under the company record. Maximum Software customer-specific custom fields (such as credit limit or payment terms overrides) migrate to custom fields on res.partner or to fields in the dedicated Odoo Accounting module on res.partner.accounting properties. Any Maximum Software customer-specific tax identification (VAT or GST number) migrates to the Contact's VAT field.

Maximum Software Vendor records map to Odoo Contact with the Vendor flag enabled. Vendor-specific fields (payment terms, bank account details, fiscal position assignment) migrate to the Contact's accounting and purchasing properties in Odoo. Vendor-specific custom fields from Maximum Software become custom fields on res.partner with the vendor property context set.

The Maximum Software Chart of Accounts exports as a flat or hierarchical account list with account codes, names, and types (Asset, Liability, Equity, Revenue, Expense). We map each account to the corresponding Odoo account.type and account.code by resolving the Maximum Software account type to the nearest Odoo Account Type (receivable, payable, liquidity, revenue, expense, other). Account codes are zero-padded to Odoo's required format. If Maximum Software uses a multi-company chart, we create a separate Odoo Accounting Plan per company. Reconciliation account flags migrate as the reconcile boolean on each account.

Maximum Software Items map to Odoo Product records. The item SKU maps to product.default_code, item name maps to product.name, and the unit of measure maps to the Odoo uom.uom reference. We map Maximum Software item categories to Odoo Product Category records, creating the hierarchy if it does not exist. Supplier info (preferred vendor, lead time, purchase price) migrates to the product.supplierinfo table linked to the matching Vendor Contact. Items with Bill of Materials or kit structures in Maximum Software map to Odoo mrp.bom records.

Maximum Software open invoices (unpaid vendor bills or outstanding customer invoices) migrate to Odoo Account Move records with move_type set to in_invoice or out_invoice respectively. The original invoice number, invoice date, and due date migrate as move_name, invoice_date, and invoice_date_due. Each line item maps to account.move.line with the correct account, debit/credit amount, and analytic distribution. Outstanding amounts preserve the open balance so that AP aging reports in Odoo are accurate immediately after migration. Paid invoices are migrated as account.move.line history only if historical reporting is in scope.

Maximum Software Users map to Odoo res.users. We resolve by email match. The user's name, email, active status, and internal group memberships migrate. Maximum Software role or permission sets map to Odoo Access Rights groups (base.group_user, base.group_erp_manager, etc.) where the equivalent rights exist; any Maximum Software-specific permission not represented in Odoo is flagged for explicit admin review. Inactive users migrate with the active flag set to false.

If Maximum Software stores sales order history in scope, open or recently closed orders migrate to Odoo sale.order records. Order lines map with product, quantity, and price to sale.order.line. Tax handling migrates to the correct Odoo account.tax record reference. Status mapping preserves the order lifecycle state (draft, confirmed, done, cancel) as Odoo sale.order.state. We do not migrate abandoned or draft-only orders unless explicitly requested.

Maximum Software purchase orders migrate to Odoo purchase.order records. PO number, vendor, order date, and expected delivery date map directly. Line items map product, quantity, and price to purchase.order.line with the correct taxes and account_analytic_domain assignments. Purchase order status (draft, sent, confirmed, done, cancelled) maps to Odoo's purchase.order.state. Confirmed purchase orders that have not yet resulted in a vendor bill generate the expected purchase commitments in Odoo's purchase analytics.

Maximum Software cost centers or project records that represent financial tracking entities map to Odoo analytic.account. Each analytic account gets a corresponding Odoo project record if the project management module is in scope. Account codes, names, and the parent cost center hierarchy migrate with the correct parent_id reference. Budget or committed amounts migrate as analytic line budget records if historical data exists in Maximum Software.

Maximum Software payment term definitions (net 30, 2/10 net 30, custom day-of-month schedules) map to Odoo account.payment.term records. Each term line (balance percentage, day count, months) migrates to account.payment.term.line entries. Payment terms are linked to Customer and Vendor contacts via the property_payment_term_id field on res.partner after migration.

Maximum Software tax codes (VAT rates, GST, withholding tax) map to Odoo account.tax records. Tax name, amount (percentage or fixed), tax type (sale/purchase/refund), and applicable account assignments migrate. Tax group assignments (for country-specific reporting such as VAT return lines) map to the nearest Odoo tax.group. Any tax applicability rules (product category filters, fiscal position rules) are documented for the customer's admin to configure in Odoo fiscal positions post-migration.

Maximum Software warehouse or location definitions migrate to Odoo stock.location records within the stock.warehouse structure. Warehouse codes map to location names, and the location type (internal, supplier, customer, inventory) maps to the corresponding Odoo location_type. Inventory quantities per location migrate as stock.quant records after the product catalog is established. Multi-warehouse Maximum Software configurations create multiple Odoo warehouse records with the correct warehouse-level routing rules.