If you're thinking about migrating from TFS on-premises to VSTS, it's not necessarily a simple decision as to how to get there. During this briefing we discussed some of the considerations that lead you to the right migration path, gotchas that we have encountered, and how we can help you get to VSTS quickly and effectively.

2. 2

3. What the heck is VSTS anyway?
VSTS in the DevOps ecosystem
Migration Considerations
Integration Scenarios with OpsHub
Next Steps
3

4. 4

5. 5

7. Simplified server management
Simplified administration
Improved connectivity with remote sites
A transition from capital expenditures (servers and the like) to operational
expenditures (subscriptions)
MSDN subscribers receive VSTS usage rights
Inexpensive/free options available for non-developers who need access
Immediate access to the latest and greatest features
Angela@PolarisSolutions.com Twitter: @OakParkGirl

8. • https://www.visualstudio.com/en-us/news/release-archive-vso.aspx

9. 9

10. “DevOps is the union of
people, process, and products
to enable continuous delivery
of value to our end users.”
- Donovan Brown
http://bit.ly/WhatIs-DevOps

11. TFS
Develop
Developer Workstation
Team Collaboration
Build&Test
Build/CI
Test
Deploy
Release
Monitor&Learn
Monitor
Microsoft
Ecosystem
Workstations - On-Premises| Hybrid | Cloud Monitoring- On-Premises | Hybrid | CloudALM Services - On-Premises| Hybrid | Cloud
DEV TEST QA
Environments - On-Premises| Hybrid | Cloud

12. Develop
Developer Workstation
Team Collaboration
Build&Test
Build/CI
Test
Deploy
Configuration
Monitor&Learn
Monitor
This graphic shows OSS and partner products that are
integrated with the Microsoft DevOps solution
Mixed
Ecosystem
Release

13. 13

14. Fully supported by Microsoft
Migrates entire collections to VSTS accounts*
Must be migrating from TFS 2017 RTM or Update 1
VSTS account must be backed by Azure AD
14

15. 15
OPTION PROS CONS
Migrate everything as-is
(TFS  VSTS)
MEDIUM EFFORT
• Tools needed to support migration
• No history lost
• All code kept in-tact with existing structures 
little ramp-up and disruption for in-flight projects
• No need to keep existing systems in place as
“Archive”
• Migration requires downtime
• Less likely that code will be “cleaned up”
• No restructuring of projects and teams for
better collaboration/visibility and easier
maintenance
Migrate project by project,
with history
MOST EFFORT
• Tools needed to assist with migration (OpsHub)
• No history lost, assuming migration tool works
perfectly
• Less need to keep “Archive”
• Opportunity to restructure and consolidate
projects, change process templates, improve
code sharing
• Opportunity to leave projects behind if obsolete
• Not all vendors offer an easy integration path
from their tools to VSTS
• Migration effort could be high
• Some ramp-up/disruption to learn new
structure of projects, code
• Less incentive to “clean-up” and organize
software assets more effectively
Tip migration
LEAST EFFORT
• No special tools needed for migration
• Opportunity to restructure and consolidate
projects, change process templates, improve
code sharing
• May need to keep archive of existing SCM and
work items
• Work items lose attachments and relationships
(without a tool like OpsHub)
• Some extra work required to access history
• Some ramp-up/disruption to learn new structure
of team projects and source code

16. 16
OPTION PROS CONS
Migrate everything as-is
(TFS  VSTS)
MEDIUM EFFORT
• Tools needed to support migration
• No history lost
• All code kept in-tact with existing structures 
little ramp-up and disruption for in-flight projects
• No need to keep existing systems in place as
“Archive”
• Migration requires downtime
• Less likely that code will be “cleaned up”
• No restructuring of projects and teams for
better collaboration/visibility and easier
maintenance
Migrate project by project,
with history
MOST EFFORT
• Tools needed to assist with migration (OpsHub)
• No history lost, assuming migration tool works
perfectly
• Less need to keep “Archive”
• Opportunity to restructure and consolidate
projects, change process templates, improve
code sharing
• Opportunity to leave projects behind if obsolete
• Not all vendors offer an easy integration path
from their tools to VSTS
• Migration effort could be high
• Some ramp-up/disruption to learn new
structure of projects, code
• Less incentive to “clean-up” and organize
software assets more effectively
Tip migration
LEAST EFFORT
• No special tools needed for migration of SCM
• Opportunity to restructure and consolidate
projects, change process templates, improve
code sharing
• May need to keep archive of existing SCM and
work items
• Work items lose attachments and relationships
(without a tool like OpsHub)
• Some extra work required to access history
• Some ramp-up/disruption to learn new structure
of team projects and source code

17. What is being migrated to VSTS?
What history is needed? ACTUALLY needed?
Are you changing your SCM tool (VC vs. Git)?
Are you changing processes?
Is there any restructuring or clean-up that needs to be done?
Do you need a big bang migration, or is a staggered
migration required?
17

18. Do you have existing build infrastructure to integrate with or
replace?
Do you have existing test infrastructure to integrate with or
replace?
Will your existing deployment and release processes be
supported in, or migrated to VSTS?
18

19. Do you need to change how teams and areas are used to
leverage new features?
Do you need to change how iterations are used for better
cross-team collaboration?
Do you need to re-write build and release automation?
19

20. 20

21. Want to move forward with a VSTS evaluation?
1. Work with your local Microsoft Dx team to determine if you’re adequately
licensed for VSTS
2. If you’re not already using Azure AD, start the process
3. Create a free VSTS account to kick the tires
4. Create an inventory of everything used today for building, testing, and
releasing software
5. Engage an experienced partner and make sure it gets done right the
FIRST time
21

22. Assist with an ALM or DevOps Health Check
Plan and Execute a VSTS migration effort and roadmap
Setup your Build and Release Pipelines
Integrate VSTS with existing ALM and DevOps tooling
TFS, VSTS, DevOps and agile related training
Coaching on agile and DevOps practices
22

23. Email: Angela@PolarisSolutions.com
LinkedIn: https://www.linkedin.com/in/andugan
Slideshare.NET: http://www.slideshare.net/angelabinkowski
Twitter: @OakParkGirl, @ChicagoALM, @TeamPolaris
Blog - http://www.tfswhisperer.com/
Chicago Visual Studio ALM User Group - http://www.chicagoalmug.org/
Polaris Solutions website - http://www.polarissolutions.com/
Angela@PolarisSolutions.com Twitter: @OakParkGirl

24. Title: Zero to DevOps
Presenter: Donovan Brown
Principal DevOps at Microsoft
When: Wednesday, April 12th 6pm
Where: Microsoft Chicago Office MPRs 1-3
200 East Randolph, 2nd Floor
Chicago IL, 60601
Register: https://polarissolutions.com/events

25. We’ll be hosting a live podcast and delivering a number of talks
including “Agile Metrics that Matter”!
Saturday, April 28th, 2016 at IIT – Chicago
Always FREE!
More info at: http://www.chicagocodecamp.com/

26. Getting your Agile Teams “Unstuck”
August 8th, 2:30pm
ThatConference
August 7th through 9th
Wisconsin Dells, WI
General and family tickets available now!
ttps://www.thatconference.com/

27. Latest Episode: Continuous Delivery
http://www.coachandbeer.com/
Now on iTunes, Stitcher, and
Agilepod!

28. 28