Migrate from Epicor iScala to Microsoft Dynamics 365 Business Central

iScala GL journal entries, chart of accounts, and financial periods map to D365 Finance's Ledger, FiscalCalendarEntity, and MainAccount structures. Multi-company deployments require each iScala company code to map to a separate D365 legal entity with its own fiscal calendar and chart of accounts. We preserve original journal entry numbers as a reference field and maintain exchange rates for multi-currency transactions. Financial dimension mapping is designed during schema design: iScala cost-centre and department fields map to D365 default dimension structures with up to 13 configurable financial dimensions.

iScala SL customer masters, open invoices, AR aging, and payment history map to D365 CustCustomerV3Entity and CustInvoiceJourEntity. Address and contact normalization occurs during field mapping: iScala's single-address-per-type model may require restructuring if the customer uses multiple delivery or invoice addresses per account. Outstanding invoice totals and aging data migrate to preserve AR continuity.

iScala PL vendor masters, open AP, purchase invoices, and payment history map to D365 VendVendorV2Entity and VendInvoiceJourEntity. Multi-currency purchase transactions preserve exchange rates used at the time of the original transaction. GRNI (goods-received-not-invoiced) entries from iScala's PC module require AP matching validation against received quantities in D365 before closing.

iScala OR order headers and lines with pricing, discounts, quantities, and fulfillment status map to D365 SalesOrderHeaderV2Entity and SalesOrderLineV3Entity. Open orders migrate with their current status; order history migrates with line-level detail preserved. iScala's warehouse assignment flags map to D365 warehouse and site structures. D365 requires the related customer account to exist before order headers insert, so SL migration precedes OR migration.

iScala PC purchase order headers, lines, and receipt records map to D365 PurchTableEntity and PurchLineEntity. GRNI entries require AP matching logic: goods received in iScala but not yet invoiced must align with the corresponding D365 Product Receipt records before AP matching proceeds. Vendor assignments and pricing agreements migrate as vendor trade agreements in D365.

iScala SC inventory items, warehouse locations, lot numbers, and serial numbers map to D365 InventTableEntity, InventLocationEntity, InventDimEntity, and the lot and serial number tables. Lot and serial tracking flags are preserved as metadata on inventory transactions. We sequence stock migration to include receipt transaction history so that lot and serial links to receipt records remain intact in D365, preserving traceability for regulated industries (pharma, food, automotive).

iScala MP work orders, routings, production schedules, and material allocations map to D365 ProdTable (production orders), ProdRoute (routings), and BOM (bill of materials) structures. D365 uses parametric production control with MES capabilities not present in iScala, so work order parameter structures require field-level mapping review per the customer's production workflow. Routing sequences and labor standards map to D365 route operations with workstation and capacity planning configurations.

iScala HR employee records, compensation history, and payroll runs map to D365 HcmWorkerEntity and DirPersonNameEntity structures. Effective-dated records migrate with their start dates preserved for audit continuity. iScala payroll processing rules and tax configurations do not have direct D365 equivalents; these require separate payroll configuration review by the customer's HR administrator or a payroll implementation specialist. PA module benefit plan assignments map to HcmBenefitDetailEntity where supported.

iScala AM asset masters, accumulated depreciation, depreciation methods, and asset locations map to AssetTable, AssetBook, and AssetLocation structures in D365. Depreciation schedules and methods (straight-line, declining balance, units of production) transfer with the asset. Asset associations to departments or cost centres migrate as D365 default dimensions on the asset book.

iScala PR project masters, WBS elements, budget balances, and time entries map to D365 ProjTable, ProjWbsTable, ProjBudgetLine, and ProjEmplTransEntity. Current budget balances migrate to ProjBudgetLine; detailed historical time entries migrate as ProjEmplTrans with ActivityNumber and ProjCategory mappings. Large time-entry volumes may require chunked migration with parent-project lookup resolution.

iScala SM service order headers, line items, and field-service scheduling map to D365 Field Service's WorkOrderHeader and WorkOrderProduct entities if the destination includes the Field Service module. Scheduling windows and SLA flags migrate as WorkOrderServiceTaskType and SLA configurations. If D365 Field Service is not included in the destination scope, service orders are mapped to the Project module for service contract tracking as a fallback.

iScala UD module custom fields attached to standard objects vary significantly between iScala versions (2.2 through 2022.1). We inventory all UD field definitions during discovery against the target version's UD table structure and map each to a corresponding D365 custom field (on the matching entity) or extension property. Any UD fields with no matching destination property are flagged for manual mapping review before migration begins. UD fields used for compliance or audit trails are prioritized over operational-use UD fields.

iScala stores company-dependent data under company codes within the same database alongside company-independent system data. We query company codes from the iScala system configuration during discovery and build a per-company extraction filter into every table pull. Each iScala company code maps to a separate D365 legal entity with its own chart of accounts, fiscal calendar, and posting profile. Multi-site configurations map to D365 sites and warehouses under each legal entity.

iScala CM contract masters, terms, billing schedules, and associated customer records map to D365 ProjTable with contract type and ProjInvoiceScheduleEntity. Active contracts with billing cycles and associated customer or vendor references migrate to D365 project contract billing structures. Contract line items mapping depends on whether the customer uses service, rental, or subscription contract types in iScala.

Document attachments stored outside the iScala SQL database (file shares, SharePoint, or Epicor's document management) do not migrate via API or SQL extraction. We document the file location references during discovery and recommend a parallel file migration using SharePoint or Azure Blob Storage migration tooling. The customer's IT team or a document migration specialist handles the file move with path remapping to the new D365 document management location.