Migrate from Epicor iScala to Dolibarr ERP

iScala GL module (journal entries, chart of accounts, financial periods) maps to Dolibarr's Accounting module. Multi-company iScala deployments store separate GL records per company code; we query GL company codes upfront and create a separate Dolibarr instance or use Dolibarr's multi-company accounting extensions per legal entity. Exchange rates from iScala GL transactions migrate as Dolibarr currency exchange rate extrafields. iScala's configurable financial reports (CFR) do not migrate; we document the report inventory for admin rebuild using Dolibarr's built-in report builder or third-party BI connectors.

iScala SL customer masters, open invoices, and AR aging records map to Dolibarr Third Parties (type Customer) and the Invoices module. Address and contact fields vary by iScala version (2.2 through 2022.1); we normalize them to Dolibarr's address and contact fields during field mapping. Outstanding AR balances migrate as open invoice records with payment terms preserved. Multi-currency AR transactions preserve the original currency and exchange rate in Dolibarr extrafields.

iScala PL vendor masters and AP aging records map to Dolibarr Third Parties (type Supplier) and supplier invoices. Multi-currency purchase transactions require exchange-rate preservation during migration; we store the original transaction currency and rate in Dolibarr extrafields so that AP aging reports reflect actuals. GRNI (goods-received-not-invoiced) entries migrate as draft supplier invoice records pending vendor invoice matching.

iScala OR order headers and lines with pricing, discounts, and fulfillment status map to Dolibarr Orders (customer orders). We preserve line-level detail, quantity ordered versus quantity delivered, and attachment references. Order status from iScala (Draft, Confirmed, In Progress, Completed, Cancelled) maps to Dolibarr Order status values. Open orders migrate as draft or validated orders depending on fulfillment state; closed orders migrate as closed records for historical reference.

iScala PC purchase order headers, lines, and receipts map to Dolibarr Supplier Orders. GRNI entries require careful sequencing to maintain AP match integrity; we migrate GRNI as draft supplier invoice records with linked receipt references. Purchase order approvals and authorization workflows do not migrate as automation; we document the workflow rules for admin to rebuild in Dolibarr.

iScala SC inventory items, warehouse locations, lot numbers, and serial numbers map to Dolibarr Products (stocked) and the Stock module. Lot and serial tracking flags preserve as product extrafields in Dolibarr. We sequence stock migration to include receipt transaction history so that lot and serial links remain intact; migrating only current balances without transaction history would break traceability. Warehouse locations map to Dolibarr warehouse records with physical location extrafields for multi-site deployments.

iScala MP work orders, routings, and material allocations represent the most complex module-to-Dolibarr mapping because Dolibarr's core does not include full MRP or production scheduling. We migrate work order headers as Dolibarr Project records with production status tracked via project status fields. Routing sequences and labor standards migrate as project task extrafields. BOM structures migrate as Dolibarr product component relationships where the third-party MRP module is installed; otherwise we flag BOM data for manual rebuild and document the bill of materials for admin to recreate.

iScala HR and PA modules store employee records, compensation history, and payroll runs. Dolibarr's HR module handles employee records and time tracking, but payroll processing rules and tax calculations require manual configuration or a third-party payroll extension. Effective-dated records migrate as-is with date tracking preserved. Compensation history migrates as employee extrafields rather than native payroll records. We scope payroll migrations conservatively: employee masters and historical leave balances migrate; payroll calculation rules and tax configurations do not.

iScala AM asset masters, accumulated depreciation, and depreciation methods map to Dolibarr Assets. Asset locations, cost centers, and depreciation schedules migrate as asset extrafields. Asset associations to departments from iScala map to Dolibarr Projects or Third Parties depending on whether the asset is linked to a project or a location. Depreciation methods (straight-line, declining balance) translate to Dolibarr's depreciation configuration.

iScala PR project masters, WBS elements, budgets, and time entries map to Dolibarr Projects. We migrate project headers, current budget balances, and task hierarchies. Detailed time entries migrate as Dolibarr Project time tracking records. Billing records migrate as project invoice links where the project is linked to a customer Third Party. Complex WBS hierarchies with multi-level dependencies may require flattening into Dolibarr's two-level task structure, with deep WBS preserved in project extrafields.

iScala SM service order headers, line items, and field-service scheduling map to Dolibarr Interventions (service tickets). Technician assignments migrate as resource assignments or contact links on the intervention record. SLA flags and scheduling windows migrate as intervention extrafields. Open service orders migrate as draft or validated intervention records; completed orders migrate as closed records for historical reference.

iScala CM contract masters, terms, and billing schedules map to Dolibarr Contracts. Active contracts with billing cycles and associated customer or vendor Third Party records migrate as Dolibarr Contract records with line items representing recurring billing amounts. Contract status, start date, end date, and auto-renewal flags migrate as contract fields. Recurring billing schedules map to Dolibarr's contract frequency and billing period fields.

iScala UD custom fields on standard objects require schema inventory per iScala version (2.2 through 2022.1) because UD field definitions vary significantly between releases. We inventory all UD fields during discovery, map their types to Dolibarr extrafield types (varchar, int, float, datetime, select, checkbox), and create the corresponding Dolibarr extrafield definitions before any data import. Any UD fields with no matching Dolibarr extrafield type are flagged for manual mapping review. UD field values migrate as extrafield data on the corresponding Dolibarr record.

iScala supports multiple companies and sites within a single SQL Server database. Dolibarr's standard installation is single-company; multi-company requires either separate Dolibarr instances per legal entity or the third-party multi-company Dolibarr extension. We scope each iScala company code as a separate migration unit, extract company-dependent records filtered by company code, and map site-specific configurations and inter-company transaction references to the customer's chosen multi-company strategy during scoping.

Document attachments stored outside the iScala SQL database (file shares, SharePoint, or Epicor document management) are not migratable via API or SQL query. We document the file location references during discovery and recommend a parallel file transfer process using the customer's existing file share access. For iScala attachments stored as SQL BLOB records, we extract and load them to Dolibarr's documents directory with references updated in the migrated records.