SuiteAnalytics Connect: NetSuite.com Data Source Removed in 2026.1 — Full Migration to NetSuite2.com Required

What changed

As of NetSuite 2026.1, the legacy NetSuite.com data source for SuiteAnalytics Connect is permanently removed. The NetSuite2.com data source is now the only available Connect data source. Any ODBC/JDBC connections, ETL pipelines, or BI tool integrations still pointing at the old data source will fail.

Key differences between NetSuite.com and NetSuite2.com

• Role-based access control — NetSuite2.com enforces role and permission restrictions on every query. The legacy data source had no such restrictions. Queries that previously returned all records may now return subsets or fail with permission errors depending on the executing role.
• Data Warehouse Integrator (DWI) role — A dedicated role that grants access to all Connect data except sensitive fields. This is the preferred role for warehouse ETL jobs. The Administrator role also works when authenticating via OAuth 2.0, but Oracle recommends DWI or custom roles instead.
• Authentication — Email/password login still works, but OAuth 2.0 is now the preferred method. OAuth 2.0 tokens persist across sessions; TBA tokens are single-session only. Plan to move any remaining email/password or TBA integrations to OAuth 2.0.
• Query language — Raw SQL is no longer supported. All queries must use SuiteQL, which is based on SQL-92 but has its own set of supported and unsupported functions. Existing SQL statements will need to be reviewed and rewritten.
• Schema changes — NetSuite2.com uses a different schema. Some record types and fields available in the old data source do not have direct equivalents. Oracle provides a NetSuite.com to NetSuite2.com Map and a list of records not directly mapped. The Records Catalog (in-product) shows available record types, fields, and the feature/permission requirements for each.
• Connection attribute — The Service Data Source property in your ODBC/JDBC driver configuration must be changed to NetSuite2.com.

How to identify stragglers

If you manage multiple integrations or users, you can audit who is still hitting the old data source in two ways:

1. Query the Connect Login Audit record type via SuiteAnalytics Connect itself.
2. Build a dataset in SuiteAnalytics Workbook using the Connect Login Audit record type.

What to do

1. Update driver configuration — Change the Service Data Source connection attribute to NetSuite2.com in every ODBC/JDBC DSN (Windows, macOS, Linux).
2. Switch to OAuth 2.0 — Migrate any email/password or TBA-based Connect integrations to OAuth 2.0. Create an integration record in NetSuite (Setup > Integration > Manage Integrations) with the appropriate OAuth 2.0 scopes.
3. Assign appropriate roles — Ensure Connect users have a role that grants access to the records they need. Use the Data Warehouse Integrator role for ETL/warehouse jobs. Review the Records Catalog for per-record permission requirements.
4. Rewrite SQL to SuiteQL — Audit every query in your BI tools, ETL scripts, and stored procedures. Replace unsupported SQL functions with SuiteQL equivalents. Oracle documents supported/unsupported functions under Using SuiteQL with the Connect Service.
5. Validate record and field availability — Cross-reference your existing queries against the NetSuite2.com schema. Use the NetSuite.com to NetSuite2.com Map for field-level mappings. For records listed under NetSuite.com Records Not Directly Mapped to NetSuite2.com Records, you may need alternative approaches (joins, custom records, or REST API fallbacks).
6. Audit remaining legacy connections — Use the Connect Login Audit record type to identify any users or integrations still targeting the old data source, and ensure they complete migration immediately.

Note: Oracle's documentation does not provide an exhaustive field-level migration reference inline. You will need to consult the Connect Schema documentation and the Records Catalog directly in your account to confirm specific field mappings and availability for your data model.