Your NetSuite customizations have a deadline. Oracle's releases through 2028 will stop certain scripts and integrations from working. If your team built custom workflows or connected external systems years ago, those tools may break without warning.
This is not a drill. Oracle's SOAP deprecation schedule, the 2028.2 release will disable SOAP web services that many businesses still depend on. SuiteScript 1.0 stops working at the same time. If your team manages NetSuite services with legacy code, the clock is ticking. Testing now saves money and prevents chaos later.
Key Takeaways
Is NetSuite right for you?
Six honest questions. We'll tell you straight - even if it's "not yet."
Your verdict
A strong fit
Understanding the Impact of NetSuite Updates on ERP Customizations
NetSuite releases two major updates each year. The 2027.1 and 2027.2 releases include breaking changes. These updates will retire tools that many businesses still use every day.
What Is Changing
Oracle has set firm deadlines for older technologies. Here is the timeline based on official Oracle documentation:
| Change |
Deadline |
Impact |
| SOAP 2025.2 endpoint only |
2027.1 |
Older SOAP endpoints stop working |
| SuiteScript 1.0 limited support |
2027.1 |
Only critical bugs get fixes |
| NLAuth for RESTlets |
2027.1 |
Authentication method stops working |
| New TBA integrations |
2027.1 |
No new Token-Based Auth allowed |
| SuiteScript 2.0/2.x on 2.1 engine |
2028.1 |
Scripts run on newer engine |
| All legacy SuiteScript to 2.1 |
2028.2 |
Must migrate to 2.1 runtime |
| SOAP web services |
2028.2 |
Endpoint disabled completely |
| Existing TBA support |
Tentatively 2028.2 |
TBA integrations stop working |
These deadlines come from Oracle's SuiteScript documentation. They mainly affect older technology. Newer scripts may need testing without full rebuilds.
Why This Matters for Your Business
Custom scripts handle critical tasks. They process orders. They calculate pricing. They sync data with other systems. When a script breaks, those tasks stop working.
The problem gets worse with scale. A wholesale distributor might have 50 or more custom scripts. Each one needs testing and possible updates. Waiting until the last minute creates rush projects and higher costs.
NetSuite customizations built years ago often lack documentation. The original developer may have left the company. Nobody knows exactly what the script does or why it was built that way.

