# Act 1

[Igor Minar at ng-europe, October 23](https://www.youtube.com/watch?v=g-x1QKriY90a):

> Once 2.0 is ready, then we’ll figure out what’s the best way to migrate. *At this point we’re really trying to create the best 2.0 ever, and once we know what that is, we’ll go back and see what is the best migration path*. Because if we run it the other way around, that would constrain what we can do with 2.0.

# Act 2

[David Iffland, InfoQ, October 27](http://www.infoq.com/news/2014/10/angular-2-atscript):

> The team also *indicated that there is no migration path from Angular 1.X to 2.0*, though they left the door open for this possibility.

# Act 3

[Coman Hamilton, JAXenter, October 28](http://jaxenter.com/angular-2-0-112094.html):

> As InfoQ’s David Iffland comments, the framework will be “drastically different looking”, meaning users will need to get to grips with a new kind of architecture. *It’s also been confirmed that there will be no migration path from Angular 1.X to 2.0*.