Migrate from SAVIO ERP to Odoo ERP

SAVIO ERP Sales Enquiry records with followup dates and reminders map to Odoo CRM Lead records. The followup date becomes the lead_id.date_deadline; the reminder cadence preserves as a custom Char field tracking the original reminder interval. Alert preferences (SMS/Email) migrate as custom fields on the lead. We run enquiry records before any contact import so that the customer relationship is established first.

SAVIO ERP Quotations keyed by size, thickness, finish (plate), and brand map to Odoo Sale Order lines. Brand-wise pricing rates transform to Odoo pricelist rules applied per product template. Per-unit pricing and size-dependent rates become Odoo Price List line conditions using attribute-based pricing. If the customer uses Odoo Quotation Templates for repeat job types, we extract quotation structures as template lines during scoping.

SAVIO ERP Sales Order Booking records map directly to Odoo Sale Order. Order lines with size, thickness, finish, and brand attributes map to sale order lines referencing Odoo product variants. Delivery address and E-way bill-required flags migrate as custom fields on the sale order. Customer outstanding balance is informational and does not block order migration.

SAVIO ERP Production Requisition linked to Sales Order maps to Odoo Manufacturing Order. Press Planning and Dryer Planning sequences become Odoo work order operations with step dependencies. The Press Planning sequence order maps to operation sequence in the routing; Dryer Planning becomes a secondary work center assignment. We preserve the production requisition number as a reference field on the Manufacturing Order for audit traceability.

SAVIO ERP's Press Planning tracks press assignments by date and shift. This maps to Odoo Manufacturing Routings with a Press work center defined as the primary operation station. We create work center capacity records matching the daily shift schedule from SAVIO ERP, and map press assignment to the work order operation start time. If SAVIO ERP tracks press-specific plates (tooling assignments), these migrate as bill of materials tools or work center tools on the routing.

SAVIO ERP's Dryer Planning tracks dryer chamber assignments and batch drying schedules. We create a Dryer work center in Odoo and map dryer assignments to secondary operations on the Manufacturing Order. Drying duration from SAVIO ERP becomes the operation duration on the secondary work order. If SAVIO ERP tracks batch size by dryer chamber, we configure work center capacity accordingly.

SAVIO ERP's D-lite (daily load) tracking by machine or production line maps to Odoo work center capacity records. Daily load percentage and machine assignment migrate to work center capacity calendars. We preserve historical D-lite data as a custom report table (or as analytic account entries) rather than live capacity records, since Odoo's capacity calendar is forward-looking. Production scheduling in Odoo uses the migrated capacity data as the baseline for finite capacity planning.

SAVIO ERP sheet inventory with size, thickness, finish (plate), and brand attributes maps to Odoo product templates with attribute-based variants. Each combination of size, thickness, finish, and brand becomes an Odoo product variant using product attributes (Product Attribute lines with value sets). Bar-code references migrate as Odoo product barcodes. Per-sheet expense costing migrates to custom product cost fields (Standard Price or Average Price depending on the costing method). We flag any sheet inventory records missing required attributes for manual resolution before import.

SAVIO ERP Party records map to Odoo Partner records with the Partner Type set to Customer or Vendor. Outstanding balances migrate as custom monetary fields for reference. SMS and Email alert preferences preserve as partner custom fields. GST registration details (GSTIN) migrate to the partner's Tax ID field. We import Customers before Vendors so that any shared contact records (party type both) are handled correctly as multi-type partners in Odoo.

SAVIO ERP GST-compliant sales invoices map to Odoo Account Move (type out_invoice). E-way bill generation flags and E-way bill document references migrate as custom fields on the account move. Invoice line items reference Odoo product variants resolved from the original SAVIO ERP item codes. We import account moves after partners and products are established in Odoo to satisfy partner_id and product_id foreign key constraints.

SAVIO ERP delivery challans map to Odoo Stock Picking (type out going). E-way bill requirement flags from the challan migrate as custom fields on the picking. If SAVIO ERP tracks challan-to-invoice linking, we create a picking reference on the corresponding Odoo account move. We import stock moves after the product variants and warehouse locations are configured in Odoo.

SAVIO ERP's Accounts module ledger structure maps to Odoo's Chart of Accounts. We map income and expense accounts to standard Odoo account types (income, expense, other income, cost of goods sold). Account codes from SAVIO ERP preserve as the Odoo account code for audit continuity. If SAVIO ERP uses non-standard account structures for laminate-specific cost centers, we create additional account groups in Odoo during configuration. We import the chart of accounts before any journal entries or invoices to avoid orphaned move lines.

SAVIO ERP Employee records with department assignments and basic compensation map to Odoo Employee records. Department names from SAVIO ERP map to Odoo Departments. Compensation details migrate as custom salary structure fields if the customer activates the Odoo Payroll app; otherwise they migrate as informational custom fields on the Employee record. Standard employee fields (name, contact, department, job title) migrate regardless of Payroll app activation.