Migrate from SYSPRO to Odoo ERP

SYSPRO Customer master records map to Odoo res.partner with partner_type = contact and customer_rank = 1. Address, contact details, credit limits, and tax jurisdiction codes migrate directly. Multi-site customer records that exist independently at different SYSPRO sites map to separate Odoo partner records with a shared parent company partner if the customer is logically one entity; otherwise each site-level customer becomes an independent Odoo partner. Custom form fields attached to SYSPRO customer take-on programs extract as Studio-defined fields on res.partner before the partner data loads.

SYSPRO Supplier master records map to Odoo res.partner with partner_type = contact and supplier_rank = 1. EDI/XML trading-partner flags and contract pricing information migrate to custom fields on res.partner since Odoo's standard vendor record does not natively store EDI configuration. The customer's AP team configures EDI or Odoo's generic import/export modules post-migration based on the trading-partner data we surface.

SYSPRO Inventory items map to Odoo product.product. Unit of measure conversions, stocking locations, cost layers (FIFO/average), and warehouse-specific quantities all migrate. Multi-warehouse setups require us to configure Odoo multi-warehouse locations and warehouse records before importing stock.quant quantities at the location level. Products with lot or serial number tracking map to Odoo's lot_number and serial_number fields on stock.production.lot.

SYSPRO BOM structures with multi-level component routing and phantom assemblies require recursive extraction from SYSPRO's Job and routing tables. We preserve bill versions and effective dates tracked per BOM revision and create Odoo mrp.bom records with the same component structure, operation sequences, and work-centre assignments. Phantom BOMs map to Odoo's type = phantom. Phantom components nested within multi-level BOMs require careful sequencing to resolve before parent-level import so that Odoo's explode logic does not duplicate line items.

Open and historical sales orders migrate with full line-item detail, pricing, discount rules, and fulfillment status. Back-ordered lines that reference inventory items not yet received in Odoo are flagged as exceptions in the reconciliation report. Closed sales orders migrate as historical records without triggering inventory reservation. The customer's delivery/picking flow is re-established in Odoo using stock moves rather than the SYSPRO shipment tracking model.

Purchase order headers and lines migrate including receipt status, blanket PO release schedules, and EDI/XML export flags. Lines referencing suppliers that do not yet exist in Odoo are held in a pending queue until the vendor partner record is created. Receipt status is preserved as a custom field since Odoo's incoming shipment model differs structurally from SYSPRO's PO receipt processing.

SYSPRO Jobs are the manufacturing work-order entity tied to routing, labour posting, and material issues. We map job status, work-centre assignments, and WIP valuations to Odoo mrp.workorder linked to the corresponding mrp.production (manufacturing order). Jobs with active WIP balances require a costing review before migration to determine whether open WIP moves to an Odoo work-in-progress valuation account or is written off as part of a cost reconciliation step.

SYSPRO AR and AP invoices including multi-currency headers and line-level tax codes migrate to Odoo account.move records. Contra-invoice relationships used for AP netting in SYSPRO are preserved via custom field mapping and reviewed by the customer's AP lead during reconciliation. Historical invoices migrate as posted entries to preserve financial history; open invoices migrate as draft entries so that the customer's accounting team can review and post them within Odoo's approval workflow.

SYSPRO account codes, cost-centre structure, and journal-entry templates map to Odoo account.account with the correct account_type and account_root assignments. Cost-centre assignments that live as separate dimensions in SYSPRO map to Odoo account.analytic.account (analytic accounts) rather than to account codes, which is a common structural difference that requires explicit mapping decisions during scoping.

SYSPRO operators carry security-role assignments and MFA enrollment records. Operator-level restrictions must be translated to Odoo's permission model, which uses access rights groups and record rules per app rather than operator-level field restrictions. We extract the SYSPRO operator table with role assignments and deliver a written mapping to Odoo access.groups as a reference for the customer's admin to configure post-migration. MFA enrollment does not migrate; users re-enroll using Odoo's built-in MFA feature.

SYSPRO Custom Form Entry fields attach to specific programs (Customer take-on, Sales Order entry, etc.) and can reference lookup tables or carry formula-driven values. We extract field definitions and data together, create the equivalent Studio-defined fields on the corresponding Odoo model before the related data loads, and preserve formula-driven values as stored custom fields with a note that the customer should evaluate whether the formula logic needs to be re-implemented as an Odoo computed field. Formula fields that depend on data transformations during migration are evaluated in the migration transform script rather than in Odoo.