Migrate from Expand ERP to Odoo ERP

Expand ERP Lead records migrate to Odoo CRM Lead. Lead source and status properties map to Odoo's lead_type and stage fields. We extract the lead owner from Expand ERP's user reference and resolve it against Odoo's Users table by email. If the customer uses Odoo Contacts for both leads and partners, we map to the Contact object with a lead flag instead.

Expand ERP Customer records map to Odoo Contact with the contact type set to contact. Billing and shipping addresses migrate to separate Partner Address records linked to the Contact. Payment terms and credit limits map to Odoo's property_payment_term_id and credit_limit fields. We preserve all custom properties as Odoo custom fields on the res.partner model.

Expand ERP Vendor records map to Odoo Contact with contact_type set to delivery. Vendor address, payment terms, and bank details migrate to the vendor's Contact record and associated Partner Address records. Purchase pricing terms map to Odoo's property_supplier_payment_term_id on the vendor Contact.

Expand ERP Sales Orders migrate to Odoo Sale Order. Order status maps to Odoo's state field (draft, sent, sale, done, cancel). Line items, quantities, and pricing migrate to Sale Order Line records with the product and unit of measure resolved. Customer reference and owner fields map to the partner_id and user_id on the Sale Order header.

Expand ERP Purchase Orders map to Odoo Purchase Order. Order status, vendor reference, expected delivery date, and line items migrate directly. Odoo's确认接收 workflow is designed around the PO receiving model; we configure the picking type and procurement settings before migration so that received quantities flow correctly into inventory after import.

Expand ERP Items migrate to Odoo Product (product.template with product.product variants if the item has size, color, or other variants). SKU maps to Odoo's default_code. Unit of measure, cost price, and sale price migrate to the product's fields. Opening stock maps as an inventory adjustment in Odoo Inventory after the product is created. Items with serial or lot numbers require a supplemental export from Expand ERP and a separate lot creation step in Odoo.

Expand ERP warehouse locations map to Odoo Warehouse records with their corresponding internal Location records (stock.location). Expand ERP's warehouse-level stock balances migrate as Odoo Inventory Quant records linked to the warehouse's virtual locations. Bin or lot serial numbers may not be available in the standard export; we request a supplemental inventory report and cross-reference it before finalizing stock quantities. Multi-warehouse customers require location hierarchy design before migration begins.

Expand ERP POS Billing transactions migrate to Odoo POS Order. Transaction headers map to POS Order with payment method, date, and total. Line items map to POS Order Lines with product resolved. Shift and register summaries from Expand ERP do not have a direct Odoo equivalent; we migrate transaction headers and line items as Order records and flag any missing register reconciliation data in the migration report. POS sessions are recreated post-migration as Odoo open-close sessions.

Expand ERP Production Jobs migrate to Odoo Manufacturing Order. Work order headers, material consumption lines, and output quantities map to the MO's components and finished products. BOM (Bill of Materials) versioning in Expand ERP requires field-level review per production job because BOM revision numbers may not export consistently; we flag BOM version mismatches in the migration report for manual reconciliation. Work order scheduling and routing operations map to Odoo's workcenter operations if the production jobs include operation steps.

Expand ERP's built-in export documentation module stores licence numbers, shipping marks, and country-specific customs fields as custom document attributes. These do not map 1:1 to any standard Odoo field. We extract them as structured Notes or as custom fields on the related Sale Order or Stock Picking record. Mandatory fields that have no Odoo equivalent are flagged in the migration report for manual re-entry or third-party trade compliance app configuration.

Expand ERP account codes and names migrate to Odoo Account records. Account type mapping (Asset, Liability, Equity, Revenue, Expense) is confirmed against the source system's chart structure and mapped to Odoo's account.type. If the customer uses Indian statutory compliance accounts (GST, TCS, TDS), we map those to Odoo's tax account fields and flag any accounts that require new creation in Odoo's accounting configuration.

Expand ERP User accounts (name, email, role) migrate to Odoo Users. Role-based access from Expand ERP maps to Odoo access rights groups (sales, purchase, inventory, manufacturing, administration) during migration. Any user with a role that has no direct Odoo equivalent is flagged for the customer's admin to assign the correct access rights post-migration. User provisioning in Odoo (active/inactive status) is set to match the source user's active period.