Migrating from TFS to VSTS - tfs

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

Related

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.

Team Foundation Server 2008 to 2015 Project Migration

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.

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

transfer projects from vss 2005 to tfs 2013

I installed TFS 2013 on my Windows server 2012 and I would like to transfer my projects from vss to tfs.
I downloaded the vss to tfs tool from [microsoft tool][1], but I was unable to install it because of compability mode, error message: "Windows Program Compatibility mode is on. Turn it off and then try Setup again"
According to this Buck Hodges blog post, you're not going to be able to do this in Windows Server 2012, and Microsoft isn't going to fix it. See the following comment:
... unfortunately, it is blocked in the installer. Right now we don't
have plans to re-release it, so you would need to run it on Win7-based
OS.
Incidentally, the post also addresses the question of upgrading to TFS 2013.
I would like to know if the upgrade tool will work with TFS 2013?
The documentation only mentions TFS 2010 and 2012. However, Hodges also addresses this:
... it should work with the caveat of what OS you install it on (see previous
comment).
the solution for me was : i installed the tool on another machine with win server 2008 , convert the projects and than move them to the tfs 2013

ugrading from TFS 2012 express Update 3 to TFS 2013 server edition

We are planning to upgrade from TFS 2012 express Update 3 to TFS 2013 server edition. Does anyone has any suggestion on how to do this or what steps should I do.
I don't know of any specific issues with that upgrade path. But here are some things that might help.
Read over the TFS Planning and DR guide
Make sure your server meets the new System requirements
Check out the upgrade documentation here, and specifically "Upgrade TFS Basic or Express"
Backup\Snapshot your TFS server before you start the upgrade.

Resources