Migrate your Epicor iScala data

GL module holds journal entries, chart of accounts, and financial periods. Multi-company deployments store separate GL records per company code. We map GL accounts and opening balances to the destination's chart-of-accounts structure, flagging currency and intercompany transaction handling separately.

SL manages customer records, open invoices, and AR. We migrate customer masters, outstanding invoices, and payment histories. Address and contact fields vary by version; we normalize them during field mapping.

PL handles vendor records, open AP, and purchase invoices. We extract vendor masters and AP aging records. Multi-currency purchase transactions require exchange-rate preservation during migration.

OR module contains order headers and lines with pricing, discounts, and fulfillment status. We migrate open and recent closed orders, preserving line-level detail and attachment references.

PC manages purchase order headers, lines, and receipts. Open PO records and GRNI (goods-received-not-invoiced) entries require careful sequencing to maintain AP match integrity.

SC covers inventory items, warehouse locations, lot numbers, and serial numbers. We map stock balances, BOM structures, and warehouse assignments. Lot and serial tracking flags are preserved as metadata on the destination.

MP module handles work orders, routings, and production schedules. We migrate work order headers, operations, and material allocations. Routing sequences and labor standards require field-level mapping against the destination's BOM schema.

HR and PA modules store employee records, compensation history, and payroll runs. Effective-dated records and benefit assignments are migrated as-is where supported. Payroll processing rules and tax codes are flagged for manual review at cutover.

AM tracks fixed assets, depreciation schedules, and asset locations. We map asset masters, accumulated depreciation, and depreciation methods. Asset associations to departments or cost centers are preserved as custom fields in the destination.

PR module stores project masters, WBS elements, budgets, and time entries. We migrate project headers and current budget balances. Detailed time entries and billing records may require chunked migration due to volume.

The UD module contains custom fields attached to standard objects across the system. UD field definitions and their stored values must be inventoried per version, as the UD schema varies significantly between iScala releases.

iScala supports multiple companies and sites within a single database. We scope each company as a separate logical entity during migration, mapping site-specific configurations and inter-company transaction rules independently.

Document attachments stored outside the SQL database (file shares, SharePoint, or Epicor's document management) are not migrated via API. We document the file location references and recommend a parallel file-migration process alongside the data migration.

SM handles service order headers, line items, and field-service scheduling. We migrate open service orders and technician assignments. Scheduling windows and SLA flags are mapped to the destination's service module equivalents.

CM stores contract masters, terms, and billing schedules for service or recurring revenue contracts. We map active contracts with their billing cycles and associated customer or vendor records.