Migrate from Epicor iScala to Odoo ERP

iScala GL records (journal entries, chart of accounts, financial periods) store company-dependent data under company codes. We query company codes from the iScala system configuration during discovery, then extract GL accounts per company and map them to Odoo's account.chart template with the company code preserved as an analytic account or as a separate Odoo company entity. Journal entries migrate with full debit/credit integrity; Odoo's double-entry accounting model matches iScala's ledger structure.

iScala SL customer masters, outstanding invoices, and payment history map to Odoo Partners with the is_company flag set to True. Address fields, contact roles, payment terms, and credit limits migrate from SL to partner fields and custom fields. Multi-currency invoices preserve exchange rates by storing the rate at invoice time in a custom field on the invoice line.

iScala PL vendor masters, open AP invoices, and payment history map to Odoo Partners with the supplier rank greater than zero. Vendor-specific fields (tax ID, bank details, payment terms) migrate to Odoo partner fields and custom fields. Multi-currency purchase transactions preserve exchange rates from PL at invoice time to maintain AP aging accuracy in Odoo.

iScala OR order headers and lines with pricing, discounts, and fulfillment status map to Odoo sale.order and sale.order.line. Open orders and recently closed orders migrate with line-level detail preserved. We flag orders with a custom field is_migrated__c and store the original iScala order number as a reference for reconciliation.

iScala PC purchase order headers, lines, and receipts map to Odoo purchase.order and purchase.order.line. GRNI (goods-received-not-invoiced) entries migrate as Odoo internal moves with a linked vendor bill reference. GRNI tracking requires Odoo configuration because it is not a native Odoo concept; we map it to a combination of received quantity versus invoiced quantity on the purchase order line.

iScala SC inventory items, warehouse locations, lot numbers, and serial numbers map to Odoo product.product, stock.quant (for stock on hand), and stock.lot. We map BoM structures to Odoo mrp.bom. Lot and serial tracking flags migrate as metadata. IMPORTANT: Lot and serial records are linked to transaction history (receipts, issues, adjustments) in iScala SC. We sequence stock migration to include receipt transaction history so that traceability links remain intact in Odoo's stock.move chain. Current balances only migration breaks lot/serial traceability.

iScala MP work orders, routings, operations, and material allocations map to Odoo mrp.production, mrp.routing, and mrp.workorder. BoMs migrate to Odoo mrp.bom. Complex routings with alternate work centers and labor standards require field-level mapping against the specific iScala MP version's routing table schema. We flag manufacturing migrations with a custom field is_mfg_migration__c and note any routing operations that need manual rebuild in Odoo due to structural differences.

iScala AM asset masters, accumulated depreciation, depreciation methods, and department or cost center assignments map to Odoo account.asset with the depreciation method (linear, declining), book value, and accumulated depreciation preserved. Asset locations and assigned departments migrate as custom fields or analytic account assignments on the asset.

iScala PR project masters, WBS elements, budgets, and time entries map to Odoo project.project and project.task. Current budget balances migrate as project financial data. Detailed time entries (hours, cost, billable amount) require chunked migration because large project histories can exceed single API batch limits. We migrate project headers and current budget balances and flag detailed time entry scope for admin review.

The iScala UD module stores custom fields attached to standard objects. UD field definitions vary by iScala version (2.2 through 2022.1), and the UD table schema must be inventoried during discovery against the target iScala version's UD structure. We extract UD field definitions and their stored values per object, then map them to Odoo custom fields (created via ir.model.fields or Odoo Studio on Enterprise). Fields with no matching destination property go to a manual mapping review queue before migration.

iScala stores company-dependent data under company codes within the same database alongside company-independent system data. We query company codes from iScala system configuration during discovery, then create each company as a separate Odoo company entity with its own chart of accounts, warehouse assignments, and user permissions. Inter-company transactions require Odoo inter-company rules configuration post-migration.

Document attachments stored outside the SQL database in file shares, SharePoint, or Epicor document management are not migratable via API. We audit and document all file location references during discovery and deliver a written file inventory with target path recommendations in Odoo's filestore. A parallel file migration (using ShareGate, SMB copy, or an Odoo file sync script) should be scheduled to coincide with the Odoo cutover date.