ERP migration

Migrate from Epicor iScala to Acumatica

Field-level mapping, validation, and rollback between Epicor iScala and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.

Get a quote See object mapping
Epicor iScala logo

Epicor iScala

Source

Acumatica

Destination

Acumatica logo

Compatibility

92%

11 of 12

objects map 1:1 between Epicor iScala and Acumatica.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Epicor iScala organizes business data around a modular structure: General Ledger (GL), Sales Ledger (SL), Purchase Ledger (PL), Stock Control (SC), Sales Order Processing (OR), Purchase Order Processing (PC), and optional modules like Project Management (PR), Service Management (SM), and Asset Management (AM). Each module is company-dependent, supporting multi-company deployments with cross-border trading and multi-currency capabilities native to the financial core. Acumatica structures data around Customers, Vendors, Inventory Items, GL Accounts, Projects, and Cases, with custom fields prefixed 'Usr' and configuration through Customer Classes, Vendor Classes, and Branch/Warehouse locations. FlitStack AI extracts transactional data via Epicor iScala's native export and API endpoints, then loads into Acumatica through its REST contract-based API. We map iScala's chart-of-accounts structure to Acumatica's GL Account codes, multi-company cost centers to Acumatica Branches, and iScala's inventory sites to Acumatica warehouses with valuation-method awareness. Approval workflows, Service Connect integrations, and electronic billing configurations do not migrate — we document these for your Acumatica team to rebuild using Acumatica's Notification Templates, Approval Maps, and eInvoice connectivity.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Epicor iScala logo

Source platform

Epicor iScala platform overview

Scorecard, SWOT, gotchas, and pricing for Epicor iScala.
Acumatica logo

Destination platform

Acumatica platform overview

Scorecard, SWOT, gotchas, and pricing for Acumatica.

Data migration guide

The complete Acumatica migration guide

Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.

Destination checklist

Acumatica migration checklist

Pre- and post-cutover tasks for moving onto Acumatica.

Why teams make this switch

Two sides of the same decision

Leaving

Epicor iScala logo

Epicor iScala

What's pushing teams away

  • Built-in reports are described as difficult to use and the interface is not considered user-friendly, creating frustration with day-to-day reporting tasks.
  • The application does not support opening multiple windows simultaneously, forcing users to close one screen before accessing another — a workflow bottleneck for order processing teams.
  • Steep learning curve and limited documentation make implementation and ongoing administration challenging for under-resourced IT teams.
  • Outdated UI compared to modern cloud ERPs creates a usability gap that frustrates younger users and increases training costs.
  • Performance issues after migration to newer Epicor Kinetic environments have been reported when server resources are undersized, causing slower reporting and task execution.

Choosing

Acumatica logo

Acumatica

What's pulling them in

  • Unlimited user licensing lets companies add staff without per-seat billing shocks, making Acumatica cost-predictable at scale.
  • Flexibility and scalability earn consistent praise — users value a platform that adapts to vertical workflows without forcing a redesign.
  • Real-time visibility across financials, inventory, and projects gives mid-market businesses a consolidated operational view previously available only in enterprise-tier ERPs.
  • Cloud-native architecture with automatic updates removes infrastructure management burden from in-house IT teams.
  • Modular licensing lets companies start with one or two suites (Financials, Distribution) and expand into Manufacturing or CRM incrementally.

Object mapping

How Epicor iScala objects map to Acumatica

Each row shows how a Epicor iScala object lands in Acumatica, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Epicor iScala

GL Account (GL000)

maps to

Acumatica

GL Account

1:1
Fully supported

iScala GL accounts (Account Code + Subaccount structure) map directly to Acumatica GL Accounts. Subaccounts in iScala become Segments in Acumatica's consolidated chart of accounts. We preserve the full account code structure as Account CD and validate against Acumatica's segment count per your company structure.

Epicor iScala

Customer (SL200)

maps to

Acumatica

Customer

1:1
Fully supported

iScala Sales Ledger customers map to Acumatica Customers with Customer Class assignment based on iScala's customer category code. Primary ship-to address from iScala becomes the default shipping address in Acumatica. Multi-contact customers in iScala (one customer with multiple buyer contacts) are preserved with all contact records.

Epicor iScala

Vendor (PL200)

maps to

Acumatica

Vendor

1:1
Fully supported

iScala Purchase Ledger vendors map to Acumatica Vendors with Vendor Class assignment based on iScala's vendor category. Remit-to addresses from iScala map to Acumatica's Remit Address. 1099 vendor configuration requires manual setup in Acumatica after migration based on US tax requirements.

Epicor iScala

Inventory Item (SC100)

maps to

Acumatica

Stock Item

1:1
Fully supported

