I have a simple question I am migrating tfs 2013 update 4 to vsts and I am using a microsoft's migration tool but I have come across an error which stats it cant fetch my collections installation path (error tf255003), I read somewhere that the migration tool which was provided by microsoft is only supported for migration tfs2017 or tfs2017 update 1 to vsts. So can I not migrate a tfs 2013 directly to vsts, or first I have to upgrade the TFS2013 TO TFS2017 UPDATE1 then do the migration please elaborate.
We recommend you upgrade to TFS 2017 update1 first, then following the Migration Guide step by step to do the migration.
For upgrading TFS 2013 to TFS 2017 update1, you can reference below articles:
Upgrading from TFS 2013 to TFS 2017
Upgrade to Team Foundation Server (TFS) 2017.
However, if you want to migrate from TFS 2013 directly, you can get and upload the source code manually, and use Execl to export and import the work items.
You can also have a try for VSTS Sync Migration Tools,it allows you to bulk edit and migrate data between Team Projects on both Microsoft Team Foundation Server (TFS) and Visual Studio Team Services (VSTS).
Besides, you can also use OpsHub Visual Studio Migration Utility, the Commercial Edition supports migration from either TFS or VSTS to either TFS or VSTS.
Related
I want to migrate TFS data from TFS 2010 (SP 1) that uses SQL Server 2008 R2 to TFS 2017 that uses SQL Server 2016. Is there any way to migrate data from TFS 2010 to TFS 2017?
You cannot upgrade directly from TFS 2010 to TFS 2017, but need to go through TFS 2013 Update 5 (see below).
You can read more here.
I would recommend setting up a new server with SQL Server 2014, where you can migrate your databases using SQL backup. Then first install TFS 2013.5 followed by TFS 2017.2 and finally updating SQL Server to 2016 (See TFS support for SQL Server). I suggest doing a trial migration first to validate that things work and to know how long production downtime is needed for the actual migration.
How to publish a project developed in VS 2015 for the TFS 2017 server itself?
If you mean to create a Team Foundation Server plugin, you can reference this article : How to create and debug a Team Foundation Server server-side plugin, it's similar for TFS 2017.
And this video tutorial : Create TFS Plugin
For write TFS extension, please see this article:
Write your first extension for Visual Studio Team Services
I want to move the whole team project data(source files and work items…) from TFS 2008 to TFS 2015. Can anybody tell me the detailed step by step process, as I have never done migration within TFS versions?
You would need to do a upgrade for your TFS. Direct upgrade to TFS 2015 is supported only from TFS 2010 and newer. If your TFS deployment is on an older version than that, you will need to upgrade to TFS 2015 in multiple hops. For your scenario, you are on TFS 2008 you could upgrade to TFS 2010 or TFS 2012 first and then to TFS 2015.
The general process for upgrading an existing deployment of Team Foundation Server is to:
Prepare your environment. New system requirements may require you to upgrade hardware or software.
Expect the best, prepare for the worst. The single most important step you can take here is to ensure you have a complete and consistent set of database backups.
Do the upgrade!
Configure new features. Depending on what version you upgraded from, you may need to configure each team project to gain access to some of the new features made available.
Walk through an upgrade from TFS 2005 to TFS 2015.
We are planning for a migration from TFS to VSTS, while going through some article online I came across the below migration tool.
**
- https://blogs.msdn.microsoft.com/visualstudioalm/2014/05/12/migrating-your-data-from-tfs-to-visual-studio-online-with-new-free-utility-from-opshub/#comments
**
I have the following questions
In the article it was mentioned that we don't need to upgrade to the latest version of TFS since the migration utility will read from TFS 2010,2012,2013.
We have few projects in TFS 2008 and few in TFS 2013, according to the above statement we don't need to upgrade TFS 2013. But, what we have to do with TFS 2008 ? will this migration tool take cares of 2008 version as well or do we need to upgrade 2008 to 2013 and then start migrating to VSTS ?
Also, if anyone already has any experience with this tool can you please share your points ?
Thank you.
Unfortunately, TFS 2008 is not supported by OpsHub Visual Studio Migration Utility. You will have to upgrade it to 2010 or higher in order to make it compatible with the migration tool.
https://github.com/Microsoft/vsts-work-item-migrator
this migrator can do all 4 types of migrations of user stories
but you will need to download zip file and point that folder to new repo in vsts
I've running 2013 TFS Server. We have multiple Projects in a single ProjectCollection. However, we just inherited a bunch of projects from a company we just aquired, and they have all thier code in a 2010 TFS server. I need to migrate the projects from this 2010 instance of TFS into our 2013 TFS server.
I've read about doing a complete 2010 migration to 2013, but one of the steps there is to uninstall 2013 and re-install after attaching the databases from the older 2010 server.
Since this isn't an option, as we already have 2013 projects in our 2013 TFS server, I'm wondering what else I can do for this migration.
You should upgrade your 2010 to 2013 before you move the collection across. As you may have version issues with SQL and Windows you might be best using a temporary server that you restore the TFS 2010 databases to and upgrade to 2013.
Once you have upgraded your server to 2013 you can easily detach and attach to your existing server.
You don't need to uninstall TFS 2013, you can attach 2010 to 2013 directly. I suggest you do the following:
Detach TFS 2010 collection using TFS 2010 management console
Backup 2010 collection database using SQL server management studio
Restore this backup on the SQL server which is hosting TFS 2013 server databases
Open TFS 2013 management console and attach 2010 collection to it. This step will perform the upgrade, so once it's done you can start working with this collection on the 2013 server.
Another thing I would suggest is doing this on the test server first.