Why Regression Testing is Your Best Defense Against Broken Customizations
Regression testing checks if updates break existing features. It catches problems before they reach production. For NetSuite releases, this testing is not optional.
What Regression Testing Does
Regression testing runs your custom scripts against new releases. It compares the results to expected behavior. When something works differently, the test flags it for review.
This process differs from other testing types. Unit testing checks individual functions. Smoke testing confirms basic features work. Regression testing goes deeper. It validates that everything still works together after changes.
How to Set Up Effective Regression Testing
Your testing strategy needs three parts:
Test Cases: Document what each script should do. Include inputs, expected outputs, and edge cases. Write these down before you start testing.
Test Environment: Use a sandbox account or Release Preview. Never test in production. One bad script can corrupt live data.
Test Schedule: Run tests before each NetSuite release. Oracle publishes release dates months ahead. Mark them on your calendar.
The goal is simple. Find problems in a safe environment. Fix them before they affect real users.
Key Steps to Prepare Your NetSuite Instance for the 2027 Release
Preparation starts with knowing what you have. Most businesses cannot list all their customizations from memory. Scripts pile up over years. Integrations connect to systems that may have changed owners.
Step 1: Audit Your Customizations
Go to Customization > Scripting > Scripts. Filter by API version. Export this list to a spreadsheet.
Look for these warning signs:
- Scripts marked as SuiteScript 1.0
- Scripts using nlapi functions
- Integration records using SOAP endpoints
- Token-Based Authentication on older integrations
The audit timeline depends on your account. Small accounts may need a short review. Larger accounts with many scripts may need more time.
Step 2: Check SOAP and TBA Integrations
Review Setup > Integration > Web Services Usage Log. This shows which systems call your NetSuite account. Note any using SOAP endpoints.
Also check Manage Integrations. Look for integrations using Token-Based Authentication. According to Oracle's authentication documentation, these need migration to OAuth 2.0.
Contact your integration vendors now. Ask about their migration timeline. Get commitments in writing. Some vendors move slowly.
Step 3: Access Release Preview
Oracle provides Release Preview accounts before each major release. These sandbox copies include upcoming features. You can test your scripts against new code before it goes live.
Administrators can request access through Setup > Company > Release Preview. They can also check upgrade notices in the What's New portlet.
Release Preview availability depends on your upgrade schedule. Oracle sends administrators the dates. Check those notices and plan testing early.
Step 4: Prioritize by Business Impact
Not all scripts matter equally. Order processing scripts affect revenue. A script that formats memos can wait.
Sort your audit list by criticality:
- Critical: Order-to-cash, billing, financial close
- High: Customer portals, inventory updates
- Medium: Internal workflows, reports
- Low: Formatting, notifications, nice features
Focus your testing time on critical and high items first.
Building a Robust Testing Plan for NetSuite Customizations
A testing plan turns good intentions into actions you can repeat. It defines who tests what and when. Without a plan, testing becomes random and incomplete.
Components of a Complete Testing Plan
Your plan should include:
Scope: Which scripts and integrations are included. Which are excluded and why.
Environment: Sandbox, Release Preview, or both. How to refresh test data.
Schedule: Test start date, duration, and completion deadline. Buffer time for fixes.
Roles: Who runs tests. Who reviews results. Who approves fixes.
Acceptance Criteria: What "passed" means for each test case.
Testing Approaches Compared
| Approach |
Best For |
Scope |
Skill Needed |
| DIY Testing |
Under 20 scripts, in-house developers |
Small to medium |
High |
| Partner Support |
20-100 scripts, limited internal resources |
Medium to large |
Medium |
| Full Migration Project |
100+ scripts, complex integrations |
Large or urgent |
Partner-led |
Choose DIY if you have developers who know NetSuite. Choose partner support if your team is stretched thin. Choose a full project if you have many scripts and tight deadlines.
User Acceptance Testing (UAT)
Technical tests prove scripts run without errors. UAT proves they work for real users.
Involve business users in testing. Have them run through normal tasks. Create orders. Process returns. Run reports. They will catch issues developers miss.
Document UAT results carefully. Business users often find problems they cannot explain technically. Screenshots help developers understand what went wrong.
Essential Areas to Focus On During Your 2027 Release Testing
Some customizations break more often than others. Focus your testing on high-risk areas first.
Custom Workflows
NetSuite workflows automate business processes. They trigger scripts. They send emails. They update records. A broken workflow can stop operations cold.
Test each workflow end-to-end. Create test records that trigger workflow actions. Verify every step completes correctly. Check that emails send and record updates.
Integrations
Your NetSuite account probably connects to other systems. Shipping carriers. Payment processors. Inventory tools. Each connection is a potential failure point.
NetSuite integrations using SOAP need the most attention. According to Oracle, these will stop working in 2028.2. Rebuilding them takes weeks, not days.
Test integrations with realistic data volumes. A sync that works for 10 orders may fail for 10,000. Performance problems hide until you scale up.
Saved Searches
Saved searches power dashboards, reports, and workflow conditions. They depend on field names and record structures. Updates can change both.
Run critical saved searches in Release Preview. Compare results to production. Look for missing records or wrong totals.
SuiteCommerce Storefronts
If you run a SuiteCommerce site, test every customer function. Product pages. Cart. Checkout. Order history.
SuiteCommerce uses SuiteScript on the backend. A script update can break the storefront without warning. Test after every release.
Roles and Permissions
NetSuite roles and permissions control who sees what. Custom roles may include permissions that change between releases.
Test each custom role after updates. Verify users can still access what they need. Check that restricted areas stay restricted.
NetSuite includes built-in tools for testing. Learning them saves time and catches more problems.
SuiteQL lets you query NetSuite data directly. It works like SQL but for NetSuite records. Use it to verify data integrity after updates.
Check record counts. Compare totals. Look for orphaned records. SuiteQL finds problems that saved searches miss.
Script Debugger
The debugger steps through SuiteScript code line by line. It shows variable values and execution paths. When a script fails, the debugger shows exactly where.
Learn to use breakpoints. These pause execution at specific lines. You can inspect what happened before the failure.
Sandbox Environments
Sandboxes copy your production account for testing. Changes in sandbox stay in sandbox. You can experiment without risk.
Refresh your sandbox before major testing. Old data creates false results. A fresh copy matches production more closely.
Web Services Logs
NetSuite provides separate logs for SOAP and REST. They help you review API activity and investigate failed requests.
Review these logs weekly during migration. They confirm old methods are phasing out. They catch systems you forgot about.
Post-Update Verification and Continuous Optimization
Go-live is not the finish line. Post-update monitoring catches problems that testing missed.
Immediate Post-Update Checks
Run these checks within 24 hours of any release:
- Critical workflows complete successfully
- Integrations sync without errors
- Dashboards show current data
- Users can perform key tasks
Document any issues immediately. Fresh details help troubleshooting.
Ongoing Monitoring
Set up alerts for script failures. NetSuite can email administrators when scripts throw errors. This beats finding problems in angry user tickets.
Track script performance over time. A script that runs in 2 seconds today may take 20 seconds after an update. Slow scripts frustrate users and hit governance limits.
Planning for Future Releases
The 2027 changes are not the last. NetSuite releases updates every six months. Build testing into your regular work.
Schedule quarterly reviews of your customizations. Look for scripts that need updates. Catch problems before they become emergencies.
Strong Fit and May Not Be Ideal
This Testing Approach Works Best If:
- You have 20 or more custom scripts or integrations in NetSuite
- Your team built customizations using SuiteScript 1.0 or SOAP
- You run a SuiteCommerce storefront with backend scripts
- Your business cannot afford downtime during month-end close
- You have internal developers who can run tests and make fixes
May Need Additional Support If:
- Your scripts lack documentation from original developers
- You have 100 or more customizations across multiple subsidiaries
- Vendor SuiteApps have unknown migration status
- Your team lacks NetSuite development experience
- You are starting this process in late 2027 or 2028
How Anchor Group Can Help With Your 2027 Testing
Testing and migrating NetSuite customizations requires expertise that not every team has in-house. Working with an experienced NetSuite consultant can help businesses prepare for major releases and avoid costly disruptions.
As an Oracle NetSuite Alliance Partner, Anchor Group helps businesses identify potential issues with scripts, integrations, and system updates before they affect operations.
How We Help
Our team provides:
- Customization audits: Review scripts and integrations through our NetSuite support services.
- Impact-based prioritization: Identify which customizations need immediate updates and which can wait.
- SuiteScript migration: Convert SuiteScript 1.0 to 2.1 for businesses with large script inventories.
- Integration modernization: Rebuild SOAP integrations using REST and OAuth 2.0.
- Deployment testing: Thoroughly test changes before moving them into production.
Our experienced NetSuite developers handle complex migration projects, helping businesses prepare for updates while minimizing operational risks.
Not sure where to start? Book a FREE 30-minute NetSuite fix consultation. We'll review your situation, identify potential concerns, and recommend practical next steps.
Our goal is simple: Help your business prepare for 2027 updates with reliable customizations, tested integrations, and fewer disruptions.

Frequently Asked Questions
What is the biggest risk of a NetSuite update to my customizations?
Scripts using old methods will stop working. SuiteScript 1.0 and SOAP web services will be disabled completely. There is no workaround once the deadline passes. Your only option is to migrate before the dates Oracle set.
Test before each major release. NetSuite releases happen twice per year. Oracle announces dates months ahead. Run tests in Release Preview during that window.
Can I test scripts without affecting production data?
Yes. Use sandbox accounts or Release Preview environments. These copies are separate from production. Changes in test environments stay in test environments. Never test new code directly in production.
What happens if a vendor SuiteApp is not updated in time?
Contact the vendor immediately. Get their migration timeline in writing. If they cannot commit to a deadline, plan for alternatives. You may need a different SuiteApp or a custom solution.
How long does a typical migration project take?
Timeline depends on your script inventory. Small accounts with under 20 scripts take less time. Large accounts with 100 or more scripts may need many months. Starting early gives you more options and lower costs.