Migrating from MS SourceSafe to SubVersion

I am considering migrating our team's codebase from our existing system, Microsoft's SourceSafe, to Subversion. I understand enough to be able to migrate by making everyone check in what they're working on and then simply import this into Subversion and tell people to switch to SV. But I'd like to do better. First of all, if there's any way to import this history of the files into SV, that would be very nice... I would rather not lose the entire history of all files if I don't have to. (Would something like vss2cvs --> cvs2sv actually work?)

Secondly, it may be difficult to convince some people (not in our group) to switch over. If there were any way to keep BOTH systems active and somehow mirror changes made in each to the other system, then that would be, in my mind, ideal. But that may be difficult or impossible to achieve. I'd even be happy with "one-way" updates, where updates to SV automatically trigger a checkin of that same change to SS -- it's better than nothing.

Anyone have answers for me or suggestions of where to find resources? If anyone has done this before, I might even be able to arrange to pay a reasonable amount for consulting services.

-- Michael Chermside

This email may contain confidential or privileged information. If you believe you have received the message in error, please notify the sender and delete the message without copying or disclosing it.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 17 16:30:12 2004