CPQ Bundles Deprecated — Migration to SuiteApps Required

What changed

Since February 2023, NetSuite CPQ has been repackaged from monolithic bundles into a collection of individual SuiteApps. The legacy bundles now receive critical fixes only — all new features and enhancements ship exclusively through the SuiteApps.

Bundle-to-SuiteApp mapping

The original Configurator bundle has been broken into four SuiteApps. Here is the full mapping:

• Configurator (Bundle 108493) → four SuiteApps:
  • NetSuite CPQ Configurator
  • NetSuite CPQ Manufacturing
  • NetSuite CPQ Ecommerce Integration
  • NetSuite CPQ Proposal Generator
• Guided Selling (Bundle 134221) → NetSuite CPQ Guided Selling
• SCA Extension (Bundles 337385 / 351171 / 352603 / 137418) → NetSuite CPQ SuiteCommerce Integration

Settings and record changes

• Options record split: Settings that previously lived on the single CPQ Configurator options record have been distributed to the options record of each corresponding SuiteApp. Any scripts or workflows that read or write fields on the old options record must be re-pointed.
• Proposal → Template rename: The proposal record is now called template. Create new templates at CPQ > Proposal Generator > Templates. Saved searches, scripts, or integrations referencing the old record ID or label may break.
• UI label updates: The Configurator SuiteApp ships with renamed UI labels for consistency across the platform. Custom scripts that match on label text (e.g., in client scripts or Suitelets) should be reviewed.

New menu paths

• Manufacturing settings — CPQ > Manufacturing > Settings (includes Convert WO button options: Top/Bottom checkbox, Line Item checkbox)
• Background Configurator debug tool — CPQ > Ecomm Integration > BC Launcher
• Proposal Generator settings — CPQ > Proposal Generator > Settings (Custom roles centers, Export/Import, Proposal Generator button, PDF filtering)

What to do

1. Contact NetSuite Support first. Oracle explicitly states you should contact Customer Support before attempting the migration.
2. Audit your customizations. Search your account for scripts, workflows, saved searches, and integrations that reference:
   • Bundle 108493, 134221, 337385, 351171, 352603, or 137418
   • The CPQ Configurator options record and its fields
   • The proposal record type
   • Any hardcoded CPQ menu paths or UI labels
3. Follow Oracle's migration process. The documented sequence is:
   1. Install the Migration Bundle for CPQ Configurator
   2. Export bundle data
   3. Uninstall the latest bundle version
   4. Install the SuiteApp and import bundle data
   5. For SuiteCommerce, follow the separate bundle-to-SuiteApp move procedure
4. Update references post-migration.
   • Re-point any scripts reading CPQ options to the new per-SuiteApp options records.
   • Replace proposal record references with template.
   • Update any SuiteScript or SuiteTalk code that navigates CPQ menu paths programmatically.
5. Test in Sandbox. Run the full migration in a sandbox account first. Validate all CPQ-dependent workflows, scheduled scripts, and SuiteCommerce product detail pages before touching production.

Gaps in the source

The release notes do not specify the internal IDs for the new SuiteApp options records or the new template record type ID. After installing the SuiteApps, inspect the records at the documented menu paths and use N/record or the Records Browser to confirm the correct type identifiers before updating your scripts.