Consulting

NetSuite

NetSuite development and cleanup

Scripts, SuiteQL, saved searches and reports that have to agree with the ledger. Our own MokuBot runs inside NetSuite, so this is daily work.

sales@mokuhub.com. We reply within 24 hours.

Two things we do end to end

Migration and reporting

SuiteScript 1.0, 2.0, 2.x → 2.1

SuiteScript 2.1 migration, end to end

Oracle has published the dates. Legacy scripts stop running in 2028.2, and 2.0 scripts start running as 2.1 a release earlier. We take the whole job: inventory, conversion, testing and deployment.

2027.1
SuiteScript 1.0 gets critical fixes only.
2028.1
2.0 and 2.x scripts run as 2.1 by default.
2028.2
All scripts must be 2.1. Legacy versions stop running.

Source: NetSuite 2026.2 September minor release notes.

  • Inventory of what is deployed and used, including 1.0 form scripts with no script record
  • Retire what nothing runs before converting
  • Conversion checked against known breaking changes, like 0-based sublist indexing
  • Sandbox testing on the 2.1 runtime, then a deployment you approve

Suitelet + React

Custom reports and dashboards inside NetSuite

When a saved search page is not enough: a React app served by a Suitelet. Opens from a NetSuite menu, no separate login, no outside hosting.

  • Data from SuiteQL and saved searches
  • Filters, charts and drill-down to the underlying records
  • Your NetSuite roles decide who can open it
  • Source in your repository

Starting points

What people bring us

  • A script that passes in sandbox and hits governance limits in production.
  • AP Aging and the general ledger disagree at month end.
  • A saved search formula that disagrees between Results and Summary.
  • Finished work in sandbox with no safe way to production.
  • A customization nobody documented, by a developer who has left.

Scope

The work itself

Build and fix

  • SuiteScript 2.1: user event, client, Suitelet, Map/Reduce, scheduled, RESTlet
  • SuiteQL and saved searches
  • Workflows, custom records and fields
  • SuiteApps and SDF projects
  • Governance limits and script performance

Move and reconcile

  • Sandbox to production migration
  • CSV and API data migration
  • AP, AR and GL reconciliation reporting
  • Permissions and role design

Process

How an engagement runs

  1. 01

    We restate the problem

    In writing, before any quote.

  2. 02

    You get a written scope

    What we build, what we leave alone, what access we need.

  3. 03

    Work happens in your sandbox

    Reviewable pieces in your repository. Progress is commits, not calls.

  4. 04

    Handover, then production

    Docs, a walkthrough, and a deployment you approve. The code is yours.

FAQ

Common questions

Send us what is not working

Which script, search or report misbehaves, and what you tried. We reply with what we would check first.

Describe the problem

sales@mokuhub.com. We reply within 24 hours.