NetSuite· Testing and UAT
OverviewMCP server
Pre-implementation
  1. Implementation plan
  2. Discovery
  3. Data assessment
  4. Solution design
Implementation
  1. Configuration
  2. Data mapping
  3. Data migration
  4. Testing and UAT
  5. Cutover
Post go-live
  1. Hypercare
  2. Handover
Step 8 of 11 · Implementation · Updated October 26, 2026

NetSuite testing and UAT

Testing shows that the configured NetSuite 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.

Start a NetSuite projectTalk to us

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 NetSuite testing and UAT work

  1. 01

    Test under the real role

    Run each test script with the role the user will have. The Administrator role hides permission and form problems.

  2. 02

    Check the GL impact

    Run each process from the first document to the posting, and check the GL Impact of each transaction. A correct document can still post to the wrong account or segment.

  3. 03

    Test on migrated data

    Run UAT in a sandbox loaded with the trial migration. Users recognize their own customers and items and find mapping errors faster.

  4. 04

    Agree exit criteria before UAT starts

    Define which defect severities block sign-off, and who signs each process. Without them, UAT ends when the calendar runs out.

From NetSuite partners
18
ERP implementation firms in Pine Services Group
10,000+
customers served by those firms

Pine Services Group is rolling superglue out across its 18 ERP implementation firms, starting with The Vested Group on NetSuite.

Read the announcement

Frequently asked questions

How do you test a NetSuite implementation before go-live?

Test under the real role; Check the GL impact; Test on migrated data; Agree exit criteria before UAT starts. 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 NetSuite?

Common sources are QuickBooks, Sage 50 and Sage 100, Microsoft Dynamics GP, Xero and spreadsheets. 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 NetSuite project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.