Are there any import and export tools that would let us move projects into and out of team system with full history and log? Our current SCM is SVN.
PS – Sorry, I know it’s a repost, but I didn’t get an answer before… 🙂
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Unfortunately, you probably didn’t get an answer because there isn’t a good one on offer…
I’ve looked into this a couple of times before, initially for the first TFS Betas. (At the time we were eager to move away from VSS while waiting for TFS to be ready… the compromise we ended up with then was to use SVN in the interim, but used a post commit hook that kept a VSS repository in sync to allow for that migration path to TFS.)
These guys (ComponentSource) were around back then with a VSS to TFS converter, and added a SVN to TFS one, but appear to have since discontinued the product.
These guys (Kyrosoft) might have some promise, but I’m concerned that they don’t post prices, and do post a customer list (of two). If anyone has experience with the product, please let us all know.
More recently the TFS Migration and Synchronization Toolkit has been released on CodePlex, but to date no one has release a SVN plugin for it (there are 66 votes for the request)
So, you can look at rolling your own plugin for the toolkit, but even then you won’t get the original dates for commits, as to my knowledge the TFS team haven’t allowed a mechanism for importers to set this, so all migrated revisions will have the date of migration.
(The discontinued first tool above purportedly used to allow this, but how they got around the limitation (secret API? adjusting system time? database manipulation?) I don’t know.)
In the end, I suspect most teams end up deciding to just switch systems at an appropriate time (eg new version or project), and manually deal with the bifurcated history lookup for the 6-12 months it remains particularly problematic…