Of course if you need any help feel free to update your question or to contact me directly. We have discussed providing some specific migration tools from other systems and it would be very interesting to know how you get on with this. If you can advise how many Subversion users you have now and how your authentication is currently handled I can provide a bit more info on the best way to do this. Subversion supports a number of different protocols which suit a variety of needs: HTTP and HTTPS are best suited to access repositories available via public networks such as the Internet, while the custom SVN protocol is generally. The format of this communication is termed the protocol. The one area that might take further thought is how you handle user account creation and authentication in uberSVN. Subversion clients (such as Cornerstone) generally access a repository by communicating with a server. When you are happy it works you can gracefully migrate from one to the other with very minimal downtime for users. Right-click Repositories and create a new repository. Let’s assume username: user1 and password: user1pass 2. Using VisualSVN Server Manager, create a new user. That way we don't interfere with your existing VisualSVN installation and you can easily test the migration without risking breaking anything in your existing setup. Synchronizing Two Repositories This can be done in following steps: 1. The way uberSVN is designed, when you add repositories and choose the 'Import Existing Repository' option, the repository will be copied from the current repository location into the storage location you choose for uberSVN at installation time. You're not the first to ask this question though so I might be wrong about that!
Obviously uberSVN is still a very new product so I imagine experiences might be difficult to come by.