How to migrate from Epicor to Dynamics 365 Finance and Operations
To migrate a client from Epicor to Dynamics 365 Finance and Operations with superglue's AI agent, connect the client's Epicor data, and give superglue access to the client's Dynamics 365 Finance and Operations 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 Dynamics 365 Finance and Operations?
Migrating from Epicor to Dynamics 365 Finance and Operations 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 Dynamics 365 Finance and Operations
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 Dynamics 365 Finance and Operations.
- 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 a Finance and Operations sandbox environment 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 Dynamics 365 Finance and Operations?
The client registers an app in Microsoft Entra ID and adds it on the Microsoft Entra applications page in Finance and Operations, linked to a service user with the right security roles. superglue configures Dynamics 365 Finance and Operations and loads the data through that access, in a Finance and Operations sandbox environment first, in this order:
- 01
Legal entities, the fiscal calendar and the accounting and reporting currencies.
- 02
The chart of accounts and its main accounts.
- 03
Financial dimensions and the account structures that decide which combinations are valid.
- 04
Posting profiles, number sequences, payment terms and tax setup.
- 05
Customers, vendors and released products, then the opening balances and the open items through data management.
What moves from Epicor to Dynamics 365 Finance and Operations?
| In Epicor | In Dynamics 365 Finance and Operations |
|---|---|
| Chart of accounts | Main accounts |
| Controlled and dynamic segments | Financial dimensions |
| Customers | Customers in the global address book |
| Projects and phases | Projects |
| Suppliers | Vendors in the global address book |
| Parts | Released products |
| Bank accounts | Bank 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 customer and vendor transactions through general journals with their original due dates, so the aging in Finance and Operations 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 general journal lines per month, main account and financial dimension.
Which decisions do you make when you migrate from Epicor to Dynamics 365 Finance and Operations?
- 01
Where do Epicor sites go?
Finance and Operations keeps sites and their warehouses inside each legal entity.
superglue recommends a site with its warehouses for each Epicor site.
- 02
How do Epicor jobs and methods become Finance and Operations production?
Finance and Operations runs production with bills of materials, routes and production orders.
superglue maps methods of manufacturing to bills of materials and routes, and moves open jobs as production orders or closes them before cutover.
- 03
How many legal entities does the client need?
A legal entity in Finance and Operations has its own ledger, currency and tax setup, and can share the chart of accounts and financial dimensions with other legal entities.
superglue recommends one legal entity for each legal company in Epicor.
- 04
Which financial dimensions go into the account structures?
Account structures decide which combinations of main account and financial dimensions are valid, with up to ten dimensions besides the main account.
superglue proposes account structures from the combinations the client actually posted in Epicor, so invalid combinations are blocked from day one.
- 05
How much history moves?
Most clients need the open items plus one to two years of monthly balances in Dynamics 365 Finance and Operations, 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 Dynamics 365 Finance and Operations?
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.
Sign the chart of accounts before anything posts
The chart of accounts of a ledger cannot change after transactions post to it. Get the chart signed before the first trial load posts anything.
Financial dimensions are shared across legal entities
Custom financial dimensions apply to every legal entity, and their values hold up to 30 characters. Agree one dimension design for all companies in scope, and shorten long legacy codes before the mapping.
One party can be a customer and a vendor everywhere
The global address book keeps each organization once, across legal entities and roles. Agree how duplicates across the old companies merge, because an address change then updates every role.
Frequently asked questions
Which data moves from Epicor to Dynamics 365 Finance and Operations?
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 Dynamics 365 Finance and Operations.
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 Dynamics 365 Finance and Operations without my approval?
No. superglue only reads Epicor. Before any write to Dynamics 365 Finance and Operations, 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 Dynamics 365 Finance and Operations 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.