What does the audit cover?
Everything that moves data into or out of NetSuite without being written down: if a person or a script touches it on a schedule, it goes on the list.
- Scheduled scripts and RESTlets, and whoever last edited them.
- Saved-search exports that are emailed, uploaded or pasted into a spreadsheet.
- CSV imports someone runs by hand, and the template they use.
- Connectors and third-party tools that read or write NetSuite, with the credentials they use.
- Spreadsheets that hold a copy of NetSuite data and are edited by hand.
What do we record for each integration?
One row per integration, so the next person to inherit it does not have to reverse-engineer it. This is the documentation we hand back.
| We record | Why it matters |
|---|---|
| Purpose and business owner | Someone must be able to say why it exists and decide to change it. |
| What it reads and writes | Shows which integrations can change financial records and which only read. |
| Schedule and trigger | Explains why a number moved at 3 a.m. |
| Credentials and role used | Finds shared logins and over-wide access. |
| Last known good run | Tells you whether it is working today. |
| Failure behavior | Does it stop, skip, retry or write half a record? |
| Who is alerted, and how | A failure nobody hears about is the expensive kind. |
| What depends on it | Shows what breaks downstream if it stops. |
What happens after the audit?
We rank the integrations by risk with you, then replace them one at a time. The old one keeps running until the new one's output matches, so the cutover is a decision, not a leap.
- Rank by risk: writes to financial records, no owner, shared credentials and no alert come first.
- Rebuild the first one as a Make scenario with a named owner, a narrow integration role and an error alert.
- Run old and new side by side and compare the output until they agree.
- Retire the old one and record the date and who agreed.
- Add a last-run check, so a scenario that silently stops running is noticed, and keep the run history for as long as audit needs.
We leave alone anything that works, is documented and is monitored. A script doing its job is not a problem to fix.
What do you hand back?
A written inventory, a risk ranking, and for each rebuilt integration: a description, an owner, an alert path and run history. This page makes no claim about savings.
- The inventory with the fields above.
- A ranked list of what to rebuild first and why.
- For each scenario we build, a one-page description in plain language.
- A short runbook: what the alert means and what to do when it fires.
Frequently asked questions
What access do you need to start?
A read-only view of what exists: the list of scripts and scheduled searches, and the people who know the history. You choose what we can see, and we do not need to write to NetSuite to inventory it.
Will you delete our scripts?
No. We retire an integration only after its replacement has matched it side by side and you have agreed.
Can we do the audit without rebuilding anything?
Yes. The inventory and risk ranking are useful on their own. Rebuilding is a separate decision.
Where does this fit with NetSuite scoping and licence questions?
That is a different job. For scoping, quotes and implementation questions, see our NetSuite consulting guides.
Want us to look at your NetSuite processes?
We build and run automations and integrations around your existing NetSuite account; we do not replace it. See our NetSuite guides and services, and the Make Enterprise NetSuite page, and the workflow automation page.





