Moving Phases or Tasks

You can use the Key Conversions Utility to move a phase from one project to another project, or a task from one phase to another phase.

Moving Phases and/or Tasks for Projects with Plans

If a plan is associated with a project, the use of the Key Conversion utility to move a phase or task may also impact the plan's data, work breakdown structure, and mapping. The types of plans that may be mapped to a project, phase, or task include:
  • Vision plans (if you are using the Vision Resource Planning module)
  • iAccess for Vision plans (if you are using the iAccess for Vision application)
  • A combination of both Vision and iAccess for Vision plans
There are some basic requirements that you must take into consideration when moving phases and/or tasks that have associated plans. For purposes of explanation, the records will be referred to as follows:
  • From record: This is the record that will be moved into the To record.
  • To record: This is the record that the From record is moved into.

The way the phases and/or tasks are moved depends on how the From and To projects are configured and the types of plans that are in use. Refer to the following scenarios for general examples.

Phases and Tasks With a Vision Plan
  • Move a task from a phase to another phase within the same project with a Vision plan: If using a Vision plan, the task is unmapped from the From phase but is not added to the plan under the To phase. You must add the task and map it under the new phase. You should also consider if you want to remove the unmapped task under the From phase.
  • Move phases or tasks from a project with a Vision plan to a project without a plan: The phase or task's information is moved to the To project. Any associated mapping is automatically removed from the plan.
  • Move phases or tasks from a project with a Vision plan to a project with a Vision plan: The plans are not combined. The phase or task in the From project is removed from the project's record in the Project Info Center and unmapped from the plan. You must manually add the phase or task to the To project's plan.

Phases and Tasks with an iAccess for Vision Plan

  • Move a task from a phase to another phase within the same project with an iAccess for Vision plan: The task is automatically removed from the From phase and shown under the To phase.
  • Move phases or tasks from a project with an iAccess for Vision plan to a project with an iAccess for Vision plan — If expenses are being planned, they are checked against the Expenses Planning Levels in iAccess for Vision Plan Settings for each selected project. They must use the same level. If consultants are being planned, the consultants are checked against the Consultants Planning Levels in iAccess for Vision Plan Settings. If they match, the phases or tasks will be moved. If the planning levels do not match, you must use iAccess for Vision Plan Settings to reset the planning levels to match between the two projects before you can proceed.
Phases and Tasks Where the Plan Types are Different
  • Move phases or tasks from a project with a Vision plan to a project with an iAccess for Vision plan: The phase or task will be removed from the From project and will no longer be mapped to the Vision plan. You will see <None> on the Labor tab to indicate that the new phase or task is no longer mapped to the project. You can delete the phase or task from the plan. The phase and task automatically display on the To project's iAccess for Vision plan.
  • Moving phases or tasks from a project that has an iAccess for Vision plan to a project that has a Vision plan: Vision moves the phase from the project with the iAccess for Vision plan to the To project that has a Vision plan. The phase is removed from the project's record and is unmapped from the iAccess for Vision plan. You must manually add the phase or task to the To project's Vision plan.