svnversion-controlmigrationstarteam

Strategy to migrate from StarTeam 5 to Subversion?


I need to migrate a large project from StarTeam 5 to Subversion, and I'd like to keep snapshots of (at least) 5-10 of the major releases. I've considered the following:

I'd appreciate any experiences or suggestions you might offer. Thank you.


Solution

  • Having not used StarTeam I cannot speak to that -- but I think you've laid out some nice options.

    1. Scripted import seems like it could be time consuming, not really get you everything, but at the same time, be a reliable way to get into svn and still preserve your release history.
    2. What is the real downside of upgrading and throwing away the install after? Do you have to re-purchase the software? Is it a tedious upgrade? Barring that, it sounds like this may just be the best option.
    3. I would really stay away from this option. cvs -> svn import is pretty shaky (really, it's a one-off thing, probably not that many individual people work on it enough to really care about making it perfect). Going from another SCM system to cvs, and THEN to svn sounds like a recipe for useless history data and frustration. :) I've only done it a couple of times, and really, the best part is once you're done, you're in svn and never touch cvs again.
    4. This option does really suck. You lose all your history.. can no longer blame other dev's for screwing things up.. On the upside though, it will absolutely work, if all else fails.