How to migrate from Epicor to SAP S/4HANA
To migrate a client from Epicor to SAP S/4HANA with superglue's AI agent, connect the client's Epicor data, and give superglue access to the client's SAP S/4HANA 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 SAP S/4HANA?
Migrating from Epicor to SAP S/4HANA 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 SAP S/4HANA
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 SAP S/4HANA.
- 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 the SAP S/4HANA quality or test system 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 SAP S/4HANA?
In SAP S/4HANA Cloud, the client sets up a communication user and the communication arrangements for the APIs superglue uses. On premise, the client activates the OData services for a technical user. In SAP S/4HANA Cloud, the implementation team sets the organizational structure in Central Business Configuration, and superglue prepares and checks the values. superglue then loads the data through the Migration Cockpit, in the quality or test system first, in this order:
- 01
Group currency, the fiscal year variant and the company codes with their currencies. In the public cloud, the fiscal year variant cannot change after activation.
- 02
The chart of accounts. In the public cloud, every company code uses the standard chart of accounts, so the client's accounts map into it.
- 03
Profit centers, cost centers and segments for reporting.
- 04
Business partner settings, house banks, payment terms and tax codes.
- 05
Business partners and products, then the G/L balances and open items at the migration key date.
What moves from Epicor to SAP S/4HANA?
| In Epicor | In SAP S/4HANA |
|---|---|
| Chart of accounts | G/L accounts |
| Controlled and dynamic segments | Profit centers, cost centers and segments |
| Customers | Business partners in the customer role |
| Projects and phases | Projects |
| Suppliers | Business partners in the supplier role |
| Parts | Products |
| Bank accounts | House banks and 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 through the Migration Cockpit as receivables and payables open items at the migration key date, with their original due dates, so the aging in SAP S/4HANA 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 monthly G/L balances for earlier periods through the historical balance migration object, for reporting only, and older detail stays in an archive the client keeps.
Which decisions do you make when you migrate from Epicor to SAP S/4HANA?
- 01
Where do Epicor sites go?
SAP S/4HANA keeps sites as plants under each company code, and inventory, production and costing all run per plant.
superglue recommends one plant for each Epicor site.
- 02
How do Epicor jobs and methods become SAP production?
SAP S/4HANA runs production with bills of material, routings and production orders, all tied to the plant.
superglue maps methods of manufacturing to bills of material and routings per plant, and moves open jobs as production orders or closes them before cutover.
- 03
How many company codes does the client need?
A company code is a legal entity in SAP S/4HANA, with its own currency and books, and it belongs to one country.
superglue recommends one company code for each legal company in Epicor.
- 04
Which migration key date does the client use?
The migration key date sets the posting date for the balances and open items of each company code. Fixed assets have their own transfer date.
superglue recommends the last day of a closed period, so the opening balances match an approved trial balance.
- 05
How much history moves?
Most clients need the open items plus one to two years of monthly balances in SAP S/4HANA, 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 SAP S/4HANA?
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.
Rehearse every load in the test system
In SAP S/4HANA Cloud, migrated data cannot be deleted or loaded again. Run each load in the quality or test system with a new migration project per cycle, and load production once the reconciliation is signed.
Customers and vendors become one business partner
SAP S/4HANA keeps a company once as a business partner with a customer role, a supplier role or both. Agree with the client how duplicates across the old customer and vendor lists merge, because the address and bank details are kept once.
Every line needs its profit center
SAP S/4HANA keeps G/L, controlling and asset postings in one journal. Document splitting puts a profit center and a segment on each line, and lines on cost accounts also carry a cost center. Agree the profit center and cost center design before balances move, because the migrated balances carry them.
superglue also runs the rest of the SAP S/4HANA project. See the SAP S/4HANA implementation
Frequently asked questions
Which data moves from Epicor to SAP S/4HANA?
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 SAP S/4HANA.
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 SAP S/4HANA without my approval?
No. superglue only reads Epicor. Before any write to SAP S/4HANA, 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 SAP S/4HANA 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.