Home/ Questions/Q 75691
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T20:33:21+00:00

I need to migrate a large project from StarTeam 5 to Subversion, and I’d

  • 0

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:

  • Manual or scripted export/import of each snapshot. Advantages: straightforward, easy to select labeled/dated versions. Disadvantages: time-consuming, does not preserve comments.
  • Polarion offers what seems to be the perfect tool in svnimporter, but it requires a .jar file from StarTeam 8.0 that is not present in StarTeam 5. Advantages: automated, complete. Disadvantages: requires upgrade to StarTeam 8.0 for one-time use.
  • Migrate via some intermediate repository (e.g. StarTeam -> CVS -> Subversion). I haven’t yet found any intermediary that will cooperate with StarTeam.
  • Migrate only the latest source. Advantages: simple, fast, encourages developers to invent new solutions rather than repeating history. Disadvantage: encourages developers to invent new solutions rather than repeating history. 🙂

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

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. 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.
    • 0