This article provides 6 key factors to consider when implementing a change management plan for the migration of your project data from Aconex to Procore. Although Procore is used as the destination for this article, the same concerns are transferable to other CDE solutions supported by BIMLauncher.
The migration of live projects across separate and disintegrated systems are not always a simple case of switching one system off, and another on. Teams are actively collaborating around live data using carefully crafted processes for the project and switching CDE solutions can be disruptive. Effective change management planning can ensure minimal disruptions and maximum retention of team productivity.
The first thing to note is that BIMLauncher can only access data that is accessible to the Aconex organisation that it is connecting with for the migration. Data that is not in this scope, will not be transferred, and left behind once the migration has completed. The key points, with our recommendations include the following:
Documents present in your organisation's Aconex document register will be included only, and other organisations data will not. We recommend that any Documents required in Procore are transmitted to your organisation prior to migration.
Mail in your Mail register will be migrated and any Mail exclusively exchanged between other organisations on the project will not be included. We recommend that any Mail required in Procore include your organisation as a recipient prior to migration.
Mail migrated to Procore can impact your Procore user experience. Mail Threads that are not “closed-out” will create notifications to Procore users present on that Mail. We recommend that each mail thread is reviewed and considered prior to migration.
Procore Project environments must be configured for compatibility with your Aconex data prior to the migration. This includes configuration of permissions and metadata fields amongst other things across all the tools that you want to migrate data to.
Aconex Workflows are not transferable to Procore. This means that any information pertaining to a partial completion of a workflow will not be transferred. Our recommendation is to complete all workflows to ensure that an outcome is recorded on each document and is subsequently transferred with each document.
Guidance may need to be offered to project teams to effectively work with their project data in Procore. We recommend planning and distributing appropriate information about these concerns amongst the project teams in an early and often manner.
Please contact BIMLauncher if you would like to include a change management service as part of your migration, or if you would like to discuss how BIMLauncher’s implementation and technology can help you manage each of the challenges mentioned above.