Migrate data from TFS 2010 to TFS 2017 - tfs

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.

Related

Best approach to upgrade TFS 2015 to TFS 2018?

We currently have TFS set up on three Win2012 servers: app server, build server, deployment server.
It is using SQL Server 2014 which is on a separate server (let's call it SQL1). We have a SQL 2017 server (SQL2) that is not in use but can be used to migrate databases there.
Our plan is to upgrade to TFS 2018. Since TFS 2018 does not support SQL 2017, What is the best approach here?
In-place upgrade TFS 2015 to TFS 2017 (which supports SQL 2014). Then upgrade SQL 2014 to SQL 2017 on SQL1. Once SQL upgrade is done, then we can do another in-place upgrade to TFS 2018.
Migrate existing TFS databases from SQL1 to SQL2 server. Upgrade TFS 2015 directly to 2018 and point to databases on new SQL 2017 server.
Backup SQL1 databases. Upgrade SQL1 to SQL 2017. Restore databases. In-place upgrade TFS 2015 directly to TFS 2018.
What would be the best approach here? Thanks.
I recommend the following:
Spin up fresh Windows 2019 or 2022 servers.
Install SQL Server 2019 on one of 'm.
Install Azure DevOps Servers 2020 or 2022 on the other.
Restore the databases on the SQL server.
Run the configuration wizard on the Azure DevOps Server and have it perform the upgrade.
In most cases this process can run in a couple of hours if you've prepared all the machines and accounts, DNS entries etc.

TFS 2013 migration to VSTS

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.

In-place migration from TFS 2010 to TFS 2015

I have a question about in-place upgrading from Team Foundation Server 2010 to Team Foundation Server 2015
Our current situation contains the following software versions:
- Windows Server 2008 R2
- SQL Server 2008 R2
- Team foundation Server 2010
We would like to perform an in-place upgrade of this server to the following new versions.
- Windows Server 2012 R2
- SQL Server 2014
- Team Foundation Server 2015
It is a single server installation on a VMWare environment. Adding additional resources is not a problem. So for that reason we would like to go for an in-place upgrade.
With the information I found on https://msdn.microsoft.com/library/vs/alm/tfs/administer/requirements it does not seem to be possible with our current SQL version to upgrade to TFS 2015 in one go.
Should we first upgrade to TFS 2012 (which still supports SQL Server 2008 R2)? Then upgrade to SQL 2012 SP1, then TFS 2015..and so on.
Or should it be easier in our situation to migrate the TFS 2010 databases to an new server with all the latest versions and then upgrade the databases (and so not performing an in-place upgrade after all)?
There is a lot of documentation describing various migration scenario's so that is causing some confusion.
Can someone give us some suggestions or answer on what is the best way forward?
What you could do is:
Uninstall TFS from the current server
Uninstall SQL Server on the current server
Install SQL Server 2014 on it
Attach the databases to the SQL Server 2014
Install TFS 2015 and walk through the upgrade wizard.
It's sort of an in-place upgrade. Indeed be aware of the Sharepoint issue, it will be your pressing reason to make in in-between upgrade stop along the way, should you need it.
I see many client de-coupling Sharepoint from TFS anyway, as the Sharepoint functionality is rarely used, or even known.
Something else to consider. If you're using any of the sharepoint functionality in TFS 2010, and you want to keep the stuff stored there, then you'll probably want to upgrade to TFS 2012 anyway. TFS 2010 uses WSS 3.0 and TFS 2015 uses the latest version of sharepoint express. There is no direct migration from WSS 3.0 to the latest version so you'll need to use the bundled version in TFS 2012 as an intermediary upgrade.
If sharepoint isn't an issue then I'd suggest building out new infrastructure and migrating the TFS databases. This will be easier and IMHO has a couple of other benefits.
you can do a test migration to flush out any additional issues
get some timings so you know how long the real migration will take

Partial TFS Upgrade

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.

In Tfs 2008 to 2010 upgrade how to point tfs database of another server in the configure wizard?

Tfs 2008 to be upgraded to TFS 2010, how do i point the database which is in another server in different domain? Otherwise is it possible to install as fresh and then move the database from TFS 2008 to TFS 2010? is there a option to directly move the database from TFS 2008 to TFS 2010.
Basically you back up the databases, restore them on the new server and use the configuration wizard to upgrade them.
There's a number of blog posts with good walkthroughs.
http://blog.hinshelwood.com/upgrading-team-foundation-server-2008-to-2010/

Resources