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

Sage X3 testing and UAT

Testing shows that the configured Sage X3 runs the client's processes from end to end. In UAT, client users confirm it with their own data and their own roles. superglue's agent writes the test scripts from the signed requirements, runs the system tests in the sandbox, and tracks UAT results and defects with the client.

How this step works

What the agent does

  • Writes test scripts per process from the requirements and the design.
  • Runs system tests with test transactions in the sandbox, and records the results.
  • Shares a UAT tracker with the client testers and collects their results.
  • Links each defect to the requirement and the setting it affects.

What you decide and approve

  • Which processes go through UAT, and who tests them.
  • Which defects block go-live.
  • When the client signs off UAT.

What the client gets

  • Test scripts with the results of each run.
  • A UAT sign-off per process.

What makes Sage X3 testing and UAT work

  1. 01

    Test in a copy of the folder

    A test folder is a copy of the folder, made in the management console, with its own endpoint for the test users. Copy it before each test cycle, so the scripts rerun on the same data.

  2. 02

    Test with the client's profiles

    Log in as a user with each function profile and its access codes. An administrator login skips the rights you need to test.

  3. 03

    Follow each document to the journal

    Post a sales invoice, a purchase invoice and a stock movement, then open the journals. Check that each line takes the account the accounting codes should give it.

  4. 04

    Test the signature circuits

    Run purchase requests and orders above and below each amount limit. Test what happens when a signer is absent or rejects.

Frequently asked questions

How do you test a Sage X3 implementation before go-live?

Test in a copy of the folder; Test with the client's profiles; Follow each document to the journal; Test the signature circuits. The agent writes the scripts from the signed requirements and runs the system tests in the sandbox.

Do client testers need a superglue account?

No. The agent shares the UAT tracker as a link. Testers record their results there, and the agent sees them in the project.

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.