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.
Given these changes, several key questions arise for NetSuite support and the expert community:
Extraction Strategy: What should be the best approach to extract data from the new table structures? How can we ensure that all necessary data, including the newly joined fields, is captured efficiently?
Data Migration: What are the best practices for migrating old data and history that are currently connected to our DWH and BI systems? How can we ensure data integrity and continuity during this transition?
Early Movers: Has anyone in the community started addressing these issues? Are there shared insights or lessons learned from initial migration efforts that can benefit others?
As we prepare for this transition, collaboration and shared knowledge will be crucial. Let's leverage our collective expertise to ensure a smooth and efficient migration to the NetSuite2.com DB, minimizing disruptions and maximizing the benefits of the new structure.