NetSuite Health Check

Your NetSuite has grown since go-live. Know what it does before the next change.

If your instance has become difficult to maintain, or you have not reviewed it for some time, ask us about a Health Check. It maps your instance and investigates the processes causing you trouble, so you can decide what to change.

Scripts, workflows, fields and their connections

If we remove this field, what breaks?

Severity

  • Custom field
  • Approval scripthigh
  • Integrationmedium
  • Saved searchlow

Not every field, script and workflow added since go-live is mapped.

Every script, field and workflow is mapped. Risks are marked. You know what breaks.

  • Transaction
  • Workflow
  • Custom record
  • Role
  • Form
  • Unknown link
  • Mapped dependency

When the Health Check is the right step

If any of this sounds familiar

The system has slowed down

If your system is slow or your closing process takes too long, we investigate the cause. Often the cause sits in the scripts. Some can be merged, some removed, and the rest made more efficient.

Every change feels like a risk

Before you remove a field or change a workflow, you need to know which scripts and records depend on it.

NetSuite after go-live

The value gap

At go-live, NetSuite is configured around the business you have then. Since go-live, both have changed. NetSuite adds capabilities; your team takes on new products, markets and processes.

The value gap is the difference between what NetSuite could deliver for your business today and what you actually get from it. Keeping the configuration and working methods from go-live leaves that gap to grow.

The Health Check shows where you are missing value and what needs to change in your processes, tools, automation or use of AI.

Available value and the value you use

  • What NetSuite can deliver
  • Value gap
  • Your setup at go-live
  • Value you get today

Step one

Which scripts and fields does each transaction depend on?

Our scanner creates an inventory of your scripts, workflows, custom records and fields, including their dependencies. You receive it as a navigable map. The scan runs inside your own NetSuite account. We do not export your data or store it anywhere else.

Open a transaction to see its related records. Open a script to read what it does and which business rule it implements. Before removing a field, check where it is used.

Step two

How does the process actually run?

We work through the process with the people who run it and compare what they need with what your instance actually does. The inventory helps us trace the problem through the configuration and code.

Cloudmaven at the meeting table with Magnolia's team during their NetSuite go-live.
Cloudmaven with Magnolia's team at their NetSuite go-live, after eight months of work on financial core, procurement and SuiteBilling.

Process

Which steps are necessary? Where does work get delayed or repeated? We review the way the process is organised before recommending system changes.

Tools

Does the configuration still match how you work? We assess settings, fields and workflows against your current requirements.

Automation

Which scripts and integrations support the process? We examine their dependencies and opportunities to optimise or merge them.

AI

Would AI help with the problem you brought us? We assess that alongside process changes and existing NetSuite functionality.

Step three

What should you change first?

You receive a technical and functional roadmap based on the problems we investigated. It shows which working practices to change, which settings to adjust, which scripts to optimise or merge, and where standard functionality could replace a custom build. The Health Check is a paid service, and its scope depends on how complex your instance is. The technical analysis, explained in plain English with its technical roadmap, takes about two days. If we also review your core business processes, the time depends on how many processes we go through. Most Health Checks take two to five days.

After the Health Check

Choose which changes to implement

We discuss the findings with you and agree which recommendations to take forward. Some problems can be fixed quickly. Others, including changes to established working practices, need a separate project. The Health Check gives you the basis for that decision.

Eric Jean Head of Customer Success

What is not working in your NetSuite?

Tell us which processes need attention so we can agree the scope of the review with you. Involve the people who run the affected process so we can understand the problem together.