86

Closed

SVN to TFS Migration Tool

description

There are plenty of development teams using SVN for version control that would like to transition to TFS. If you are a member of one of those teams, please vote for this issue. I'd like to create a CodePlex project for a SVN to TFS tool, and if there is enough interest I'll create it.
 
So... what needs to be included in the requirements for a SVN to TFS tool? Is 1 way migration enough, or is bi-directional syncing needed? How about labels? Branching? Anything else?
 
If you have thoughts on what a SVN to TFS tool should look like, please leave your comments or attach a doc.
 
-Matt
Closed Nov 11, 2009 at 7:32 PM by mmitrik
Closing this as there are multiple SVN to TFS solutions posted on the TFS Migration and Integration Solutions page: http://msdn.microsoft.com/en-us/teamsystem/bb840033.aspx

comments

jkingry wrote Aug 1, 2007 at 8:59 PM

Migration of branching is a must. Someway of indicating SVN "branches" that should be a TFS label would also be useful. E.g. branches with no additional revisionsAbility to handle multiple SVN repositories is a must - for us, a repository per team project makes sense, but other mappings might be useful.

IDisposable wrote Aug 10, 2007 at 5:33 PM

Labels and branches are a MUST. Bi-directional is not needed now that we can expose TFS to an SVN client.

minichmayr wrote Feb 28, 2008 at 8:16 AM

Bi-Directional Syncing would be great. It's easier to migrate from SVN to TFS if one knows, that it's not a one-way trip.

Branches should be included in migration. Labels could be included. Heuristic: SVN Branches that are located inside a "tags" folder and have no history entries since the branch-revision could be treated as labels.

legalize wrote Apr 5, 2009 at 5:56 PM

I really need this because I'm trying to migrate my project from sourceforge to codeplex. svnsync against the SVN url provided for codeplex projects doesn't work. svnadmin won't work with URLs. Please help! I asked about this over on the codeplex project for codeplex itself and got no responses.

curtisp wrote Apr 6, 2009 at 5:12 PM

There is a solution available from a thrd party developer. http://www.timelymigration.com/
There are also a couple of companies that provide custom solutions for migration. You can find them under the "Solution Provider" headding here http://msdn.microsoft.com/en-us/teamsystem/bb840033.aspx?ppud=4

Thanks
Curtis

djseng wrote Apr 23, 2009 at 2:09 PM

I've a unique situation. We're about to begin a collaborative effort with another vendor. They use SVN and they have the current source. We have TFS, I'd like to somehow sync our TFS source control with there SVN repository. What I'd like to do, is do our development in our local TFS server where we can associate Work Items with check ins and etc. Then we'd need the ability to send our changes back up to their SVN repository.