OpsHub Visual Studio Migration Utility

The OpsHub Visual Studio Migration Utility is now available in two versions, the free utility and commercial utility.

OpsHub Visual Studio Migration Utility Free Version helps customers wanting to migrate the most commonly requested data from an on-premises Team Foundation Server to their Visual Studio Team Services account or another on-premises Team Foundation Server. It enables basic migration of history of version control change sets, work items, test cases. Refer Functionalities Supported (Free utility) to know more details on what is available in this free utility. The Free utility offers very limited support through the community supported Q&A forum with no additional support included.

You can download the free OpsHub Visual Studio Migration Utility on Visual Studio Gallery here : http://aka.ms/OpsHubVSOMigrationUtility

OpsHub Visual Studio Migration Utility Commercial Version, in case you are looking for any of advance migration options OpsHub Visual Studio Migration Commercial Utility offers migration of test suite, Test Run and Test Result or traceability between WI and Change Sets etc. To know more details of functionalities supported refer Functionalities Supported (Commercial Utility). The commercial utility offers additional support by OpsHub throughout the data migration process.

Please contact This email address is being protected from spambots. You need JavaScript enabled to view it. for upgrading your utility to avail advance migration options available in Commercial utility

The utility supports the following versions of Team Foundation Server: 2010, 2012, 2013 and 2015.

The migration utility migrates historical information for work items, version control change-sets, test cases, test results, and all the relationships between them in incremental manner.

It keeps the data intact and provides a functionality for mapping users for source and destination systems with all validations.

If you are looking for some more advanced scenarios, OpsHub also has the full-fledged OpsHub Integration Manager commercially available. 

Supported Operating Systems:

  1. Windows Server 2008 R2
  2. Windows Server 2012
  3. Windows Server 2012 R2
  4. Windows 7
  5. Windows 8
  6. Windows 8.1

Hardware/Software Prerequisites:


  1. RAM – minimum 4 GB (recommended)
  2. Disk space - 5 GB Free Space (recommended). [Note: Larger disk space is required for changeset migration, size depending upon source code data which is being migrated]

.NET Framework

The OpsHub Visual Studio Migration Utility installation needs Microsoft .NET Framework 4. If the required .NET Framework or Object Model is not available, the installer will provide an error indicating the .NET framework is not found and will redirect you to the download page.

Brian Harry launched the OpsHub Visual Studio Migration Utility tool in his Keynote at the TechEd North America conference 2014. If you want to learn more about the TechEd announcements and to view his keynote visit, check out these videos.

Following are some screenshots of the experience of utility from beginning to end:

Advanced scenarios where the OpsHub Integration Manager is better suited include

  • Broad ALM integration support for more than 40 native and out of the box systems
  • Integrations and migrations between Team Foundation Server, Visual Studio Team Services, and many other ALM solutions including Atlassian Jira, IBM Rational, HP Quality Center, and many others. Checkout OpsHub Supported ALM systems for more insight
  • Two-way synchronizations and migrations
  • On-premise, Customer cloud and Hosted deployment options
  • A fully functional and user interactive Web based Administration
  • History prevention and conflict resolutions between the work-items during integration/migration process
  • Multiple replication models to support your development organization
  • Customized migration/integration business rules including the ability to support customized TFS process templates
  • Additional services to assist your team with your migration and integration needs


If you have any quesitons about OpsHub Visual Studio Migration Utility, please post them to StackOverflow (www.stackoverflow.com) with hashtags #opshub and #visual-studio-online. OpsHub team will be periodically reviewing the questions posted there and answering them as appropriate. 

Other Documents for Help

For additional help and a walkthrough for setting up your Visual Studio Team Services account with the appropriate prerequisites for using this migration utility, you can visit our Walkthrough Page.

For any further help or assistance in downloading, installing or configuring the utility, log a ticket to our OpsHub-Visual Studio Customer Support and we will get back to you within 24 working hours.



S5 Register