iScala Stock Control items map to Acumatica Stock Items with Item Class assignment. iScala sites map to Acumatica Warehouses with site-specific on-hand quantities translated to warehouse-level availability. Valuation method (Standard, FIFO, Moving Average) is read from iScala item setup and applied as the ValMethod on each Stock Item in Acumatica.

Epicor iScala

Sales Order Header (OR300)

maps to

Acumatica

Sales Order

1:1
Fully supported

Open sales orders from iScala map to Acumatica Sales Orders with order type, status, and all line details. Original order date and required dates are preserved as User-Defined fields since Acumatica's CreatedDateTime is set at import. SO Shipment Nbr references from iScala map to shipment records in Acumatica's Fulfillment workspace.

Epicor iScala

Purchase Order Header (PC300)

maps to

Acumatica

Purchase Order

1:1
Fully supported

Open purchase orders map to Acumatica Purchase Orders with vendor, terms, and line details. iScala's PO shipment handling (receipts against PO) requires Acumatica's Receipts workflow — we flag any partially-received iScala POs so your Acumatica team can receive remaining quantities manually or via Landed Cost entries.

Epicor iScala

Invoice (SL300 / SL310)

maps to

Acumatica

AR Invoice / AP Invoice

1:many
Fully supported

iScala invoices split by module: SL300 invoices become Acumatica AR Invoices tied to the Customer; SL310 invoices (intercompany or adjustment) map to appropriate GL Journal Entries in Acumatica. Fully paid invoices are migrated as historical records with payment reference; open invoices are migrated with balance due for continued collection.

Epicor iScala

Project (PR000 / PR100)

maps to

Acumatica

Project (PM)

1:1
Fully supported

iScala Project Management jobs and phases map to Acumatica Projects with phases as Project Tasks. Budget lines from iScala PR200 map to Acumatica Project Budget entries by task. Non-project costing in iScala (PR000 direct entries without a project) become Expired Costs in Acumatica Projects with the Allow Non-Project Transactions flag enabled.

Epicor iScala

Asset Register (AM100)

maps to

Acumatica

Fixed Asset

1:1
Fully supported

iScala Asset Management assets map to Acumatica Fixed Assets with asset class, acquisition date, acquisition cost, and depreciation method from iScala's depreciation profile. Accumulated depreciation to date of cutover is recorded as a separate depreciated-cost entry. Book values in Acumatica are recalculated after migration to match iScala's depreciation register.

Epicor iScala

Lot / Serial Number (SC200)

maps to

Acumatica

Lot/Serial Number

1:1
Fully supported

iScala lot and serial numbers from Stock Control map to Acumatica's lot and serial tracking on Stock Items. Active lots with remaining quantity map as open lot/serial records in Acumatica Inventory. Expired lots are migrated with expiration date preserved for compliance reporting.

Epicor iScala

UD Fields / Extended Properties

maps to

Acumatica

Custom Fields (Usr prefix)

1:1
Fully supported

iScala user-defined fields attached to customers, vendors, items, and orders require creation of matching Usr-prefixed custom fields in Acumatica. Each custom field's data type in iScala is matched to the appropriate PXDB attribute in Acumatica — string to PXDBVarChar, numeric to PXDBDecimal, date to PXDBDate. We deliver a field-mapping manifest before migration so your Acumatica admin creates the schema first.

Epicor iScala

Multi-Company Configuration

maps to

Acumatica

Branches + Tenant

1:1
Fully supported

Each iScala company code maps to a separate Acumatica Branch within the tenant. Branch-specific settings (tax zone, shipping terms, warehouse assignment) are configured per branch after data migration. iScala inter-company entries require Acumatica Inter-Branch Transactions setup — we provide the mapping rules and flag entries that need inter-branch journal creation.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Epicor iScala logo

Epicor iScala gotchas

High

Web Services license exhaustion degrades API performance

High

Multi-company schema requires per-company scoping

Medium

User-Defined (UD) field schema varies by iScala version

Medium

Linux container migration can break file share and report paths

Low

Stock lot and serial records require linked migration

Acumatica logo

Acumatica gotchas

High

API user licenses cap concurrent sessions and request throughput

High

Multi-tenant filtering requires CompanyID awareness

Medium

Custom fields require separate discovery before field mapping

Medium

Notes and attachments use a separate linked table structure

Low

Implementation timelines frequently run 3–9 months end-to-end

