First of all, you should really ask yourself the question whether you really need to migrate the history. It's nice to have, but it's often also a pretty big effort.
I have tried vss2svn in the past (2-3 years ago). At that time, the conversion failed miserably, but we were trying to convert a +12G VSS repository... We just left the existing VSS repository available for consultation, and imported the latest version of all projects into svn. The tool we used at that time was the one you find at pumacode (http:// www.pumacode.org/projects/vss2svn). There seems to be another tool available on codeplex these days (http://www.codeplex.com/VSS2SVN), don't know how whether it's any better than the original one. greetz, jeroen On 9 feb, 17:52, stoeltin...@gmail.com wrote: > Up till now we have been using Visual SourceSafe, but are looking into > other SCM solutions. Does Subversion have the ability to import > Visual SourceSafe database files? > > Thanks
