The Microsoft Project Online Migration Process
Integent’s process for a migration to the cloud usually involves performing the migration process twice.
The first migration can be referred to the development migration. This migration helps uncover issues that may be encountered during the process of migrating to the project online tenant.
For instance, project schedules from the previous project management solution may not migrate correctly. For example, are we unable to open projects after the migration with Microsoft Project Professional? Perhaps items in the SharePoint Project Sites fail during migration, such as documents. Similarly, a lookup table may not come over correctly or even a project portfolio analysis is missing.
Although all migrations have challenges, migrating from earlier versions of Project Server bring up even more challenges. Consequently, a Project Server 2007 to Project Online migration provides some unique challenges. Subsequently, the route taken in your migration may require a Project Server 2007 to Project Server 2010 migration first. In short, this depends on whether the migration path taken involves any type of migration tools.
A Project Server 2013 to project online migration, however, is a bit less complex.
The importance of encountering and resolving these issues during the development migration cannot be understated. That is to say, resolving project and SharePoint data issues is important to the team. Most importantly, because it helps determine the length of time the production migration will take. Above all, we want a smooth and condensed production migration.
The development migration does not typically require migrating the entirety of the customers data. What it does entail is a full migration of the configuration and resources, with a subset of projects and SharePoint data.
Once the development migration has been completed it is time to validate the results. The validation is first performed by the Integent team during and after migration activities have taken place. Firstly, validation includes a review of all custom fields, SharePoint content (documents, issues, risks), Resources, System Views, and Project Schedules.
Once the Integent team has completed migration activities and internal validation, the customer will become involved in validation. Most importantly, the customer be involved in order to confirm the success of the migration themselves and gain their buy-in.
Upon completion of the development validation the production migration is performed. Likewise, the process is the similar to the development with a couple caveats.
- If using one instance of Project Online, some of the previously migrated data will be cleaned. Secondly, all data will be migrated.
- Again, if using one instance there is no need to re-migrate the configuration. Therefore this step would not be necessary.
- If using a second instance the process would be identical to the development migration. However, except that the Integent team would be migrating all projects and Project Site data.
Once all migration activities have been completed, the production system would be validated. Similarly, the validation process would be just like that performed in development. Once complete, the system would typically be released to the user community.
If the customer intends on using the Project Online Migration as an opportunity to revise the configuration. That is to say enhance their configuration by creating custom fields and views. On the other hand perhaps trim their configuration of unused items.
Above all, this would typically be performed after the production migration has been successfully completed and validated. Microsoft PPM, the cloud based product has many features available. Though tempting, keeping it simple is something the better approach.
Integent is ready to provide Microsoft Project Online Migration Consulting services to move you to the cloud. Contact us for an assessment today.