Pair-specific challenges

  • Multi-company iScala structures map to Acumatica Branches, not tenants

    Epicor iScala supports multiple company codes within a single database, each with its own chart of accounts, fiscal calendar, and currency settings. Acumatica uses a single-tenant model with Branches representing separate business units. When migrating multi-company iScala deployments, FlitStack AI maps each iScala company code to a distinct Acumatica Branch. Each branch needs its own Warehouse, Tax Zone, and Shipping Term assignment in Acumatica before data lands. Inter-company entries in iScala (e.g., IC invoices between company codes) require manual configuration of Acumatica's Inter-Branch Transaction rules after migration — we document each inter-company entry as a separate mapping artifact so your Acumatica admin can set up the corresponding branch-to-branch journal entries.

  • iScala Service Connect workflows do not transfer to Acumatica Approval Maps

    Epicor iScala uses Service Connect for EDI processing, approval routing, and automated document flows between modules. Acumatica's equivalent is Approval Maps for document-level approvals and Automation Schedules for recurring processing tasks. These are fundamentally different automation paradigms — Service Connect uses event-driven triggers with custom code (VBA or ICE), while Acumatica's Approval Maps use a rules-based configuration UI. We export your Service Connect workflow definitions as a reference document so your Acumatica implementation team can rebuild equivalent logic. EDI mappings for vendor portals or customer portals that run through Service Connect will require a separate integration rebuild using Acumatica's OData endpoints or a third-party EDI connector.

  • Inventory valuation method must be explicitly mapped per item

    Epicor iScala Stock Control allows different valuation methods (Standard, FIFO, Moving Average) per item and per site. Acumatica applies valuation at the Stock Item level — once set, the ValMethod field on InventoryID determines costing globally across all warehouses. Mismapping a Standard-cost item as FIFO in Acumatica will produce incorrect margins on existing inventory. FlitStack AI reads the iScala item valuation setup (SC100 and SC200 records) and maps each item's method to the matching Acumatica ValMethod. For items with site-level differing valuation in iScala, we flag them for your Acumatica admin to decide on a single method per item and document the decision.

  • iScala electronic billing configurations require Acumatica eInvoice rebuild

    iScala's electronic billing setup (particularly for Peppol, FatturaPA in Italy, and Germany-specific formats) is configured at the company level in iScala with country-specific format rules. Acumatica handles eInvoicing through its Tax Configuration module and built-in connectivity to Peppol Network and country-specific tax authorities. The billing format settings from iScala do not transfer — they must be reconfigured in Acumatica's eInvoice Setup screen. We document your current iScala electronic billing configuration (format type, tax authority codes, delivery endpoints) as a setup guide for your Acumatica admin to reproduce after migration.

  • Lot and serial tracking requires Acumatica License Configuration before migration

    iScala supports lot tracking and serial number tracking per item in Stock Control. Acumatica requires Lot/Serial tracking to be enabled at the License level (SM201060 — License Monitoring Console) before you can enable it on Stock Items. If your iScala setup uses lot or serial numbers on any items, the Lot/Serial feature must be activated in your Acumatica license before migration — this is a pre-migration configuration step that cannot be changed retroactively. We identify all iScala items with active lot/serial tracking and flag them so your Acumatica admin can enable the feature first.

Migration approach

Six steps for a successful Epicor iScala to Acumatica data migration

  1. Inventory iScala modules and export configuration

    FlitStack AI starts by profiling your Epicor iScala deployment — identifying which modules are active (GL, SL, PL, SC, OR, PC, AM, PR, SM), the number of company codes, and the volume of records per module. We connect to iScala using read-only credentials and export master data (chart of accounts, customers, vendors, items) followed by transactional records (open orders, open POs, invoices, receipts). For iScala versions without API access, we use iScala's built-in Export Data function with CSV output. We deliver a data inventory summary before any transformation begins so you can confirm scope.

  2. Configure Acumatica branches and custom fields

    Before data loads, your Acumatica admin (or our team) creates the Branch structure matching your iScala company codes, configures the chart of accounts with required segments, and builds Usr-prefixed custom fields matching iScala user-defined fields. We deliver a schema setup manifest listing every custom field to create, its Acumatica data type, and the iScala UD field it replaces. Acumatica's License Configuration (particularly Lot/Serial tracking) is verified at this stage. Customer Classes, Vendor Classes, Item Classes, and Warehouse records are created to match iScala category structures.

  3. Map master data with field-level validation

    FlitStack AI transforms iScala records to Acumatica format: GL accounts mapped to AccountCDs with subaccount segments, customers and vendors matched by code and validated against Acumatica's address and tax registration requirements, and Stock Items with valuation method and Item Class mapping. We run a field-level diff against a representative sample (typically 200-500 records per entity) before committing the full master data set. Currency exchange rates from iScala are imported into Acumatica's Currency Rate Types so multi-currency amounts display correctly. Unresolved mappings (unknown customer classes, missing tax zones) are flagged for manual resolution before the transactional migration runs.

  4. Migrate transactional history and open documents

    Open sales orders, purchase orders, and invoices are migrated with full line detail and original document dates preserved as custom User-Defined fields since Acumatica sets CreatedDateTime at import time. Project records with phases, tasks, and budget lines are loaded into the PM module. Fixed Assets with depreciation schedules are imported with accumulated depreciation to date of cutover. Closed periods in iScala are migrated as historical records with Status = Completed. We validate document totals against iScala's AR/AP aging reports to confirm no balance discrepancies before moving to inventory and financial history.

  5. Cut over with delta pickup for in-flight changes

    After master data and open transactions load, your team continues working in iScala during the final preparation window. The full migration commits against Acumatica. A delta-pickup window (typically 24-48 hours) captures any records created or modified in iScala during the cutover — new orders, new receipts, updated customer addresses. FlitStack AI generates an audit log of every record loaded, including source system ID for traceability and de-duplication. One-click rollback is available if post-migration reconciliation reveals data integrity issues. After delta pickup, iScala is placed in read-only mode and Acumatica becomes the system of record.

