Step 7 of 11 · Implementation · Updated November 19, 2026

Sage X3 data migration

After mapping sign-off, a Sage X3 data migration is a controlled load. superglue's agent shows you the target and a transformed sample, waits for your approval, loads in batches, and reconciles source and target. The same saved tools run the trial load and the production load, so production gets exactly what you tested.

How this step works

What the agent does

  • Builds the load as saved tools that run the same way every time, with no AI at execution time.
  • Loads in small batches and reports rejected records with the reason.
  • Reconciles record counts and totals between source and target after each load.
  • Runs timed trial loads, so you know how long the final load takes.

What you decide and approve

  • When a batch is safe to load. Every write pauses for your approval.
  • How rejected records are fixed: in the source, in the mapping or by hand.
  • Whether a reconciliation difference blocks the next load.

What the client gets

  • A reconciliation report for each load.
  • A list of rejected records with the reason.

What makes a Sage X3 data load work

  1. 01

    Pick the load path for each object

    The REST web API reads every module, but writes only objects that Sage has moved to its newer framework. Older objects load through SOAP web services or import templates. Decide the path per object before you quote the migration.

  2. 02

    Test each file before the load

    The import function has a test option that checks the file definition without importing it. Run it on each file before the real load.

  3. 03

    Correct rejects in temporary storage

    A record with errors is not imported, and the next records still are. With temporary storage on, rejected lines stay in a storage area where they can be corrected and imported again.

  4. 04

    Keep the import log

    The import log shows the result of each import and the items to act on. Keep it with the reconciliation for each load.

  5. 05

    Reconcile per company and ledger

    Check the trial balance of each company and each ledger, not only the folder total. A correct total can hide a wrong company.

Frequently asked questions

How do you load data into Sage X3 safely?

Pick the load path for each object; Test each file before the load; Correct rejects in temporary storage; Keep the import log; Reconcile per company and ledger. The agent runs the trial and the production load with the same saved tools.

Does superglue write to Sage X3 without approval?

No. Before any write, the agent shows the target, the connection and a transformed sample, and waits for your approval.

How does superglue work with our consultants?

superglue works alongside your team. The agent takes on the repetitive work, such as reading documents, drafting, mapping, loading and reconciling. Your consultants keep the client relationship and the decisions, and they approve every change to a client system.

Can we use our own implementation method?

Yes. Write your firm's method as a playbook, and every consultant and every session follows it. The documents the agent produces carry your firm's branding.

Which systems can we migrate from into Sage X3?

Common sources are Sage 300, Sage 100, Dynamics GP, Sage 200, Dynamics NAV, Epicor and QAD. The agent also reads Excel, CSV and XML exports and most systems with an API or a database.

Is client data safe?

superglue holds a SOC 2 Type 2 report and works under GDPR. Credentials are encrypted with AES-256. On the Enterprise plan, superglue can run on your own infrastructure.

How do we start?

Start with one live Sage X3 project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.