NetSuite2.com Migration
Use this guide to transition from the legacy NetSuite.com data source to the NetSuite2.com data source. It outlines key changes in field mappings and naming conventions to ensure a smooth migration.
NetSuite.com to NetSuite2.com map
To migrate from NetSuite.com to the NetSuite2.com data source, you must modify your queries. To do this, you must know the corresponding ID of a field, list, or record in NetSuite2.com. You can refer to NetSuite's spreadsheet to learn about the mapping between the NetSuite.com and NetSuite2.com entities. For more information about how to use the spreadsheet, see NetSuite's documentation.
This list is not exhaustive and will be continually updated with new record mappings. You can check the latest updates in the SuiteAnalytics Release Notes section released on Help Center Weekly Updates.
Custom field names in NetSuite2.com
NetSuite.com and NetSuite2.com handle the naming of custom fields differently. To query these fields in NetSuite2.com, you must understand the naming conventions of both of these data sources. You can refer to NetSuite's Understanding Custom Records, Lists, and Field Naming document to learn about their naming conventions.
NetSuite2.com data models
Fivetran offers two dbt Core*-compatible data models for NetSuite SuiteAnalytics. These models support both the NetSuite.com and NetSuite2.com connections. You must set the netsuite_data_model variable in your dbt_project.yml file to netsuite2 to run the NetSuite2.com version of the package. For more information, see our NetSuite SuiteAnalytics Data Models documentation.
* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.