Transition to NetSuite2.com: What Does This Mean for You?

Imagine NetSuite as the foundation of a well-oiled machine that has been running for twenty years. Even the best systems need an upgrade at some point. With support for NetSuite.com ending in 2025.1 and the full transition to NetSuite2.com in 2026.1, a major change is on the horizon. What does this mean for you, your organization, and your daily processes?

In this blog, we discuss why this transition is necessary, the key changes, and, most importantly, how to prepare. Whether you’re an experienced SuiteCloud Connect user or simply use NetSuite in the background, these insights will help you navigate the transition smoothly.

Why the Transition to NetSuite2.com?

Due to increasing demand for better security and more advanced data analytics capabilities, NetSuite is moving to NetSuite2. NetSuite2.com introduces a modernized data structure with several improvements:

• Role-based access: Data is accessible based on roles, ensuring greater control and security.
• New Data Warehouse Integrator (DWI) role: Full access to data without requiring administrator rights.
• Consistency in data analysis: SuiteAnalytics Workbook now offers a more stable and uniform data view.

While these improvements primarily occur behind the scenes, they also bring practical changes that impact how you use NetSuite.

What Changes for SuiteCloud Connect Users?

SuiteCloud Connect provides access to NetSuite data via ODBC, JDBC, or ADO.NET and is crucial for many businesses. With the transition to NetSuite2.com, the rules are changing:

• New data source: You must switch from NetSuite.com to NetSuite2.com as the source. This requires adjustments in external applications and BI tools.
• SuiteQL: The new query language SuiteQL replaces SQL. This means existing queries need to be rewritten to continue functioning. For more info on SuiteQL, click here.
• Authentication: Only Token-Based Authentication (TBA) or OAuth 2.0 will be supported. OAuth 2.0 is preferred due to the reusability of tokens.

What If You Don’t Use SuiteCloud Connect?

Even without SuiteCloud Connect, the transition brings changes, such as:

• Authentication methods: You’ll need to set up one of the new methods (TBA or OAuth 2.0), including for API connections. Often, this is already the case, and no changes are needed.
• Role-based access: Access to data will be strictly controlled via roles, as in the User Interface. This may affect integrations that required broad access.

Action Points: What Can You Do Now?

The transition to NetSuite2.com requires preparation. To ensure a smooth changeover, it’s advisable to take the following steps:

Review current use of NetSuite.com:
Using the ConnectLoginAudit record, identify which users and connections still rely on NetSuite.com and whether the drivers are up-to-date. Also, update the data source to NetSuite2.com in your external applications. Check with your vendor to ensure they are ready for NetSuite2!

Rewrite SQL queries to SuiteQL:
NetSuite2.com will work with SuiteQL, which offers more capabilities than the older SQL version. Therefore, these queries need to be rewritten with SuiteQL (SQL-92). A useful resource is the SuiteAnalytics Workbook or the Records Catalog (Setup > Records Catalog), where you can view the updated record types and fields.

NetSuite has also released a handy sheet with the main database changes.

Request it here

Test your reports and integrations
Many fields and record types in NetSuite.com have changed or are no longer available in NetSuite2.com. Testing thoroughly is essential!

Looking Ahead

The transition to NetSuite2.com requires adjustments but also provides a solid foundation for the future. By taking action now, you can avoid stress and fully benefit from the new possibilities.

Do you have questions or need help with the transition? Contact us; we’re happy to assist!

Ruben de Niet
NetSuite consultant