<p>There are about 200 projects in cvs and at least 100 projects in vss. Some are inactive code in maintenance mode. Some are legacy apps. Some are old apps no longer in use. About 10% are in active development. The plan is to move everything to perforce my end of year 2009.</p>

<p>Has anyone done a large migration like this? </p>

<p>Has anyone come across best practices for moving from cvs to perforce? Or a similar migration. Any gotchas to look out for?</p>

[{'answer_id': 79202, 'author': 'Kevin Little', 'author_id': 14028, 'author_profile': 'https://Stackoverflow.com/users/14028', 'pm_score': 0, 'selected': False, 'text': '<p>Forgive my answering a question with a question, but doesn\'t <a href="http://www.perforce.com/" rel="nofollow noreferrer">Perforce</a> provide tools for this? Or, at the very least, documentation? I\'d be beating up my Perforce salesperson...</p>\n'}, {'answer_id': 79219, 'author': 'Jonathan Arkell', 'author_id': 11052, 'author_profile': 'https://Stackoverflow.com/users/11052', 'pm_score': 2, 'selected': False, 'text': "<p>I haven't had to do something of this scale, but I have a few ideas.  First off, start by taking a small, unimportant project, and migrate that.  That will give you an idea of how much trouble it is going to take to migrate the rest of the projects.  Immediately after that you should choose a medium size project as there may be issues with migrating a larger project (say with branches) that might not be apparent on a small project.</p>\n\n<p>Make sure you spend a bit of time seeing how easy it is to convert cvs projects to vss, or the other way around.  If converting from vss to perforce is a real pain, you can convert vss to cvs, and then to perforce.  Don't sink days into it, but it could back you out of a sticky situation.  I think the key here is go incremental.</p>\n\n<p>Backups are good.  Period.</p>\n\n<p>Consider a cutoff date, and any projects that are inactive, and older then that, should be mothballed.  Check out the final revision and store that in Perforce.  Do you really need 15 yearold visual basic code?</p>\n"}, {'answer_id': 79495, 'author': 'Mark', 'author_id': 4405, 'author_profile': 'https://Stackoverflow.com/users/4405', 'pm_score': 4, 'selected': True, 'text': '<p>On the VSS side, there are conversion tools that are available to help with migration.  They can mostly maintain version history (there are caveats that are explained in the readme and docs).  I have migrated well over 50 VSS projcts into perforce using the VSS to perforce tool.   Getting the data out of VSS can be a bit finicky and not terribly speedy, but it works.  If you have direct access to the disks (i.e.  not over a network share) to the VSS repository, the conversion can go much quicker.   You can find information about the scripts <a href="http://kb.perforce.com/Conversions/VssToPerforce" rel="nofollow noreferrer">here</a>.</p>\n\n<p>There is a simlar page for CVS to perforce conversion <a href="http://kb.perforce.com/Conversions/CvsToPerforce" rel="nofollow noreferrer">here</a>, although I don\'t have direct experience with that.  These links are good places to start.  You can also search through the Perforce mailing lists at the Perforce Knowledge Base located <a href="http://kb.perforce.com/" rel="nofollow noreferrer">here</a>.  I\'m pretty sure that you might find some conversion information in the mailing list archives.</p>\n\n<p>Migrate your old projects first.  You can make sure that your process works.  When we migrated active code to Perforce, I took one weekend and basically took down access to the servers and moved the code over to Perforce.  Honestly, it was a pretty easy migration and when people came back on Monday they were ready to go.  You might think about preparing your employees with Perforce cheat sheets after you start doing the migration.</p>\n\n<p>The biggest gotchas might actually be preparing your people to use Perforce.  Had I done it over again, I would have migrated our smaller active projects first and prepared smaller numbers of people to use Perforce at once.  As it was, I had to train 120+ people on day 1 after the migration and that was a bit much.  Also, make sure that you don\'t have 100+ people hitting your server for a fresh sync on day 1 either.  We wound up taking our server down multiple times during the first few days.  We used a windows 32 bit server which I would not recommend.  We have a windows 64bit server now and it\'s much more robust.  If you can, I would actually use Linux as your OS for your perforce server.  Again, there should be good info on the Perforce site about performance.</p>\n'}, {'answer_id': 79790, 'author': 'Matthew Jaskula', 'author_id': 4356, 'author_profile': 'https://Stackoverflow.com/users/4356', 'pm_score': 0, 'selected': False, 'text': '<p>Consider not migrating dead and inactive projects. Simply put their repositories in read-only mode. The data will still be available if needed and you save the time effort of migrating them. Just migrate the 10% that are in use. Document the process thoroughly. </p>\n\n<p>If one of the un-migrated projects gets resurrected some time in the future you can easily migrate it using your documentation as a reference.</p>\n'}, {'answer_id': 79820, 'author': 'Kevin Sheffield', 'author_id': 590, 'author_profile': 'https://Stackoverflow.com/users/590', 'pm_score': 1, 'selected': False, 'text': '<p>What ever you do, keep the old repositories in read-only mode some where.</p>\n'}, {'answer_id': 80733, 'author': 'Douglas Leeder', 'author_id': 3978, 'author_profile': 'https://Stackoverflow.com/users/3978', 'pm_score': 0, 'selected': False, 'text': '<p>We migrated our svn repository with a tool that we wrote, and just took the head revision of our starteam projects.</p>\n\n<p>Watch out for differences between single-file checkins (CVS) and multi-file changesets (Perforce).</p>\n\n<p>Watch out for branches is separate space (CVS) vs. branches in filepath-space (Perforce).</p>\n'}]
['https://Stackoverflow.com/questions/78983', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/13753/']