<p>I'm currently maintaining a CVS repository for source control.  There is a push afoot to move to StarTeam.  It has already been purchased and is a corporate standard for most projects.  I was told by the corporate owners of the StarTeam servers that there is no known way to do a complete migration of our current CVS repository to StarTeam.  We have been advised to do a checkout of the latest version and import that into StarTeam.</p>

<p>I would really prefer to keep all of my version history and not have to choose between simply losing all of the data or maintaining my CVS repository indefinitely.</p>

<p>Has anybody had any luck doing this?  Any recommended tools or processes?  Or am I just wasting my time and I should just migrate and cut my losses?</p>

<p>UPDATE: The official response from Borland is that this is definitely doable, but not with the boxed software.  I can purchase services from Borland to help me accomplish this.</p>

I wonder why a "professional" tool does not provide any means to import from well known legacy systems...
Although it may sound queer at first, i would recommend converting the cvs repos to subversion ( using e.g.
cvs2svn
, offered by tigris.org ), and then creating your own script to update from the subversion repos and commit into the starteam repository, provided it does offer an api or an command line client.
The advantage is that subversion supports nicely things like omitting branches or directories, and offer access via an api, which cvs does not.
Also, the documentation on subversion is quite extensive. (
example
on using the subversion api from python
Good luck!