Platform deep dives

Context on both ends of the pair

Epicor iScala logo

Epicor iScala

Source

Strengths

  • Integrated multi-company, multi-currency General Ledger supporting real-time financial closing across subsidiaries.
  • Comprehensive manufacturing module (MP) with work orders, routings, and material production control.
  • Lot and serial number tracking in stock control (SC) for regulated industries like pharma and food.
  • Service order management (SM) with field-service scheduling for companies with on-site service operations.
  • Embedded reporting with iScala Query Designer and Crystal Reports for financial and operational analytics.

Weaknesses

  • UI is considered outdated compared to modern cloud ERPs, with no multi-window support limiting concurrent workflow.
  • Built-in reporting is difficult to use, driving users to external BI tools for ad-hoc analysis.
  • Limited public API documentation for iScala makes programmatic data extraction complex.
  • Web Services licensing model can cause degraded API response times when license pools are exhausted.
  • Steep implementation and training requirements for under-resourced IT and business user teams.
Acumatica logo

Acumatica

Destination

Strengths

  • Unlimited named-user licensing eliminates per-seat cost scaling as teams grow.
  • Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally.
  • Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities.
  • Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code.
  • Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.

Weaknesses

  • Steep learning curve and complex initial setup create significant onboarding friction.
  • Report Designer is widely cited as unintuitive and difficult to use for non-developers.
  • Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity.
  • Implementation timelines frequently exceed initial estimates, especially for multi-module deployments.
  • API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.

Complexity grading

How hard is this migration?

Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Epicor iScala and Acumatica.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Epicor iScala: Not publicly documented for iScala; Web Services license pool governs concurrent API sessions rather than a per-minute rate.

  • Data volume sensitivity

    B

    Epicor iScala doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Epicor iScala to Acumatica migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Epicor iScala to Acumatica data migrations

Answers to the questions buyers ask most during Epicor iScala to Acumatica migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Epicor iScala to Acumatica migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most iScala-to-Acumatica migrations complete in 48-72 hours for the data migration phase under 50,000 transactional records. Multi-company deployments with 500,000+ records or complex inventory setups (lot/serial tracking, multiple valuation methods) extend to 5-7 days. The longest planning steps are multi-branch configuration in Acumatica, custom field schema setup, and inventory valuation method validation. We provide a data inventory before migration so the timeline is confirmed against actual record counts.

Adjacent paths

Related migrations to explore

Other ways to leave Epicor iScala

Epicor iScala logo
Dolibarr ERP logo
Epicor iScala to Dolibarr ERP Migration
Epicor iScala logo
Epicor Prophet 21 logo
Epicor iScala to Epicor Prophet 21 Migration
Epicor iScala logo
Infor CloudSuite Corporate logo
Epicor iScala to Infor CloudSuite Corporate Migration

Other ways to arrive at Acumatica

ABRA Gen logo
Acumatica logo
ABRA Gen to Acumatica Migration
Access ERP logo
Acumatica logo
Access ERP to Acumatica Migration
Access SupplyChain logo
Acumatica logo
Access SupplyChain to Acumatica Migration

Same-ERP migrations

Acumatica logo
Dolibarr ERP logo
Acumatica to Dolibarr ERP Migration
Acumatica logo
Epicor Prophet 21 logo
Acumatica to Epicor Prophet 21 Migration
Acumatica logo
Infor CloudSuite Corporate logo
Acumatica to Infor CloudSuite Corporate Migration

Ready when you are

Move from Epicor iScala.
Land in Acumatica, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Book a call
Accuracy guarantee Rollback included Quote in 1 business day