Many implementations of Oracle Primavera P6 require the migration of data from existing project management tools. The most common situation we encounter is the migration of data from Microsoft Project to Oracle Primavera’s P6.
While there are many issues involved in the migration of data from Microsoft Project to Oracle Primavera P6, most clients focus their attention on the technical data transfer piece. Although this is a vital part of the migration process, it is, in itself, fraught with common pitfalls that can be avoided.
Careful attention must also be paid to normalizing the data, including activity, resource and calendar information. Normalizing the data requires in-depth knowledge of both Microsoft Project and Primavera P6. Additionally, there are different versions of Microsoft Project and Oracle Primavera P6, each of which has slightly different and subtle nuances in the way in which it imports and exports data. Data normalization also requires a thorough understanding of the future state Primavera P6 configuration, which may be a work in progress as the Primavera P6 implementation goes through its initial prototyping phase.
In summary, clients can spend too much time and effort on migrating Microsoft Project data to Primavera P6, balancing evolving configurations, data anomalies and technical data transfer problems. Ten Six has experience in accelerating this process, avoiding problems and making the migration process smoother and easier.