Migrate from Masterplan to Odoo ERP

Masterplan Customers map to Odoo res.partner records with the customer_rank set to 1 (or the is_company flag active for B2B accounts). We extract customer name, billing address, shipping address, payment terms, credit limit, and currency settings from the Masterplan UI export. Because Masterplan lacks a self-service API, we coordinate with Masterplan support to pull a full customer CSV including any custom fields confirmed during discovery. The Odoo partner must have the Contacts app (base) enabled before import.

Masterplan Vendors map to Odoo res.partner with supplier_rank set to 1. We preserve vendor address, payment terms, W-9 data, and 1099 eligibility flags as custom fields or tags on the partner record. Vendor CSV extraction follows the same vendor-assisted process as customer data. Odoo's Purchase app must be installed for supplier workflow functionality.

Masterplan Items (Finished Goods, Raw Materials, Components, Services) map to Odoo product.template with the appropriate product_type. We preserve the costing method (standard, average, FIFO) from Masterplan as the Odoo costing_method field, and the item type as product_category mapped to Odoo's product category hierarchy. Masterplan's product code becomes the Odoo default_code (SKU) for dedupe. If Masterplan uses multiple units of measure (each, case, pallet), we map them to Odoo's unit of measure and uom_category tables before product import.

Masterplan's GL account hierarchy maps to Odoo account.account records with the corresponding account_type (asset, liability, equity, revenue, expense). We extract account number, name, type, and any department or cost-center rollup structure. Odoo requires a Chart of Accounts template (localization package) to be installed before manual accounts are created. We apply the appropriate fiscal country localization for the customer's jurisdiction so that tax accounts and fiscal position defaults are pre-populated.

Outstanding payables and receivables from Masterplan map to Odoo account.move records with move_type of in_invoice (AP) or out_invoice (AR). We normalize Masterplan aging buckets (which vary by customer configuration) to standard 30/60/90/120-day buckets on the Odoo partner record's credit_limit field. Invoice amounts, due dates, and aging status migrate as open invoices rather than paid records; the customer reconciles actual payments post-migration in Odoo.

Open Sales Orders from Masterplan map to Odoo sale.order records. We extract order number, customer reference, line items (product, quantity, unit price), and fulfillment status. Partially shipped or partially invoiced orders are flagged explicitly so the destination handles them correctly post-cutover. The Odoo Sale app must be installed. If Masterplan uses multi-company orders, we configure Odoo's multi-company rules before import.

Open Purchase Orders from Masterplan map to Odoo purchase.order records with vendor, line items, quantities, and unit prices preserved. Partially received orders are flagged in the data map for the customer to reconcile in Odoo post-go-live. The Odoo Purchase app must be installed before import.

On-hand quantities per warehouse location in Masterplan map to Odoo stock.quant records tied to stock.location records. Because Odoo's warehouse structure (Warehouse > Location > Shelf) often differs from Masterplan's location hierarchy, we ask the customer during scoping to define the target Odoo warehouse layout before inventory import. We extract stock levels per Masterplan location and remap to the Odoo location structure. Negative stock and non-scheduled inventory adjustments are flagged as exceptions requiring customer review before import.

Multi-level BOMs from Masterplan map to Odoo mrp.bom records with the appropriate type (kit, manufacturing, subassembly). We preserve component quantities, scrap factors, and phantom assembly flags. For multi-level BOMs, we either flatten them into a single-level BOM in Odoo or create a nested BOM structure depending on the customer's Odoo manufacturing configuration. Phantom assemblies in Masterplan map to Odoo's phantom bom_type. The Odoo MRP (Manufacturing) app must be installed.

Active and historical work orders from Masterplan map to Odoo mrp.production records with status preserved (draft, confirmed, in progress, done, cancelled). We extract routing steps, labor hours, material allocations, and backflush transactions. Work order history older than the agreed lookback cutoff (configured with the customer during discovery, based on Masterplan's archive/purge settings) is excluded and noted as out-of-scope. The Odoo MRP app must be installed.

Historical journal entries from Masterplan map to Odoo account.move records with move_type of entry. We migrate entry date, account lines, debit/credit amounts, and memo. Entries older than the migration lookback cutoff or outside the active fiscal year are excluded. Because Odoo fiscal year lock can prevent post-period entries, we coordinate with the customer's accountant to ensure open fiscal years are configured in Odoo before journal entry import begins.