Migrate from Fulfil to Odoo ERP

Fulfil Sales Orders map to Odoo Sale Order. Order status, line items, fulfillment state, and channel attribution migrate via Fulfil REST API with Odoo Sale Order created through the sale.order model. Shipping and payment records attach as delivery and invoice records respectively. Channel attribution from Fulfil (Shopify, Amazon, manual) maps to an Odoo custom field or tag for segmentation.

Fulfil Items carry SKU, description, cost, price, reorder point, and bin location. We map all standard fields plus any user-defined custom fields on the item record. For made-to-order and engraved items, the Fulfil custom attributes stored on Sales Order Lines are flattened into Odoo product variant attributes (product.attribute and product.attribute.value) during the transform step before the product record is created.

Fulfil Purchase Orders include vendor assignment, expected dates, line items, and receiving records. We create Odoo Purchase Orders from Fulfil PO data via the purchase.order model. The vendor field maps from Fulfil's vendor record to Odoo's res.partner with supplier flag set to true. Expected dates map to date_planned on PO lines.

Fulfil receiving records (the actual receipt of goods against a PO) map to Odoo stock.move records linked to the purchase.order. We sequence receipt records ahead of vendor account closeout in the migration run to ensure that all incoming inventory transactions are landed before the vendor is deactivated in the destination system, preventing orphaned receiving entries in Odoo's inventory valuation.

Fulfil multi-warehouse configurations with bin-level location data map to Odoo warehouse record (stock.warehouse) and location hierarchy (stock.location). Each Fulfil warehouse becomes a root Odoo warehouse, with bin locations nested under the warehouse's view_location_id. Associated stock levels migrate as inventory snapshot records in the stock.quant model.

Fulfil Customer records include contact details, billing address, shipping addresses, and account-level pricing tiers. We create Odoo res.partner records with the customer flag set, preserving the name, email, phone, and address structure. Custom fields on the Fulfil Customer object require explicit per-tenant field-level mapping against Odoo res.partner custom fields, which we pre-create in the destination schema before import.

Fulfil lot tracking and serial number assignments on Items are tied to inventory transactions. We carry these through as stock.lot records in Odoo, linked to the product_id and the location where the lot or serial was assigned. Traceability across receiving and fulfillment steps is preserved by mapping the Fulfil lot_number field to Odoo's name field on stock.lot and setting the company_id from the relevant Fulfil entity.

Fulfil custom product attributes (engraving text, embroidery, made-to-order options) are stored as extended attributes on Sales Order Lines rather than as a distinct object. We extract these as structured line properties from the order-line JSON, then create Odoo product.attribute records and product.attribute.value records for each distinct custom option type. The Sales Order Line in Odoo inherits these variant attributes so that the made-to-order configuration carries through to the manufacturing order if Odoo's MRP module is in use.

Fulfil vendor invoice records in the financials module export to Odoo account.move records of type in_invoice. Mapping depends on the destination's chart of accounts structure, which we reconcile during the account mapping step. Open and historical invoices migrate with their line items, amounts, and due dates. Vendor bill state (draft, posted, cancelled) maps directly to Odoo's move state model.

Where Fulfil's manufacturing module is in use, work orders, BOMs, and production steps are accessible via API. We map work orders to Odoo mrp.production records and BOMs to mrp.bom. Complex BOM hierarchies with multi-level routing may require manual sequencing in the destination because Odoo's BOM explosion logic handles nested structures differently from Fulfil's manufacturing workflows. We document the BOM structure and flag any non-standard routing for manual configuration in Odoo MRP.

Fulfil financial accounts are exportable but require mapping against the destination's chart of accounts. Multi-entity deployments need account codes reconciled across legal entities. There is no automated cross-walk export from Fulfil. During migration scoping, we collect the full account tree for each entity and work with the customer to build a manual mapping table before any financial record transfer begins. Odoo's account.account records are created with the mapped codes and names, and the company_id is set per entity.