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

Sage X3 configuration

Configuration builds the signed design in Sage X3: features, setup records, numbering, roles and workflows. Done by hand, it is hours of screens that are hard to review and hard to repeat in production. superglue's agent applies the setup through the Sage X3 API, in the sandbox first, and records each change it makes.

How this step works

What the agent does

  • Turns the signed design into a configuration plan for your review.
  • Applies the setup through the API in the sandbox.
  • Records each change, so the configuration can be reviewed and repeated.
  • Repeats the tested configuration in production.

What you decide and approve

  • The setup values that only the client can decide.
  • Every write. Each one pauses for your approval.
  • When the sandbox configuration moves to production.

What the client gets

  • A configured sandbox and production account.
  • A configuration workbook that lists every setting.

What to get right in Sage X3 configuration

  1. 01

    Change activity codes in the test folder first

    Each change to an activity code needs a folder revalidation, and revalidation runs only when no user is connected. Test the change in the test folder, then schedule it in production.

  2. 02

    Follow the setup order

    The account core model comes before the company, and a site needs its company. Open the fiscal year before its periods, in each company.

  3. 03

    Settle categories before the product load

    Sage recommends creating the folder category first and then the site categories. A later change to a category does not update existing products or product-site records.

  4. 04

    Grant access by profile

    Function profiles set which functions users can run, and access codes protect data in read, write and execution modes. Build both per business role.

Frequently asked questions

What should you get right when configuring Sage X3?

Change activity codes in the test folder first; Follow the setup order; Settle categories before the product load; Grant access by profile. The agent applies the setup in the sandbox first.

Does superglue change Sage X3 without approval?

No. The agent shows each change before it writes and waits for your approval. Production repeats the configuration you tested in the sandbox.

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.