Who should check?
Teams planning a migration from the legacy NetSuite CPQ Configurator bundle, and teams that have already migrated and still need existing configured transactions. The migration-bundle installation step does not apply to CPQ Guided Selling.
Published milestones
- Since February 2023 — historical support contextOracle describes legacy CPQ bundles as receiving critical fixes while SuiteApps receive enhancements. This is existing product history, not a new Ebenstead announcement.
- Migration bundle 1.0.0 — ID 596110Oracle documents a data-preservation step for Configurator migrations and retention of that bundle afterward.
- October 19, 2026 — Oracle release-note updateThe CPQ release notes describe the improved migration process. No calendar migration deadline is stated.
Check your Oracle account notice before scheduling an update.
A practical response
- Confirm which CPQ components are installed and contact NetSuite Customer Support before planning the migration. Do not remove bundles as routine cleanup.
- Document the installation, export and import sequence, including the migration bundle that must remain. Rehearse the process and validate retained configuration and transaction data in a suitable test account.
- Test editing representative existing configured transactions and the affected quoting processes. Record acceptance and the retained-bundle requirement before approving production changes.
What we’ll review
Installed CPQ bundle and SuiteApp versions, the presence of NSCPQ Bundle Migration (ID 596110), configuration and transaction dependencies, export/backup requirements, a test account and the Oracle support plan.
See a related project
Explore our release-preparation approach →Sources and updates
Oracle documentation
Update history
- 2026-10-24 — First published from verified Oracle documentation. Product dates and versions are separate from this editorial date.