Sage 100
Sage X3
Migrations · Updated November 19, 2026

How to migrate from Sage 100 to Sage X3

To migrate a client from Sage 100 to Sage X3 with superglue's AI agent, connect the client's Sage 100 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.

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

Migrating from Sage 100 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 Sage 100 and Sage X3

    Connect Sage 100 read-only through the Sage 100 Business Object Interface on the client's server, or through the SQL Server database on Sage 100 Premium. superglue writes nothing. The client then gives superglue access to Sage X3.

  2. 02

    Assess the Sage 100 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 Sage 100 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 Sage 100: 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 Sage 100, and superglue loads the open items with the same steps as the trial loads. After the client closes the last period in Sage 100, superglue loads the final balances, and you sign the reconciliation with the client.

How do you get the data out of Sage 100?

  • The superglue gateway runs on a computer with Sage 100 installed and reads with a Sage 100 user. Sage 100 Premium can also be read straight from SQL Server.
  • When superglue reads through the Sage 100 business objects, each session uses a user license while it runs, so superglue signs out after each task and the client keeps working.
  • Ask which third-party enhancements the client uses, because they keep data in their own tables.

The client installs 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 Sage 100 to Sage X3?

In Sage 100In Sage X3
General ledger accountsGeneral accounts
Account segments such as division and departmentAnalytical dimensions
Customers by AR divisionCustomers
JobsProjects
Vendors by AP divisionSuppliers
Items and product linesProducts
Bank codesBank accounts

Open items

Open invoices, credit memos and unapplied cash, open AP invoices, open sales and purchase orders, and inventory on hand per warehouse.

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

Sage 100 keeps history as long as the retention settings allow. superglue reads all of it and reports the first complete year.

History loads as journal entries per period, account and dimension.

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

  1. 01

    Where do Sage 100 account segments go?

    A Sage 100 account has a main account segment and up to nine more segments, such as division and department. Sage X3 keeps the general account and records the other values as analytical dimensions on each line.

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

  2. 02

    How do the Sage 100 costing methods move?

    Sage 100 sets a costing method on each item: standard, average, FIFO, LIFO, lot or serial. Sage X3 sets the valuation method per product and site, and tracks lots and serial numbers on the product.

    superglue proposes the valuation method for each product and site from the item's costing method, makes lot and serial items lot-controlled or serial-controlled products, and loads the opening stock per lot or serial number.

  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 Sage 100, 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 Sage 100 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 Sage 100 to Sage X3?

The AR division is part of the customer number

The same company can exist as 01-ACME and 02-ACME, with separate balances. superglue finds these pairs and proposes one customer, with the division kept for reporting.

Product lines decide the accounts

Each product line holds the sales, cost of goods sold and inventory accounts for its items. superglue maps the product lines to the account defaults in the new system, so postings stay the same.

Enhancements add their own tables

Third-party enhancements add fields and tables that the standard exports miss. Agree with the client which of them move before you set the scope.

Registers that were not updated sit outside the general ledger

Sales journals and AP invoice registers that were entered but not updated do not appear in the general ledger, and neither does a Daily Transaction Register that was not updated. superglue lists them before each load.

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 Sage 100 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.

Does superglue write to Sage X3 without my approval?

No. superglue only reads Sage 100. 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 Sage 100: 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 Sage 100 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