How to migrate from Epicor to Acumatica
To migrate a client from Epicor to Acumatica with superglue's AI agent, connect the client's Epicor data, and give superglue access to the client's Acumatica account. superglue assesses the data in minutes, plans every phase, recommends an answer to each decision, and runs a trial load that reconciles to the cent before cutover. You review, decide and sign off with the client.
This guide covers Epicor Kinetic, formerly Epicor ERP 10. Epicor plans its last on-premise Kinetic feature release for 2028, so many on-premise clients are planning their move now.
What are the steps to migrate from Epicor to Acumatica?
Migrating from Epicor to Acumatica takes six steps: connect both systems, assess the data, plan every phase, decide the mapping, run a trial load and cut over. Each load repeats exactly what you tested, and every write waits for your approval.
- 01
Connect Epicor and Acumatica
Connect Epicor read-only through its REST API with an API key and an integration user, or through the SQL Server database on premises. superglue writes nothing. The client then gives superglue access to Acumatica.
- 02
Assess the Epicor data
In minutes, superglue counts every record, finds the open items and lists the data issues with examples. You know the size of the migration before you quote it.
- 03
Plan every phase
superglue drafts the plan from discovery to cutover, with tasks, owners and the Epicor specifics already in it.
- 04
Decide the mapping
superglue brings each decision below with a recommendation from the client's own data. You confirm or change each answer, and the client signs the mapping.
- 05
Run the trial load
superglue loads an Acumatica test tenant and compares it with Epicor: the trial balance per period, the open receivables and payables per customer and vendor, and the inventory value. superglue explains every difference before cutover.
- 06
Cut over
At cutover, superglue loads the final data with the same steps as the trial load, and you sign the reconciliation with the client.
How do you get the data out of Epicor?
- Epicor cloud clients give superglue an API key and an integration user, and superglue reads through the REST API and business activity queries. On-premise clients can also give read access to the SQL Server database through the superglue gateway.
- Each REST session uses an Epicor license. Ask how many web service licenses the client has, because without them superglue uses a user license, and calls wait when all web service licenses are busy.
- Ask which companies, sites and GL books are in scope, because every company has at least one site and can keep several books.
On-premise clients install the superglue gateway once: Connecting to on-prem systems
What needs to be configured in Acumatica?
The client adds an API user and a connected application for superglue. superglue configures Acumatica and loads the data through that access, in an Acumatica test tenant first, in this order:
- 01
The features the client licenses, such as subaccounts, multicurrency and projects.
- 02
The subaccount structure, companies and branches, and the chart of accounts.
- 03
The financial year and its periods, opened for every migration date.
- 04
Cash accounts, credit terms, taxes and numbering, then the preferences and classes of each module.
- 05
Customers, vendors and items, then the opening balances and the open items.
Access setup for the client: Acumatica configuration guide
What moves from Epicor to Acumatica?
| In Epicor | In Acumatica |
|---|---|
| Chart of accounts | GL accounts |
| Controlled and dynamic segments | Subaccount segments and branches |
| Customers | Customers and customer classes |
| Projects and phases | Projects and project tasks |
| Suppliers | Vendors and vendor classes |
| Parts | Stock and non-stock items |
| Bank accounts | Cash accounts |
Open items
Open AR and AP invoices, open sales and purchase orders, inventory on hand per site with its cost, and open jobs with their work in process.
Open items load as AR and AP documents with their original numbers, dates and due dates, in an open financial period, so the aging in Acumatica matches on day one.
History
Epicor keeps posted GL transactions per book and fiscal period, and superglue reads every year the client wants to keep.
History loads as journal transactions per financial period, account and subaccount.
Which decisions do you make when you migrate from Epicor to Acumatica?
- 01
How do the Epicor segments become subaccounts?
Acumatica has one account and a segmented subaccount, which fits the Epicor account format well.
superglue maps the natural account to the account and the controlled segments to subaccount segments, with only the segments the client reports on.
- 02
How do Epicor jobs and methods become Acumatica production?
Acumatica Manufacturing Edition runs production with bills of material, routings and production orders.
superglue maps methods of manufacturing to bills of material and routings, and moves open jobs as production orders or closes them before cutover.
- 03
Which companies and branches does the client need?
In Acumatica, a company can have several branches. Branches drive balances, reports and access rights.
superglue recommends one company for each legal company in Epicor, and branches only where the client reports per site.
- 04
Which classes carry the defaults?
Customer and vendor classes set the accounts, terms and other defaults for every record in them, and item classes set the units, the valuation method and the posting class.
superglue proposes classes from the groups the client already uses, so each record gets its defaults from its class.
- 05
How much history moves?
Most clients need the open items plus one to two years of monthly balances in Acumatica, and older years as yearly balances. The client keeps the older detail in an archive.
superglue recommends two years of monthly balances per account, and full transaction detail only where the client needs to look into single transactions.
What are the common challenges when you migrate from Epicor to Acumatica?
Account logic is spread across many records
Epicor decides posting accounts through GL controls on the company, the part class, the product group, the part and other records, and reason codes can override them. Walk through the account logic with the controller before the mapping starts, because the new system sets accounts in fewer places. superglue traces which control set each account in the client's posted transactions.
Costing is set per site
The costing method on a part is only a default, and each site keeps its own costing method. Agree one costing method per site in the new system before inventory values move.
Visible IDs can change
Customer and supplier IDs can be edited, while transactions point to hidden numbers. superglue links every transaction through the hidden number, so a renamed customer keeps its history.
Brief the controller on equity accounts
Acumatica has no equity account type, so equity accounts are set up as liability accounts and shown as equity on the balance sheet. Controllers who read the account list often ask about it, so explain it before they see it.
Finish the preferences before the first trial load
Acumatica does not load the records of a module until that module's preferences are complete. Put the preferences in the configuration plan ahead of the first trial load.
superglue also runs the rest of the Acumatica project. See the Acumatica implementation
Frequently asked questions
Which data moves from Epicor to Acumatica?
The chart of accounts, customers, vendors and items, the open items, and as much history as the client needs. The mapping table on this page shows where each record lands in Acumatica.
Can superglue read Epicor cloud without database access?
Yes. superglue reads Epicor cloud through the REST API and business activity queries, with an API key and an integration user.
Does superglue write to Acumatica without my approval?
No. superglue only reads Epicor. Before any write to Acumatica, it shows the target, the connection and a transformed sample, and waits for your approval.
How do I know the migration is complete?
superglue reconciles the trial load and the final load against Epicor: the trial balance per period, the open receivables and payables per customer and vendor, and the inventory value. You get a reconciliation report to sign with the client.
What happens when I start this migration?
You sign up and connect the client's systems. If you want to see a full migration run first, superglue can set up Pinecrest Supply, a sample client.
Start your Epicor to Acumatica migration
Sign up and connect the client's systems, or let superglue set up Pinecrest Supply, a sample client, to see a full migration run first.