Subversion Migration & Roll-out Package
Moving source code between two different version control systems is like moving houses. Most of the furniture may fit pretty well in the new house, but in some cases it is necessary to adjust or drop some of the pieces. Technically it is possible to migrate all important information like versions, labels, etc. to Subversion. However, it is key for you to understand whether your current use cases, workflows, and processes can be reflected in Subversion as well.
Our many years experience in migrating various version control systems to Subversion have taught us one thing for sure: a migration of your version control system to Subversion is nothing you want to do in a quick and dirty way. Spend some time at the beginning of the migration project to establish a sound migration plan to quickly guarantee the efficiencies and cost savings of Subversion.
At the end of the migration and roll-out package you will know exactly whether and how your existing version control system can be migrated to Subversion. You will understand what concepts and work procedures can be mapped to Subversion, and you will know what adjustments may be necessary to support your desired way of working.
The migration and roll-out package consists of following phases.
- Inception (Kick-off and definition of deliverables) – 3 days
- Test migration (technical test migration, gap analysis) – 2 days
- Migration concept and plan (documentation of migration concept and plan, presentation of results) – 2 days
To get a fully detailed agenda please contact our Professional Services team.
|Max. 5 attendees|