Migrating NetSuite’s Database from Legacy to NS2: Challenges and Key Insights

Transitioning NetSuite’s database from the old version to NS2 is far from straightforward. As I discussed in my previous post, numerous variables come into play, including changes in field and table names and structural differences. Additionally, differing values within fields and table linkages necessary to retrieve data that was inherently present in the original tables under the old DB structure significantly elevate the migration risk.

Our team is still in the midst of this data migration process, and I'd like to share some essential tips for others undertaking similar migrations:

1. Rethink the Migration Approach Initially, I questioned whether to adapt the migration to fit the old table structures to enable a quicker transition to post-DWH outputs like BI reports or interfaces. However, I soon concluded that it’s more effective to start fresh by establishing new tables in the NS2 structure. This approach involves mapping out and prioritizing the critical fields we currently utilize for reports and interfaces, focusing on them in the initial phase.