As we approach the end-of-life (EOL) for the NetSuite.com database (Q1-2026), and with support ceasing by Q1-2025, it’s imperative for businesses to prepare for the migration to the new NetSuite2.com DB. The new database structure presents several changes and improvements that necessitate careful planning and execution.
Firstly, there are significant changes in the table structures and field names. For example, the “Transactions” table is now simply “Transaction,” and field names such as “Transaction_id” have been shortened to “id.” Additionally, field values have been modified; for instance, “Sales Order” is now abbreviated to “SalesOrd,” and boolean values have been standardized from “N/Y” to “False/True.”
Moreover, some fields that were previously part of the main tables are now maintained in separate tables, requiring joins to access them. For example, instead of having “Transaction_Lines.Company_id” directly in the transaction lines table, there is now a link to an “Entity” table that holds the company value. Similarly, “Item_unit_price” now needs to be extracted from a “Price” table with a join.
Additionally, there are changes in table behavior. For example, the “DATE_CREATED” field, which was part of the “Transaction_lines” table,
has been removed, and only “LINELASTMODIFIEDDATE” remains to identify changes in a row. Furthermore, in the “Transaction Line” table, instead of retaining old rows with updated statuses, rows are now deleted upon updates.