Fields marked with an asterisk (*) are required.

  1. Key Features
  2. Functionalities Supported (Free Utility)
  3. Functionalities Supported (Commercial Utility)
  4. Limitations
  5. Free v/s Commercial Utility

  • Easy to use and helps user make intelligent need based decision
  • One-way migration from on-premises Team Foundation Server to Visual Studio Team Services
  • Change history is preserved during migration with original details included in work item revision history and version control changeset comments
  • Entities supported include :
    • Version Control
    • Work Item Tracking
    • Test Cases
    • Test Results
  • Mapping between on-premises Active Directory accounts & Workgroup user accounts in Team Foundation Server with Microsoft Accounts (formerly known as Windows Live IDs) used in Visual Studio Team Services

  • Migration of files
  • Migration of folders
  • Preserving changeset contents
  • Support for following change type: add, edit, rename, delete, branch, merge, and type
  • Automatic Conflict Resolution for conflicting merge changes
  • Migration of files and folder having maximum item length supported by Team Foundation Server with hierarchy
  • Migration of all types of workitems with revisions
  • Migration of all fields of each workitem
  • Migration of all in-use areas and iterations associated with the workitems
  • Storyboard migration support
  • External link support
  • Migration of all types of attachment supported by TFS
  • One to one user mapping

  • Migration to the on-premises Team Foundation Server end-point allowed
  • Migration of test entities (test suite, run and result)
  • Migration of labels in version control
  • Migration of multiple projects data in single migration configuration
  • Migration of traceability between Workitems and changesets
  • Migration with actual source end point's history user to target (partial user impersonation)
  • Migration with source and target end point having common set of process templates customization
  • Re-running same migration configuration multiple times

  • General Known Limitations
    • The user used to create VSTS End Point should not be used to make any change/check-ins in VSTS while the migration is running. It is hence, suggested to create a separate user to connect to the end point and run the migration
    • Mapping of user with same User Display Name under two different domain is not supported by the tool
    • Due to the model/limitation of TFS itself, the Work item ID’s and changeset ID’s of the migrated content in Visual Studio Team Services will not match the Work item ID's and changeset ID's of the same content in on premise TFS. Metadata information about the source changeset like original username, original check-in timestamp are embedded in changeset comments during migration for changesets
    • Note: Your source TFS usage is not required to be frozen or put on-hold for the migration. The migration utility can run perfectly fine in the background, and so your team can continue using TFS while the migration is running
    • 32-bit version of the windows operating system is not supported
  • ALM Known Limitations
    • Pure Impersonation is not supported; partial impersonation which shows impersonated user as well as authenticated user is supported. This shows impersonated user in history with via as authenticated user
      • E.g. Following text highlights how it will show in the migrated Work Item history if “User One” created a bug in the source TFS whereas credentials of user “Migration User” were given to authenticate with Visual Studio Team Services in the utility
      • “User One (via ‘Migration User’) created Bug”
    • For some cases, impersonation will not work for link. Rather than showing impersonated user, it will show authenticated user for links operations in history
    • Following fields value will not be migrated and will be set default by VSTS as per current system time:
      • User fields: Created By, Closed By, Activated By, Resolved By
      • Date fields: Closed Date, Activated Date, State Change Date, Accepted Date, Resolved Date, Called Date, Revised Date, Created Date
    • Creation of Project WorkItem type and fields for any WorkItem is not supported. They has to be created prior in the Visual Studio Team Services instance
    • Adding WorkItem to the specified categories in TFS is not supported
    • Creation of Builds, Users, test configurations, test settings and test environments are not supported
    • Attachment Date Attached migration is not supported
    • Inactive users cannot be mapped in utility
    • Project name on both the ends should match. The utility does not allow mapping project with different names on source and targeting end
  • Version Control Known Limitations
    • If Branch/Move across project has been done in your on-premises TFS and only some of those projects are selected for migration. Then the utility will convert Branch/Rename (Move) -> to -> Add change type
    • Branching of a folder as a new project is not supported by the utility. Since in the VSTS the $/ProjectName folder already exists
    • Migration of data in a project where tf destroy was performed with /keephistory parameter is not supported in the utility, since the data in question is no longer present in TFS
    • Labels created at Collection Level scope will not be migrated
    • Migration of check-in notes, check-in policies is not supported
    • The check-in Date of a changeset(s) will not be retained in VSTS. Instead the current time value will be set by default

Scroll Up