While Microsoft is calling their new web framework "MVC 6" and branding it as a unified successor of MVC / Web API / Web Pages, the reality is much more complicated than that. The newASP.NET 5 alone is a completely different managed runtime, which results in plenty of changes, compatibility issues and necessary adjustments when trying to bring your old application over to the new world. On top of that MVC 6 introduces plenty of changes. While controllers in "old" and "new" world may look similarly, a lot of core concepts that you might have been used to when working with Web API projects have changed, and finding corresponding ones is a tricky, and often frustrating, task. This talk will draw parallels between the Web API framework pipeline that you might be used to (MessageHandlers, Filters, Selectors, Formatters etc), to the one which are part of MVC 6, and explore the techniques you can use when migrating a Web API project to MVC 6 - hopefully easing your transition into the next generation of ASP.NET.