Migrate from Zenscale to Odoo ERP

Zenscale's hierarchical financial chart of accounts with cost-center tagging maps to Odoo's account.account model with the account.account Type and l10n_in_india fiscal localization applied. Cost-center assignments from Zenscale map to Odoo's account.analytic.account (analytic dimension). We extract account code, name, parent_id hierarchy, and cost-center assignment and validate that Odoo's India localization tax group settings are consistent with the mapped account types before import.

Zenscale maintains customer and supplier ledgers with GST registration numbers (GSTIN), payment terms, and credit limits. These map to Odoo res.partner records with partner_type set to 'customer' or 'vendor'. The Zenscale GSTIN field maps to res.partner.vat and triggers Odoo's India fiscal position logic for inter-state GST treatment. We validate GSTIN format (15-character alphanumeric) during the transform step and flag any malformed registrations for customer correction before import.

Zenscale stores FG, RM, and semi-finished items with BOM linkages, UoM, and stock thresholds. These map to Odoo product.product records with product.category set to the matching Odoo product category (all goods, raw materials, consumables). Stock quantities map via product.quant records. Item-level valuation methods (FIFO, standard cost) map to product.valuation. We flag items with active BOMs so the BOM migration step can link them to mrp.bom records in the correct dependency order.

Zenscale open PO and SO records with line-item pricing, delivery schedules, and GST tax components map to Odoo purchase.order and sale.order. Zenscale's line-item GST tax rates map to Odoo's account.tax records using the India GST tax template (CGST, SGST, IGST). We extract pending order balances, not fully invoiced amounts, and flag orders with delivery schedules that may require Odoo procurement or dropshipping rules to be configured before the records can be activated.

Zenscale production BOMs are embedded within production orders rather than existing as standalone records. We request a full production order export including closed orders to extract the BOM definitions (components, quantities, consumption rates) alongside routing steps and work-center assignments. These map to Odoo mrp.bom with mrp.bom.line components and mrp.routing.workcenter routing records. Multi-level BOM nesting is preserved by resolving sub-assembly BOM references before import so that the top-level BOM can reference already-migrated child BOMs.

Zenscale production orders include routing steps, work-center assignments, and BOM component quantities. Open and in-progress production orders migrate to Odoo mrp.production records with the mrp.bom reference resolved from the BOM migration step. Closed production orders migrate as mrp.production records with state='done' to preserve historical production records for costing and audit. Work order lines migrate as mrp.workorder records linked to the parent production.

Zenscale stores employee records with salary components (basic, allowances, deductions), attendance, and statutory contribution data (PF, ESI, TDS). These map to Odoo hr.employee with contract records (hr.contract) capturing salary structure lines. Indian statutory fields (PF number, ESI number, PAN) map to custom fields on hr.employee. We flag any employee without a mapped salary structure for the customer to configure in Odoo HR before activating payroll. Note: Odoo's India payroll app (l10n_in_hr_payroll) covers Indian compliance but may require a certified payroll implementation partner for full statutory alignment.

Indian GST compliance data (GSTR-1, GSTR-3B summaries, input tax credit registers) are stored in Zenscale against transactions. We extract tax summary records and line-item GST amounts and map them to Odoo account.tax records with the appropriate GST type (cgst, sgst, igst, cess). GSTR-2A reconciliation data migrates as documentation records rather than live tax filings; the customer refiles or continues filing in GST portal directly. This is flag-high because incomplete GST records create retrospective liability under Indian tax law; we validate totals against Zenscale GST reports before decommissioning.

Zenscale quality management stores inspection results linked to purchase orders and production lots. These map to Odoo quality module records (qc.inspection) linked to stock.move or mrp.production. QC pass/fail status, inspector names, and rejection reasons migrate as inspection records with a note field for rejection detail. Odoo Quality Control requires the quality app to be installed; we confirm this during scoping and configure QC triggers as part of the Odoo setup phase.

Zenscale stores attached documents (invoices, GRNs, quality certificates) in a proprietary file store without a documented attachment export API. We migrate attachment metadata (filename, date, record type) and deliver a file path mapping document so the customer's admin can relocate the actual files to Odoo's document management (ir.attachment with res_model and res_id) post-migration. Binary file content requires Zenscale's direct export assistance or manual download.