We’re migrating customizations into E10 vanilla as part of our upgrade process via the Solution Manager. I’ve done some proof of concept testing to verify I know how to migrate BAQs and Dashboards as well as delete them. We’ve reviewed the ERP Analyzer spreadsheet specifically for dashboards. Our plan is for every dashboard we want to keep migrate the corresponding BAQs, and for any that didn’t uplift fix and test before migration. Once Dashboards and corresponding BAQs are migrated we’ll start working through bpms, etc until we work our way through all customizations in the ERP Analyzer spreadsheet. We’re thinking of saving the CAB files on a network drive with a date as part of the filename so if we need to update anything we can create a new CAB file with an updated date and archive the old CAB file. Never having done this before I’m not sure if there are benefits to putting all BAQs in a CAB file and Dashboards in another or if having a single “master” CAB file is easiest. Are there any recommendations / strategies for migrating customizations? Does our plan sound reasonable.
After the customizations are migrated we’ll start bringing in end users for testing / training in E10 looking for issues for the next month or so until we feel confident we’re ready for the 2nd DB conversion. We’d love to hear any feedback.