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!
We wanted to migrate a small team project, although the tool already fails on setting um a new migration. During the "Select Team Project(s)" step we get the error (in German) "Der angeforderte Wert "CreatePending" konnte nicht gefunden werden.".
On February 1st, 2016, download link refers to:
I love the tool and use it often, but latest download seems to be broken.
We are able to download from the download button on vs gallery page. We have had issue with VS Gallery download with certain versions of browsers (where download fails to trigger). If possible, can you please try with another browser. If not, can you please provide browser version details.
My Dev Team is attempting to migrate a TFS 2013 Project to Visual Studio Online.We start the utility, go through set up steps, map users, and then start the migration, and it looks like it just hangs with no updates (visually atleast) once the migration begins. We let it run over night, yet no change. Is this by design, any help would be appreciated.
Also looking at the logs we get this common error, which points to a security context being lost or something in that manner, but we were able to setup the entire migration, so connection with the tfs server with the creds was successful:
Failed to login to Team Foundation Server : 'Server Url' with user : null. Server Error : ; nested exception is:
java.net.ConnectException: Connection refused: connect. You may have given wrong credentials or credentials are not valid now.
Hi Thunomi, Im facing the same issue, so now I´m totally stuck in the middle of a migration.
Did you find the solution to this? Remember any clue?
I really appreciate if you share it.
Thanks in advance
Sometimes if the IE cache is reset the cached authenticated information is lost. The service runs in the BG, thus the pop-up for re-authentication will not appear. Can you try clearing the tfs cache?
- Stop the migration and close the migration utility (and Visual Studio related applications)
- Go to location(s) and delete the content of the Cache folder
- Restart the OVSMU tool. Select both end points by configuring a New Migration, the tool will ask you to re-authenticate. Do it.
- Now don't continue with that new migration, cancel it. Go back to your existing migration and Start it.
- Verify OpsHub.log and OpsHubTFSService.log for successful progress.
Very poor support. Can't believe this is the proposed Microsoft solution. Tried 3 separate email addresses to receive verification code, checked all spam folders. Support inbox is not monitored and answers don't appear to be given on StackOverflow.
We hope the support provided during the meeting was satisfactory. The older versions of the tool are deprecated.
Please do update us when you retry with the original proxy configuration.
We look forward for your feedback on the tool once you migrate your projects.
I'm trying to migrate from a TFS 2010 to VSO. Got 6 out 7 projects migrated. the last one, and the biggest one, gives me this error message during the version control migration -> OH-SCM-009: Error occurred while sync. There is no working folder mapping for $/<folder's name>. The folder in question has been created in VSO and all the users have been mapped. When looking at the log file, I do get There is no working folder mapping for $/<folder's name> in the java exception messages. I'm running V1.3.1.000. Please help?
This issue duplicate of a stack overflow logged issue. Please track the Stack Overflow issue at http://stackoverflow.com/questions/34157542/opshub-oh-scm-009-error-occurred-while-sync-there-is-no-working-folder-mapping
I've been running a migration for a few months. When the migration times out, I can resume it without any issues. However this time, I received a credentials error which prevents me from resuming. Is there a way for me to renter the login my TFS credentials so that I can resume the migration?
Error in initiating adapter for System : Team Foundation Server ALM due to OH-ConnLoader-0003: Connector for system name : my_migration_name could not be instantiated due to OH-TFS-Connector-0048: Failed to login to Team Foundation Server : http://my_tfs_server/tfs/ with user : null. Server Error : TF400324: Team Foundation services are not available from server my_tfs_server.
Technical information (for administrator):
Unable to connect to the remote server. You may have given wrong credentials or credentials are not valid now.
Click on new migration and select end point which will ask for username and password again.
OpsHub is using windows stored credential. If this will not resolved issue then please send us full log to firstname.lastname@example.org
I have TFS 2015 Express on a Win 10 (64-bit) PC. I would like to migrate the projects to VSO and wondered if this tool could help me.
However it won't install at all. It says "this app can't be installed on your PC". I've tried in compatibility mode and with administrator privileges, but it won't install. I don't see any requirement for it to be a server operating system, but does anyone know if it will only work on a server? I have the recent version from November so I thought it might work on Win 10 but not sure if that's a problem. Anyone have any ideas why this is not compatible with my system?
Can you confirm what is the .NET Framework version and the TFS Object Model version installed on your machine?
Was Windows 10 freshly installed on your machine or did you upgrade from an older version?
Also can you verify in the 'Event Viewer' what is the cause of the error when the installer fails?
I have the same problem as Rosie, and Im stuck. Please help!
Cannot install this utility in a Win 10 (64-bit) PC ?
When Executing OVSMU-V2.0.0.003.exe...
"This app can't run on your PC"
To find a version for your PC, check with the software publisher
- Tried compatibility mode With Win7 and Win8
- Tried to open it as administrator
Please Help! Any workaround? Thanks in advance
By the way (again) the version shown above in Visual Studio Gallery ( OVSMU-V1.3.1.000.exe ) runs OK in my Win 10.
But not sure if I can make my migration from TFS2010 to Vs Team Services successfully with that version. V1.3.1.000
Let us know. Thanks
UPDATE - Happy to say that I noticed the size of downloaded .Exe (V2.0.0.003 195Mb) was far away of V1.3.1.000 234Mb.
So I have downloaded V2 again and now it works ( and the file is 304Mb that makes sense )
So, I have no idea what could happened with the download. Now, it is time to continue. Thank you anyway.
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.
This is a special situation which only occurs if the current system has been upgraded from TFS 2008 Update 1 version (Directly or Indirectly). That version allowed some operations which are no longer allowed in current versions of VSTS/TFS. If those operations were used in tha old version then migration fails. Currently there is not simple work around for this.
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.