CPQ Configurator Migration: Required Bundle 596110 Preserves Config Records and Transaction Data

What Changed

Oracle now requires an intermediate migration bundle—NSCPQ Bundle Migration (Bundle ID 596110)—as part of the transition from the legacy NetSuite CPQ Configurator bundle to the replacement CPQ SuiteApp. This bundle is public and managed.

The migration bundle serves two purposes:

• It preserves configuration records and transaction field data created by the original CPQ Configurator bundle.
• It enables the original CPQ Configurator bundle to be cleanly uninstalled. Without it, the uninstall will fail.

Critical warning: Once installed, the migration bundle must remain in the account if you need to edit configured items that were added to transactions by the CPQ Configurator bundle. Uninstalling the migration bundle permanently deletes all transaction field data and configuration data originating from the CPQ Configurator bundle. There is no recovery path described in the documentation.

This step applies only to NetSuite CPQ Configurator. It does not apply to NetSuite CPQ Guided Selling.

What to Do

1. Ensure you have already updated the NetSuite CPQ Configurator bundle to the latest version before proceeding.
2. Navigate to Customization > SuiteBundler > Search & Install Bundles.
3. Search for NSCPQ Bundle Migration (Bundle ID 596110).
4. Click the bundle name, then click Install on the Bundle Details page.
5. After installation, export bundle data before continuing with the remaining migration steps (SuiteApp install, data import, bundle uninstall).
6. Do not uninstall the migration bundle if your account contains transactions with configured items you still need to edit.

Things the Source Doesn't Clarify

• The release notes do not specify which NetSuite release introduced this migration path or when the legacy CPQ Configurator bundle reaches end-of-life.
• There is no detail on which specific custom records, custom fields, or transaction body/line fields are preserved by the migration bundle. Before migrating in production, inspect the bundle contents in a sandbox to catalog the records and fields it touches.
• No SuiteScript or REST/SOAP API changes are called out, but any scripts referencing CPQ Configurator custom records or fields should be tested in sandbox after migration to confirm field IDs and record types remain stable.