Migrate from Rootstock Cloud ERP to Odoo ERP

Rootstock Items map to Odoo Product records with Product Type set based on Rootstock's item type (Stockable, Consumable, or Service). The Item's stocking policy, costing method (Standard or Average), and lot/serial control flags map to Odoo's Routes, Manufacturing routes, and Traceability settings. Product variants in Odoo handle any size/color/style options that existed as separate Items in Rootstock. We extract all custom Salesforce fields on Item records and map them to Odoo Product extra fields or dynamic fields depending on field type compatibility.

Rootstock Sales Orders map to Odoo Sale Orders with header fields (customer, ship-to, payment terms) mapped to Odoo's partner_id, partner_shipping_id, and payment_term_id. Sales Order line items map to Order Lines with the Rootstock Item linked to the Odoo Product. We preserve fulfillment status (Open, Partially Shipped, Shipped, Cancelled) in a custom status field and flag partial shipment records for Odoo back-order handling. Sales Order custom fields migrate to order-level extra fields.

Rootstock Purchase Orders map to Odoo Purchase Orders with vendor, ship-to warehouse, and approval status preserved. Rootstock vendor records (Account objects with the Vendor checkbox) map to Odoo Supplier records before PO migration so the supplier reference is satisfied at import. PO line items map to Odoo Order Lines with the Rootstock Item linked to the corresponding Odoo Product. Approval workflows in Rootstock (built on Salesforce approvals) are documented but not migrated; Odoo's purchase approval matrix is configured separately post-migration.

Rootstock Work Orders map to Odoo Manufacturing Orders. Work Order headers with routing steps, labor estimates, and material allocations map to Odoo MO headers linked to the Product (the finished good). Routing steps in Rootstock map to Odoo Work Orders with the Work Centers defined in Odoo's MRP routing configuration. Material allocations map to Odoo MO Components linked to the finished Product's BoM. Work Orders tied to a Sales Order in Rootstock are linked to the corresponding Sale Order in Odoo via the link_mrp_production_procurement_group mechanism.

Rootstock multi-level BOMs with versioning and effective dates map to Odoo BoM structures. Because Odoo supports a single active BoM per product variant (with an optional alternative BoM), we apply a selection rule during migration: the most recently approved BOM revision with an effective date at or before the migration date becomes the active Odoo BoM. Prior revisions and alternate BOMs are archived in a custom Text field (rs_bom_history__c) as JSON containing version, effective date, and revision status. Multi-level BOMs are migrated as nested BoM structures in Odoo with the correct BoM type (kit, manufacture, or subcontract) set per Rootstock's BOM type.

Rootstock Inventory Locations map to Odoo Locations organized in a warehouse hierarchy. We pre-map Rootstock's flat location list with parent-warehouse relationships to Odoo's warehouse > location > sublocation structure. Organizations with complex multi-site hierarchies (regions > plants > warehouses > bins) require explicit location mapping before migration; circular location assignments in Rootstock are flagged and resolved. Location types (plant, warehouse, bin, staging) map to Odoo's location_type field and determine inventory valuation applicability.

Rootstock Purchase Receipts map to Odoo incoming Stock Moves linked to the corresponding Purchase Order. Receipt dates, quantities received, and partial receipt flags migrate to the Stock Move and associated Stock Move Line. If Rootstock receipt records contain lot or serial number assignments, those link to Odoo lot records attached to the Stock Move Line. Receipts without a corresponding PO in the migration scope are flagged for reconciliation.

Rootstock's chart of accounts (stored on Salesforce with GL account objects) maps to Odoo's Chart of Accounts structure. Account type (Asset, Liability, Equity, Income, Expense), account code, and name migrate to Odoo Account records. Multi-company and intercompany accounts from Rootstock map to Odoo's Multi-Company configuration if the destination Odoo instance uses multiple companies. Tax codes from Rootstock's tax configuration map to Odoo's Tax mapping tables.

Rootstock's Salesforce Account records with Customer type map to Odoo Company records. The Account Name becomes the Company name, shipping and billing addresses map to Odoo Contacts under the Company (as the primary Contact), and payment terms map to Odoo's Payment Term on the partner record. Custom customer fields on the Account object (credit limits, customer type, tax codes) map to Odoo partner fields or custom partner fields as appropriate.

Rootstock Vendor records (Salesforce Account objects with Vendor checkbox enabled) map to Odoo Supplier records with the Supplier flag set on the partner. Associated purchase terms, W-9/1099 settings, EDI identifiers, and multiple vendor site addresses migrate to Odoo's partner record with additional contact addresses. Vendor records must be migrated before Purchase Orders to satisfy the supplier reference on PO lines.

Rootstock lot master records and serial number assignments map to Odoo Lots (for lot-controlled Items) and Serial Numbers (for serial-controlled Items). The lot number, source document reference, and manufacturing date migrate to Odoo's lot_master_format and associated fields. Full traceability linking lots to source documents (purchase receipts, work orders, delivery orders) is preserved via Odoo's traceability settings enabled at the product level. Lot/serial records are migrated after Products but before any inventory transactions that reference them.

Rootstock ECOs manage BOM and engineering change approvals. Odoo does not have a native ECO object. We migrate ECO headers as Odoo Document records attached to the affected Product, with the change description, approval status, and effective date preserved in document metadata. Approval workflow history and electronic signatures cannot be migrated into Odoo since there is no native approval workflow equivalent for engineering changes; these are documented in the handoff inventory for the customer's admin to rebuild in Odoo via Studio or custom modules.