How To Migrate TFS to Jira

Visual Studio Team Foundation Server (TFS) is the go-to choice for many companies when they need a robust source code, project, and DevOps management system and collaboration tool that covers the entire application lifecycle. Visual Studio usually comes either as a on-premise (TFS), or cloud solution (VSTS). Both compliment each other, but are widely used separately. One of the more common use cases we’ve seen is migration from TFS to Jira. This could be a quite daunting task, not to mention time consuming, but fortunately we have the right solution that will save you time and money.

Why Team Foundation Server

Team Foundation Server is definitely not easy to grasp, but quite powerful when mastered. It offers integrated, collaborative Git-friendly environment, continuous integration, and various planning and tracking tools. It’s back-end is flexible, allowing for wider range of development procedures, testing and reporting.

We’ve seen a rising number of clients who are heavily invested in TFS, but some wish to adopt Jira as a cloud-backed bug and issue system to save on cost and access new functionalities.

Some customers are running Jira in parallel with their existing system with real-time data synchronisation between the two systems to de-risk the migration process. In this way, the new Jira instance can be shown to support all requirements with the old system still available should problems be encountered.

Challenges When Migrating from Team Foundation Server to Jira

Migrating to Jira is still not an easy task, often involving third-party apps and even some additional coding. As we found out there are Jira migration plug-ins available to move data into Jira from other systems, but the range of systems supported is limited and migration flexibility is limited.

Yes, you can export data via CSV in conjunction with third-party applications as evident from the Atlassian Community forum, however in many cases such migration will impose heavy limitations, and in some cases will require additional coding, or even an in-house solution. Not to mention that it’s time-consuming and CSV imports does not support the migration of attachments, or mapping additional fields beyond the basic ones.

Although people find great ways to go about migrating TSF to Jira, there are still no clear procedure available for keeping records within TFS system and Jira synchronised.

Implications of Migrating from TFS to Jira

We already highlighted some of the more common problems when migrating from Team Foundation Server to Jira - lack of built-in solution, not so flexible third-party tools, need of additional scripting when mapping the data, time-consuming and cumbersome.

The lack of adequate solutions often drives companies to make a major investment in programming/scripting to build a solution. Above all this extends the timeframe of a project, and increases its cost. That often leads to the development being outsourced to an Atlassian service partner, which again reflects on the overall cost.


The need defines the means. A lot of companies are constantly looking for productised solution from an Atlassian partner that delivers up to 100% of the required migration solution. The demand is for a visual-responsive programming tool that rapidly reflects any custom actions into a ready-made solution.

Customers frequently ask us if we can provide a completely automated way of keeping records permanently synchronized between TFS or other systems and Jira instances. Cloudpipes does more than just that. We offer a cloud-based solution to any similar such cases with nil requirements for infrastructure, which can easily and securely reach back into any data centre where the TFS is deployed on-premise.

How Cloudpipes Achieves Migration to Jira

Cloudpipes provides a fully optimized solution for Jira migration which can be tailored according to individual needs, or as a ready-made deployable solutions on the go.

Our TFS to Jira integration lets you create, monitor, and update user stories, make comments, and send attachments among other things. Cloudpipes’ powerful import/export capabilities allows for a seamless data migration that allows the mapping of dependent resources like users, components, versions, labels etc. on the destination Jira.

The built-in visual drag and drop editor helps you easily build a migration workflow in the form of sets of pipelines. Our customers can also select the scale of the migration - individual projects or a subset of tickets can be selected as target for migration. Migrations are achieved through our on-premise agent that enables migrations to operate on any combination of cloud and/or on-premise Jira Server instances.

Cloudpipes also has a powerful templating functionality called Blueprints. Blueprints provide an effortless way of setting up a pre-made workflow schema constructed as suite of pipelines that delivers a working provision off-the-shelf.

We know that it’s not easy migrating large databases. Fortunately, our Jira integration presents a reliable and stable solution that can be deployed in more than one way.

Looking to migrate TFS to Jira? Let us help. Get in touch with us now!