How to migrate from Epicor to NetSuite
To migrate a client from Epicor to NetSuite with superglue's AI agent, connect the client's Epicor data, and give superglue access to the client's NetSuite 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 NetSuite?
Migrating from Epicor to NetSuite 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 NetSuite
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 NetSuite.
- 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 NetSuite sandbox account 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 NetSuite?
The client turns on the SuiteCloud features and adds an integration record for superglue. superglue configures NetSuite and loads the data through that access, in a NetSuite sandbox account first, in this order:
- 01
Subsidiaries and their base currencies.
- 02
Accounting preferences and periods.
- 03
The chart of accounts, then departments, classes and locations.
- 04
Custom fields, records, segments, forms and workflows, and SuiteScript where the design needs it.
- 05
Customers, vendors, contacts and items, then the opening balances and the open items.
Access setup for the client: NetSuite configuration guide
What moves from Epicor to NetSuite?
| In Epicor | In NetSuite |
|---|---|
| Chart of accounts | Accounts |
| Controlled and dynamic segments | Departments, classes and locations |
| 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 invoices, credit memos, vendor bills and vendor credits with their original numbers and dates, so the aging in NetSuite 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 entries per month, account and segment.
Which decisions do you make when you migrate from Epicor to NetSuite?
- 01
Where do the Epicor segments go?
NetSuite keeps one account and offers departments, classes, locations and custom segments for the rest.
superglue maps the natural account to NetSuite accounts and each segment in use to a NetSuite segment.
- 02
How do Epicor jobs and methods become NetSuite production?
NetSuite runs production with assembly items, bills of materials and work orders, and routings need the manufacturing routing feature.
superglue maps parts with a method of manufacturing to assembly items with bills of materials, and moves open jobs as work orders or closes them before cutover.
- 03
How many subsidiaries does the client need?
In NetSuite OneWorld, subsidiaries set the currency, the tax and which customers and vendors each company can use. Changing them after go-live means reworking master data.
superglue recommends one subsidiary for each legal company in Epicor, decided before any master data loads.
- 04
Which item types do the items become?
NetSuite separates inventory, non-inventory, service, other charge, kit and assembly items. Non-inventory and service items can be for sale, for purchase or for resale.
superglue proposes the type for each item from how the client bought and sold it.
- 05
How much history moves?
Most clients need the open items plus one to two years of monthly balances in NetSuite, 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 NetSuite?
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.
Lock the subsidiary structure before the first load
The currency of a NetSuite subsidiary is fixed once its first transaction is saved, so a late change means a new subsidiary and a reload. Get the structure signed in the design phase.
Plan the sandbox around refreshes
A sandbox refresh replaces everything in the sandbox, including your configuration. superglue keeps the configuration and applies it again, so a refresh does not cost you the setup work.
superglue also runs the rest of the NetSuite project. See the NetSuite implementation
Frequently asked questions
Which data moves from Epicor to NetSuite?
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 NetSuite.
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 NetSuite without my approval?
No. superglue only reads Epicor. Before any write to NetSuite, 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 NetSuite 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.