A DNS switch will be implemented, redirecting traffic from your Classic Primo front-ends to your Primo VE views. From this point on, deeplinks, permalinks, and short permalinks will be transformed into Primo VE compatible URLs. This action is seamless and doesn't involve any downtime.
Users' eShelf favorites will be copied from Classic Primo to VE.
Saved searches and queries are not migrated
Primo APIs will be routed to point at Primo VE instead of PBO.
Primo Analytics data will be migrated over to Primo VE Analytics, accessible via Alma.
Primo VE will be enabled on Alma sandboxes.
Support Chat for VE will be enabled on your Alma production.
If any of the campuses are subscribed to Leganto and/or CampusM, you will adjust them to integrate with VE instead of Classic Primo.
After Migration
Test the redirection
Test authentication and verify that E-shelf saved records are available
Test Primo VE Analytics and verify that Primo Analytics data is available