This migration utility helps customers to migrate the most commonly requested data from an on-premises Team Foundation Server to their Visual Studio Online account. It is designed for basic migration scenarios to migrate history of version control changesets, work items etc.
This is downloading version 1.3 but the description says 2.0. I have just tried installing the 1.3 version and it tells you once installed to install the new version in a registration email. I have been struggling for a week with the old version with errors and then just generally too slow. Fingers crossed this is a big upgrade with V2. UPDATE***Started using this and they have removed the ability to select more than 1 team project to migrate at a time. Lowered rating in response.
Smaller project code and history seems to work, eventually. I've had no success with work items regardless of Agile or Scrum workflow. There seems to be no way to import any custom templates.
As the existing TFS 2010 server is creaking at the seams, I had to run from a separate machine which didn't help the performance issue. I'm about to try on a dedicated more powerful box, importing one project at a time but I'm starting to think copying only the code with no history manually and loosing the workflow is going to be our only option. How Ms can release an upgraded TFS with no fully supported method of migrating existing data is beyond me. What's next? New Office which cant read any previous word or excel docs?
Not receiving any verification code via email. Checked inbox and spam. Also don't know how to re-run the application. Can't find it in start menu. If I try to re-install it just disappears after the standard permission elevation warning. Think I'll stick with on premises.
Seems pretty poor - can't even install since it asks for a verification code that will be emailed to the address you enter but no email ever arrives (I've checked all spam folders etc...). Need to implement a better method of providing verification as this is basic stuff.
We have done some testing with the tool, and while it seems that it generally works, we have some showstopper issues.
1) For some reason, it is extremely slow - OpsHub is looking into the issue, but we currently estimate a 9-day migration time for 5 Team Projects with a decent amount of changesets and work items. 2) More of an issue, though, is that the dates of Work Item Closed Dates, etc. as well as the Changeset dates are not migrated. This means that we cannot run realistic reports after migration or effectively track code changes.
I realize that issue #2 is not really in the hands of DevOps, but it would be nice to see a fully supported migration path from Microsoft where all available data is migrated. Otherwise, at least in our case, we cannot get started with VSO. There will simply be too large of an overhead after migration to do this.
Ryan, On #1, The migration speed is dependent on number of revisions, connectivity speed, the speed of end point and size of changesets and attachments (as they need to be transferred over the network to VSO).
On #2, The current VSO (and TFS) API doesn't allow us to set those attributes on a write. Hence the limitation.
Works well if you have a vanilla install of TFS and a brand new VSO instance with admin rights for both.
If you need any advanced customizations beyond that (e.g., being able to cloak incoming folders, re-base your import under a sub-folder, select only a subset of changesets to import, etc) I don't think you will be able to. It only includes the most basic settings: an instance of TFS to import from, an instance of VSO to export to.
It also has the tendency to fail easily. I had a very old TFS instance that had been upgraded from 2008 to 2010 and then again 2012. I'm not sure if it failed due to some corruption in TFS (it worked fine for us through VS), or if it was due to some historic branching issues. It also seems to need a lot of permissions.
Overall, it's the best product available, and you can't beat the price (free), but it can be problematic and require a little tweaking to get just right.
The utility is not designed to migrate from customized templates on TFS side. If you have customized templates on TFS side, the utility will give an error. If you are getting any other error please post it in Q&A section and we will help you in resolving it.
Worked very smoothly and completely migrated ~15 realtively simple projects and ~1,300 changesets. After configuring online security and mapping logins, the process couldn't have been much smoother. The only issue I've noticed so far is that check in timestamps for revisions will be set to the time of migration check-in; however, the comments have the original check-in user and original timestamp. Overall, this is an excellent utility - highly recommended for moving collections from TFS to Visual Studio Online!
I see this error while migrating one of our on premise projects on TFS to VSO. Able to migrate most of my projects but got stuck at this one. Can you please help ?
OH-SCM-009: Error occurred while sync. TF14009: Cannot merge source '$/***********/***********/***********' into target '$/***********/***********/***********/Branch/******' because the target is underneath source.
Was your TFS Server upgraded from 2008 to newer version? The error code indicates a scenario which was only possible in older versions of TFS. Pending a new branch and remaining the source branch in the same changeset is no longer possible in TFS.
During the validation step and after successful login, I keep getting a timeout. Full details at the StackOverflow link below.
Am currently evaluating options for the destination of an existing TFS 2010 Project Collection - which has to be moved across domains.
Our customer intends for us to use VSO - but am wondering if OpsHub supports migrating in from a TFS Project Collection backup at all?
We are not sure we understand your query. Could you elaborate some more, do you mean to migrate from a TFS 2010 Project Collection backup that exists only at the database layer and no application layer is present? Or you mean a Project Collection that was moved across TFS instances that existed over different domains. In this case, the user mapping might create trouble, but only if the current instance users and the backup collection users are different.
I am in the process of trying to migrate from an installed TFS 2012 collection to Visual Studio Online. I have progressed through the migration utility and chosen the relevant options, but when it comes to the Migration Summary screen and tries to verify everything, I get the following error:
"The account you have logged in to run the migration utility does not have the correct level of administrative privileges in order for us to provide the best possible migration experience
We need for this account to temporarily have additional permissions by adding it to the Project Collection Service Accounts security group."
I have read through the instructions to do so in the "Learn More" link (http://www.opshub.com/ohrel/Resources/TFS/permissions.php?page=serviceaccount), but the problem is the Visual Studio Online layout has either changed since this article was written, or the options just aren't there for me. Clicking the "Security" tab for the project collection, I don't see the "Users" button. I just get a list of VSO groups. The project collection service account group is in there, but the "Add" button is greyed out so I can't add my user into it.
Visual Studio Online has recently changed this to disallow users directly changing members of Service Account. There is however, a workaround that you can use.
1. Create a new (custom) VSO Group
2. Under 'Members', add your user.
3. Under 'Member of', add [DefaultCollection]Project Collection Service Accounts
4. Go back to OVSMU and re-validate the migration that you were creating.
I’m trying to migrate from TFS 2010 to Visual Studio online.
I have followed the steps highlighted at https://www.visualstudio.com/en-us/get-started/setup/migrate-team-projects-vs.
At the ‘Select Team Project(s)’ screen I get the error “Object reference not set to an instance of an object.”
I have emailed my logs to firstname.lastname@example.org. Do you have any recommendations?
So, I didn't read that OpsHub only supports TFS 2010 and newer and unfortunately I have 2008. I backed up the database and on a temporary server installed 2010 and imported my 2008 collection. Once in TFS 2010, it worked quite well. I could not, however, migrate the work items. I could only migrate version history and labels.
FYI -- OpsHub support responded to this email and message within 12 hours.
All work OK thanks, but changesets numbers on VSO not same as it in our On-premises TFS.
when we open the collection from the VSO it shows changesets 239... instead the
of 1598.., what we doing wrong?
Is the migration one-way and final? I'd like to do a test-migration, but don't want to trash our on-premise TFS instance.
I remember during some of the TFS upgrades, it would move/rename/combine some of the databases in-place. I'd hate to try a migration and mess up our instance.
Sometimes the email is caught in SPAM filters at various levels. We have seen this occur occasionally.
So if you don't receive the verification email, please send and email requesting the verification code to ovsmu at opshub dot com
I wanted to migrate project from TFS 2010 with default, not customized, Scrum v1.0 process template but the tool complains about "Template Customization or Template Mismatch error".
In previous Q&As I noticed there was some plan to support Scrum v1.0 and was scheduled on February's release. As of September 2015 it is still not available. Can you please update us on its status?
When the migration utility tries to pull up the list of available projects, I get the error below. Things I have confirmed:
1) Running the latest ( I think ) version of the utility - V1.3.000B000
2) Migrating from TFS2010
3) My VSO user IS in the "[DefaultCollection]\Project Collection Service Accounts" group
4) I have created a project in VSO with the exact same name as the one I am migrating
5) When managing endpoints, the "Team Project Collections" display for both servers, indicating that it does appear to be connecting/authenticating correctly
6) Tried deleting VSO project to switch from Scrum ( desired type ) to Agile, since source project is "MSF for Agile Software Development - v4.2"
Thank you in advance for your help.
2015-07-22 23:14:36,677  ERROR Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
at TFSMigrationUI.ViewModel.ProjectSelectionViewModel.loadProjectWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e) in e:\OVSMUBranch\TFSMigrationUI\ViewModel\ProjectSelectionViewModel.cs:line 324
at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)