we are migrating from TFS 2010 to Visual Studio Online. Our biggest Team Proyect has 14k ChangeSets. We are trying to migrate but based on the current "speed" it would take about 18 days to migrate.
I now there is a similar thread but:
Slow TFS migration from on-premise to TFS online with OpsHub tool
but it does not provide a solution. So I'm asking for help.
For TFS 2010 we have one Application Tier Server, a Database Tier Server.
Both Servers are performing ok (Memory, CPU,Network) during the migration
We are launching the migration Utility from a differect computer which also has ok performace (Memory, CPU, Network)
But in 12 hours, only 400 changesets has been migrated.
We are using version 1.0.1.008
Thanks in advance
Update from OpsHub.
We have done major performance improvements in the current release. It would be available to public by the end of this week.
Thank you Christian for your assistance in this case.
A rule of thumb is that it will take as long to migrate your history as it took to make it in the first place and those times are not outside the bounds of reality. I would ditch the history and move just the tip.
Clarification: No that is not slow that's just how long it takes to do migrations.
If you have a lot of modifications to code and or work items then it will take a very long time. You can make things faster by throwing processor at your source server and sticking a fat pipe in the way, but you are network bound.
You could spin up an Azure server in the same data center as your target VSO and install and configure your TFS 2010 environment there. Then run the migration. That will be much faster, and will still take a long time.