This quickly leads to the realization that things are more complicated that first anticipated and organizations end up doing most of the work manually after all. The first order of business is to convert the schedules from Primavera into Project Online schedules. Which takes us to… “Let’s try automating the migration!” But organizations with hundreds or thousands of complex projects cannot even fathom this approach. This usually only applies to organizations that need to migrate a very small set of low-complexity projects (which is rarely the case). Reactions to this challenge can generally be put into one of three categories: “Let’s manually create our projects in Microsoft Project Online!” Organizations that have made, or are looking to make, the switch from Primavera to Microsoft Project Online are faced with the daunting task of migrating their project information.
This decision can be driven by the need to move to a cloud-based SaaS solution, or simply because the organization wants a better user experience and increased flexibility for managing projects and portfolios. These days, more and more organizations are looking to make the switch from Oracle Primavera to Microsoft Project Online.
0 kommentar(er)
