How to migrate from Epicor to Sage Intacct
To migrate a client from Epicor to Sage Intacct with superglue's AI agent, connect the client's Epicor data, and give superglue access to the client's Sage Intacct 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 Sage Intacct?
Migrating from Epicor to Sage Intacct 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 Sage Intacct
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 Sage Intacct.
- 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 Sage Intacct sandbox or implementation company 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 Sage Intacct?
The client authorizes the superglue sender ID in Sage Intacct and adds a user for superglue. superglue configures Sage Intacct and loads the data through that access, in a Sage Intacct sandbox or implementation company first, in this order:
- 01
Multi-entity, the base currencies and the first fiscal month. Base currencies and the first fiscal month can change only before transactions exist.
- 02
The configuration of each module, such as General Ledger, Accounts Payable and Accounts Receivable, and the names of terms and dimensions.
- 03
Entities, locations, departments and the other dimensions.
- 04
The chart of accounts and the journals.
- 05
Customers, vendors and items, then the opening balances and the open items.
Access setup for the client: Sage Intacct configuration guide
What moves from Epicor to Sage Intacct?
| In Epicor | In Sage Intacct |
|---|---|
| Chart of accounts | GL accounts |
| Controlled and dynamic segments | Dimensions such as departments, locations and classes |
| Customers | Customers |
| Projects and phases | Projects |
| Suppliers | Vendors |
| Parts | Items |
| Bank accounts | Checking and credit card 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 invoices and AP bills with their original numbers, dates and due dates, so the aging in Sage Intacct 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 summary journal entries per month, account and dimension.
Which decisions do you make when you migrate from Epicor to Sage Intacct?
- 01
Where does manufacturing go?
Sage Intacct has inventory and kits but no production jobs, routings or manufacturing work in process.
superglue recommends finishing or closing open jobs before cutover, moving work in process as a journal entry, and keeping production in a manufacturing system the client chooses.
- 02
Where do the Epicor segments go?
An Epicor GL account combines the natural account with controlled segments such as division and department. Sage Intacct keeps one account and moves the rest into dimensions.
superglue maps the natural account to Sage Intacct accounts and each segment in use to a dimension, usually departments or locations.
- 03
Which companies become entities, and which become locations?
In Sage Intacct, an entity has its own books, tax and bank accounts. A location only adds a reporting value.
superglue recommends one entity for each legal company in Epicor, and locations for the sites inside a company.
- 04
Which records are shared across entities?
Customers, vendors and items can live at the top level and be shared, or belong to one entity.
superglue recommends shared customers and vendors, so each company appears once and intercompany reporting stays clean.
- 05
How much history moves?
Most clients need the open items plus one to two years of monthly balances in Sage Intacct, 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 Sage Intacct?
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.
Manufacturing needs a home
Jobs, methods of manufacturing and work in process only move to a system with manufacturing. Decide early where production runs after go-live, because it changes the scope of the project.
Plan module configuration as its own workstream
In Sage Intacct, the settings of General Ledger, Accounts Payable and the other modules cannot be imported like data. Unless the partner starts from a template company, they are set by hand, screen by screen. superglue sets them and checks every value, so the configuration is ready when the data is.
Agree user-defined dimensions with the person who reports on them
A user-defined dimension stays in Sage Intacct once it holds data. Add only the ones the client will report on, and get each one agreed before the first load.
superglue also runs the rest of the Sage Intacct project. See the Sage Intacct implementation
Frequently asked questions
Which data moves from Epicor to Sage Intacct?
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 Sage Intacct.
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 Sage Intacct without my approval?
No. superglue only reads Epicor. Before any write to Sage Intacct, 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 Sage Intacct 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.