← All fixed-scope offers

Fixed-scope offer · SuiteScript 2.1 & OAuth 2.0 Upgrade

SuiteScript 2.1 and OAuth 2.0 Upgrade: modernise your NetSuite code and integrations before the deadlines.

A NetSuite modernisation project from an independent NetSuite consultant: SuiteScript 1.0 rewritten in SuiteScript 2.1, integrations moved from token-based authentication to OAuth 2.0, SOAP web services moved to REST, and the code put under proper version control.

Fixed priceInventory first, then upgradeTested in sandboxNo disruption to users

1Why now

Two deadlines make this the right time to modernise:

NetSuite 2027.1

No new TBA integrations

Oracle has announced that from 2027.1, new integrations can't use token-based authentication (TBA). New integrations must use OAuth 2.0, and new authorisation-code integrations must use PKCE.

NetSuite 2028.2

SOAP web services removed

Oracle plans to remove SOAP web services in 2028.2, and has indicated that support for existing TBA integrations will end around the same time. Anything still on SOAP or TBA then stops working.

Today

SuiteScript 1.0 is frozen

SuiteScript 1.0 still runs, but all new capability is in SuiteScript 2.x. Older scripts are harder to maintain, slower to change and riskier at every upgrade.

Dates are from Oracle's published release notes and may change, so I check the latest guidance at the start of every project. For the detail, read NetSuite TBA to OAuth 2.0: what the 2027.1 and 2028.2 changes mean.

2What's included

Inventory and assessment

  • Every script, deployment and SuiteScript version
  • Every integration, its authentication and its endpoints
  • Risks, dependencies and a migration order

SuiteScript 1.0 to 2.1

  • Scripts rewritten in SuiteScript 2.1, not just converted
  • Scheduled scripts moved to Map/Reduce where it helps
  • Hard-coded IDs replaced with script parameters
  • Error handling and logging added

TBA to OAuth 2.0

  • Integration records and OAuth 2.0 set up
  • Client credentials (machine-to-machine) or authorisation code with PKCE
  • Celigo, Boomi and custom connections re-authenticated
  • Old tokens and access tidied up

SOAP to REST

  • SOAP web service calls moved to SuiteTalk REST and SuiteQL
  • RESTlets where REST doesn't cover a need
  • Payload and mapping changes tested end to end

Version control and deployment

  • Code moved into a SuiteCloud Development Framework (SDF) project
  • Source control in Git
  • A repeatable sandbox-to-production release process

Anything else that's due

  • Deprecated APIs and features in use
  • Unused scripts, deployments and integration records removed
  • Governance and performance tuned with APM

3What you receive

01

Modernisation assessment

An inventory of every script and integration with its risk, the work needed and a migration order.

02

Upgraded scripts

SuiteScript 2.1 code with parameters, logging and error handling, tested in sandbox before release.

03

Upgraded integrations

OAuth 2.0 authentication and REST endpoints in place, with old credentials retired.

04

Test evidence

Before-and-after results for every script and integration, signed off with your team.

05

Code in source control

An SDF project in Git, so future changes are tracked and repeatable.

06

Documentation and handover

What each script and integration does, how it's deployed, and a handover session.

4Plan and timescale

  1. Before we start

    Free inventory

    I list your scripts and integrations from a read-only role. You then receive a fixed price, a migration order and dates in writing.

  2. Phase 1

    Assess and plan

    Risks and dependencies confirmed, test cases agreed with process owners.

  3. Phase 2

    Upgrade in sandbox

    Scripts rewritten and integrations moved to OAuth 2.0 and REST, in batches, each tested.

  4. Phase 3

    Release to production

    Changes released in small, scheduled batches, outside your busiest periods and month-end.

  5. Phase 4

    Handover

    Documentation, Git repository and a handover session with your team.

Smaller estates of a few scripts and one or two integrations usually take about two weeks. Larger estates are delivered in phases.

5Who does the work

Every offer is delivered personally by Raja Saqib, a certified NetSuite consultant and CIMA-qualified accountant with more than 15 years of NetSuite implementation, integration and project recovery work, from start-ups to FTSE 250 and NASDAQ-listed groups.

SuiteHeroes is an independent NetSuite consultancy based in London, working with clients across the UK and worldwide. You deal with the consultant doing the work from the first call to the final report.

See my NetSuite experience →   Read the case studies →   All NetSuite consulting services →

6Common questions

Do existing TBA integrations stop working in 2027.1?

No. Oracle says existing TBA integrations keep working after 2027.1; the change stops new ones being created. But support is expected to end around 2028.2, so it's worth moving in a planned way rather than at the last minute.

Do we have to rewrite every SuiteScript 1.0 script?

Not necessarily all at once. The assessment ranks scripts by risk and business importance, so the critical ones are upgraded first and unused ones are removed.

Will users notice anything?

They shouldn't. Everything is tested in sandbox first and released in small batches, outside month-end.

Do you work with Celigo and Boomi connections?

Yes. Moving iPaaS connections to OAuth 2.0 is part of the upgrade, along with custom RESTlet and web service integrations.

Get ahead of the 2027 and 2028 deadlines

Book a free call and get an inventory of what needs upgrading.

Book a free 30-minute call