We moved our TFS to the cloud

Previously at SSW, we had TFS on-premises (at tfs.ssw.com.au) and TFS in the cloud (at ssw.visualstudio.com) and I let the devs choose where they wanted to place new projects. Initially I was surprised to notice that most projects went to the cloud. Eventually I noticed they *always* chose the cloud. So I’m happy to announce we now have migrated everything to the cloud.

Our TFS migration went well and if we did it today, it would go even smoother. We have a good relationship with the Visual Studio and TFS teams, and for our migration we had some bumpy bits. Rogan Ferguson from the TFS Database Import Service Team helped us plenty and we gave some feedback and it was impressive to see the fixes done so quickly

Using what we learned from the migration, SSW Solution Architect Danijel Malik and I gave a presentation on the best tools and simplest way of making the move — check out the video of the presentation below.

We also gave this presentation at Ignite — you can see that version of the presentation over at Channel 9.

You should do it too

The TFS Database Import Service team say they support 2 versions of TFS at one time. You can assume that when a new version of TFS comes out, support for the old version is dropped. You see this mentioned in phase 3 of the TFS Migration guide (page 21). Currently the two supported versions are TFS 2017 RTM and TFS 2017 Update 1. However, the team has been extending the support for TFS 2015 Update 3 beyond the normal window for a few months now. They have said that this version of TFS will be retired on Monday, April 24th. Better factor this deadline into your migration plans.

Call us if you want to join the fun in the cloud and jump on VisualStudio.com (aka Team Services).

Originally published at adamcogan.com on April 13, 2017.

Like what you read? Give Adam Cogan [SSW] a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.