Criteria for Successful Project Migration

The characteristics of the source and the target model in a project migration map drives how successful a migration of a project is between the two models.

The following items are always migrated with a project, regardless of the source and target models:

  • Project status messages
  • Related documents and related document categories

The related documents of deliverables and activities that are mapped keep their relationship with the mapped document. Related documents of deliverables and activities that are not mapped are migrated to related documents of the project, without a relationship to a deliverable or activity.

  • Project discussions
  • Deliverable discussions for mapped deliverables
  • Start and end dates

The following items do not migrate, regardless of the source and target models:

  • Stages
  • Resource requests and allocations
  • Microsoft Project plans and templates
  • Quick grids

The items in the table below are migrated if they meet the listed requirements:

Project Component Requirements for Migration

Gates
  • Same relative position in the model (first gate, second gate, etc.).
  • Same name.
  • Same number of gatekeepers with matching gatekeeper functional areas.

Gate Documents
  • Same name.
  • Located in gates with the same names.

Only the latest version is migrated.

Deliverables
  • Same name.

Consider the following additional rules:

  • A target deliverable can map to at most one source deliverable. Deliverables are processed in the source and target models stage by stage, starting with the stage the source deliverable is in. The process continues with each following stage, looping back to the beginning of the model until it finds the first match to a target deliverable.
  • A file-based deliverable (with content) that does not map to a deliverable in the target model using the above rule, migrates to a related document in the target project.
  • A deliverable that includes an online form that does not map to a deliverable in the target model using the above rules, does not migrate to the target project.

Only the latest version is migrated.

Activities
  • Same name.
  • The activity's deliverable has been mapped to a deliverable in the target model.

Only the latest version is migrated.

Workflow History

The associated deliverable or activity must successfully migrate.

Metric Values
  • Same name.
  • Metric is available to both the source and the target models.

Notes:   

  • When matching project components between the source model and the target model, Accolade ignores initial spaces, initial numerals, and letter case, but not final spaces or numerals.
  • Accolade adds gate documents, deliverables, and activities from the source project that do not have a direct match in the target model as related documents in the target project. If a deliverable is created as a related document, all of its activities also are created as related documents in the target project.

  • Publishing older versions of a document that was included in a project migration or copy, or uploading a document that was downloaded from a source project into a new project, can update metrics in projects related to the source project, not the newly created migrated project. After a project is migrated, document owners should download the template or the latest version from the new project, refresh the data and update the project system ID references as necessary, and upload the document to the new project.

  • The migration map does not control whether a project team or the project history migrates to the new project. Process Managers select whether to include this information when completing project migrations.
Learn More: