Important

You are browsing upcoming documentation for version 7.1 of OroCommerce, scheduled for release in 2027. Read the documentation for the latest LTS version to get up-to-date information.

See our Release Process documentation for more information on the currently supported and upcoming releases.

Migrating from the Legacy OroLab Bundle

This bundle supersedes the legacy orolab/customer-part-number extension. Follow these steps to move existing data to the new entity. For command options, see CLI Commands.

Note

Migrations\Schema\OroCustomerPartNumberInstaller runs the first time this bundle’s schema is installed - on a brand-new application install, or when this bundle is newly added to an already-installed application and oro:platform:update is run. If the legacy orolab_customer_part_number table already exists at that point, the installer automatically enqueues the same migration query, so step 1 below is not required. Steps 1 through 6 are needed only if the legacy table did not exist yet when this bundle was installed or updated (e.g., the legacy extension is added later), or to re-run the migration manually.

Preview the migration with --dry-run, then run it for real:
```
php bin/console oro:customer-part-number:migrate-from-orolab --dry-run
php bin/console oro:customer-part-number:migrate-from-orolab
```
This copies the existing rows from the legacy orolab_customer_part_number table into the new oro_customer_part_number table. A row is skipped when it already exists there, when it has no customer, or when its part number is longer than the 255 characters the new column allows. The command summary counts the skipped rows by reason, and a row skipped because of a missing customer or a part number that is too long is also reported individually.
Run the website search reindex, so migrated customer part numbers appear in the storefront search:
```
php bin/console oro:website-search:reindex --scheduled
```
Verify the migrated customer part numbers in the storefront (search results, product view, listing pages, etc.).
Remove the legacy entity configuration:
```
php bin/console oro:customer-part-number:cleanup-orolab
```
The legacy orolab_customer_part_number table is intentionally kept and must be dropped manually if it is no longer needed.
Remove the old OroLab customer part number extension (the legacy package/bundle) from the application.
Clear the application cache:
```
php bin/console cache:clear
```