How to migrate from Epicor to Business Central
To migrate a client from Epicor to Business Central with superglue's AI agent, connect the client's Epicor data, and give superglue access to the client's Business Central 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 Business Central?
Migrating from Epicor to Business Central 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 Business Central
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 Business Central.
- 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 Business Central 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 Business Central?
The client signs in to Business Central with superglue's Microsoft app. superglue configures Business Central and loads the data through that access, in a Business Central sandbox environment first, in this order:
- 01
The chart of accounts, then the posting groups and the setup that links them to the accounts.
- 02
Dimensions, with the two global dimensions.
- 03
Number series, VAT or sales tax, payment terms and the allowed posting dates.
- 04
Customers, vendors and items with their posting groups.
- 05
The opening balances and the open items, posted through journals.
What moves from Epicor to Business Central?
| In Epicor | In Business Central |
|---|---|
| Chart of accounts | G/L accounts |
| Controlled and dynamic segments | Dimensions |
| Customers | Customers |
| Projects and phases | Projects |
| Suppliers | Vendors |
| Parts | Items |
| 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 open customer and vendor ledger entries with their original document numbers and due dates, so the aging in Business Central 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, account and dimension.
Which decisions do you make when you migrate from Epicor to Business Central?
- 01
Where do the Epicor segments go?
Business Central keeps one G/L account and adds the other segments as dimension values.
superglue maps the natural account to G/L accounts and each segment in use to a dimension.
- 02
How do Epicor jobs and methods become Business Central production?
Business Central runs production with production BOMs, routings and production orders, which come with the Premium license.
superglue maps methods of manufacturing to production BOMs and routings, and moves open jobs as production orders or closes them before cutover.
- 03
Which posting groups does the client need?
General business, general product, customer, vendor and inventory posting groups decide which G/L accounts sales, purchase and inventory documents post to.
superglue derives the posting groups from the accounts that each customer, vendor and item used in Epicor, so postings stay the same.
- 04
Which two dimensions become global dimensions?
Business Central shows two global dimensions on every entry and offers six more shortcut dimensions on documents.
superglue recommends the two dimensions the client filters on most, measured from how often each one is used in Epicor.
- 05
How much history moves?
Most clients need the open items plus one to two years of monthly balances in Business Central, 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 Business Central?
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.
Plan the time for the financial setup
The chart of accounts, dimensions and posting groups are the slow part of a Business Central setup. The standard API cannot create them, so consultants usually build configuration packages by hand. superglue builds this setup from the signed mapping and reads every value back before the first trial load.
Check posting groups on every new customer and vendor
Customers and vendors created by an integration start without posting groups unless a template sets them, and their first invoice fails to post. superglue fills the posting groups as each record is created, so the trial load posts cleanly.
superglue also runs the rest of the Business Central project. See the Business Central implementation
Frequently asked questions
Which data moves from Epicor to Business Central?
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 Business Central.
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 Business Central without my approval?
No. superglue only reads Epicor. Before any write to Business Central, 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 Business Central 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.