Epicor
Sage X3
Migrations · Updated November 19, 2026

How to migrate from Epicor to Sage X3

To migrate a client from Epicor to Sage X3 with superglue's AI agent, connect the client's Epicor data, and give superglue access to the client's Sage X3 account. superglue assesses the data in minutes, plans every phase, recommends an answer to each decision, and runs trial loads that reconcile 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 January 2028, with active support until December 31, 2029, so many on-premise clients are planning their move now.

What are the steps to migrate from Epicor to Sage X3?

Migrating from Epicor to Sage X3 takes six steps: connect both systems, assess the data, plan every phase, decide the mapping, run trial loads and cut over. Each load repeats exactly what you tested, and every write waits for your approval.

  1. 01

    Connect Epicor and Sage X3

    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 X3.

  2. 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.

  3. 03

    Plan every phase

    superglue drafts the plan from discovery to cutover, with tasks, owners and the Epicor specifics already in it.

  4. 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.

  5. 05

    Run the trial loads

    superglue loads a Sage X3 test folder and compares it with Epicor: the trial balance per period, the open receivables and payables per customer and vendor, the uncleared bank items, and the inventory value. superglue explains every difference, and you repeat the trial load until a full run reconciles with no new differences. The last run is a timed rehearsal of the cutover.

  6. 06

    Cut over

    At cutover, the client stops entry in Epicor, and superglue loads the open items with the same steps as the trial loads. After the client closes the last period in Epicor, superglue loads the final balances, 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 claims an Epicor license. Ask how many web service licenses the client has, because without them superglue uses a user license.
  • 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 X3?

The client adds a Sage X3 user for superglue and names the folder superglue loads into. superglue configures Sage X3 and loads the data through that access, in a Sage X3 test folder first, in this order:

  1. 01

    The charts of accounts and the analytical dimension types.

  2. 02

    The ledgers and the account core model.

  3. 03

    Companies and sites, with the legislation and the currencies of each company.

  4. 04

    The fiscal years and periods of each company, and the dimension values.

  5. 05

    Accounting codes, payment terms and tax codes.

  6. 06

    Customers, suppliers and products, then the opening balances and the open items through import templates.

What moves from Epicor to Sage X3?

In EpicorIn Sage X3
Chart of accountsGeneral accounts
Controlled and dynamic segmentsAnalytical dimensions
CustomersCustomers
Projects and phasesProjects
SuppliersSuppliers
PartsProducts
Bank accountsBank 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 supplier open items with their original numbers, dates and due dates, so the aging in Sage X3 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 period, account and dimension.

Which decisions do you make when you migrate from Epicor to Sage X3?

  1. 01

    Where do the Epicor segments go?

    An Epicor GL account combines the natural account with controlled segments such as division and department. Sage X3 keeps the general account and records the other values as analytical dimensions.

    superglue maps the natural account to general accounts and each segment in use to a dimension type.

  2. 02

    How do Epicor methods of manufacturing move?

    Epicor keeps the components and the operations of a part together in one method of manufacturing. Sage X3 keeps a BOM and a routing apart, and a routing can apply to one site.

    superglue splits each method into a Sage X3 BOM and a routing, maps resource groups to work center groups and resources to work centers, and moves open jobs as work orders or closes them before cutover.

  3. 03

    How many companies and sites does the client need?

    In Sage X3, a company keeps the legal books, and sites hold the financial, sales, purchasing, inventory and production activity.

    superglue recommends one company for each legal company in Epicor, and a site for each location that keeps inventory or its own books.

  4. 04

    Which analytical dimensions does the client need?

    Sage X3 records analytical dimensions on journal lines, each account can require or default them, and the client chooses which dimension types to use.

    superglue proposes dimension types from the segments and fields the client actually reports on.

  5. 05

    Which cutover date does the client use?

    A cutover on the first day of a period lets the open items and balances load as of one date. A fiscal year start keeps the year's reports and year-end filings in one system, and a date in the middle of the year means combining two systems for the audit and the tax returns. Avoid a date when the team must close the books or report results.

    superglue recommends the first day of a month, and the first day of the fiscal year when the client can wait for it. The final balances load after the last period in Epicor is closed.

  6. 06

    How much history moves?

    Most clients need the open items plus one to three years of monthly balances in Sage X3, at least the current and the prior fiscal year for comparison, 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 X3?

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.

Every object loads through its own import template

Sage X3 imports each object through an import template, with the same checks as manual entry, and the import log lists every record that fails. superglue builds the import files and explains every rejected record.

Customers and suppliers are business partners

Sage X3 keeps each trading partner once as a business partner, which can be a customer, a supplier or both. Agree with the client how duplicates across the old customer and vendor lists merge.

Activity codes switch features on

Sage X3 turns features and field sizes on with activity codes. Some are set when the folder is created, and every change needs a folder revalidation. Agree the activity codes in the design phase.

Open items must not count twice

Open invoices and bills post to the receivables and payables accounts when they load, and the opening trial balance holds the same amounts. Load the open items and the opening balances against one conversion account, and check that it ends at zero.

Plan fixed assets as their own stream

The trial balance brings the cost and the accumulated depreciation, but the asset register needs each asset with its in-service date, useful life and depreciation to date, and tax books need their own values. Agree early where the register lives after go-live, and reconcile it to the asset accounts.

superglue also runs the rest of the Sage X3 project. See the Sage X3 implementation

Frequently asked questions

Which data moves from Epicor to Sage X3?

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 X3.

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 X3 without my approval?

No. superglue only reads Epicor. Before any write to Sage X3, 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, the uncleared bank items, 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 Northwind Outdoor Supply, a sample client.

Start your Epicor to Sage X3 migration

Sign up and connect the client's systems, or let superglue set up Northwind Outdoor Supply, a sample client, to see a full migration run first.

Migrations to Sage X3