MicrosoftThere is no reason that I can see (other than maybe disk space and web access costs - practically negligeable for a company like Microsoft) that Microsoft couldn't just leave Project Online/pwa up and running with read-only access to anyone with a PP3 or PP5 license for another year or two to let people get whatever they need off of it during their transition to whatever product they decide. And the fact that they don't offer any kind of official detailed migration path/tool for their customers without paying 3rd party companies is shameful.
Unfortunately it isn't that simple Chrstopher. Project Online shares servers, databases and other infrastructure with SharePoint - true multi-tenant, so even in one SharePoint content database there could be rows from different tenants that might be items in PWA or might just be another tenant's SharePoint documents. The project business has warned for a while that it would go away, and I guess the final push was SharePoint needing to make some changes which would have also needed work from Project, to maintain their PWA pages for the Project Online application, which they weren't prepared to take on. (This was the reason given at a recent conference by a Microsoft person). So it can't just be left running. I agree totally that the lack of a native migration tool is bad - especially as one was promised Q and A on the Future Vision of Project | Microsoft Community Hub although it was envisaged to be to the new product - and it has become very clear over the interveening 7+ years that the new product isn't something the majority of customer would or even could migrate to.
