Migration from MSCP 1 to MSCP 2.0 #487
Description
Problem to solve
Will there be a migration for customized projects and values from MSCP 1 to MSCP 2.0. While changes and customizations will be documented an automated method to prevent missed controls and configs could save troubleshooting time during transition.
Intended users
Anyone using the project and migrating to 2.0 when released
Further details
Automation prevents issues, it looks like the project is architected in a way that this feels possible
Proposal
On first being pointed at a repository user can choose project to update
Documentation
Testing
Should be little risk as changes are documented and written to disk in the v1 project
What does success look like, and how can we measure that?
Success is a user migrates to 2.0 without spending any time transitioning and evaluating old content