Move Tasks to Another Project

In the Game Plan, tasks can be moved from one project to another.
The main use cases for moving tasks to another project are...
1. Improve performance for large projects.
  1. Performance can degrade when a project has ≥2000 tasks. The tasks could be actual project tasks, or….
    1. "What-if" scenarios that you want to keep, but you don't want those extra tasks adversely impacting performance. To improve performance, the "what-if" scenarios could be moved to another project.
  2. Perhaps you have a project that lasts for years and has many thousands of archived tasks. Performance can degrade when all archived tasks are loaded. The older archived tasks from 1-2+ years ago could be moved to another project (instead of deleting them).
2. Combining related small projects into a single project...
  1. Sometimes after planning things as separate projects, you might realize they are related and decide you want to put them into the same project.
    1. Sometimes some of those tasks have been completed and you want to maintain the lifecycle history (which you would lose if you copy/pasted them).
3. When tasks were accidentally created the wrong project.
4. Moving tasks to another project can be a shortcut to assign resources to a project (see #7 below).
To move tasks from one project to another in the Game Plan, select Multiple Projects, then load both projects.
To move one or more tasks from one project to another (Target Project), select and drag them in the Task Grid. Multiple tasks can be selected by selecting a summary task, using the Ctrl-key, or using the Shift-key.
The lifecycles of all tasks are maintained (Sandbox, Planned, Active, Completed, Archived).
If there is a link between tasks and one of the tasks isn't moved to the Target Project, a cross-project link is created automatically.
If you attempt to move tasks assigned to resources that are not assigned to the Target Project, and you are not the owner of the Target Project (assigned by a Playbook Administrator), you will receive an error message and will not be permitted to continue.
If you are the owner of the Target Project, you will receive a warning with the option to assign the missing resources.
When dragging a project, a new Top-Level summary task is created in the Target Project and the tasks move to it, while the original Project remains.
The main differences between moving tasks vs. copy/paste...
1. All Active/Completed/Archived tasks retain their lifecycle when moved from one project to another while copy/paste changes them all to Planned by default.
2. Any Active/Completed/Archived task segments with customized "hours per day" are maintained when move while copy/paste resets them to "average hours per day".
3. The Change Log is maintained for each task when moved, while copy/paste creates a new task and Change Log.
4. When tasks are moved, the start/end dates are maintained exactly. When using copy/paste, all ‘Start on’ tasks get switched to ‘Earliest’, which removes any spacing you may have added between tasks. There is an option to maintain the spacing, but you have to remember to set it.
5. If you are moving tasks to a project that the resources aren’t assigned to yet...
  1. If you are the owner of the Target Project, you can assign those resources during a move.
  2. When you copy/paste, you have to cancel the copy/paste, go to Admin and have them assign the resource(s) to the project, browser-refresh the main site, and then start the copy/paste over again. Or you can leave the tasks unassigned and reassign them later.
Need a hand? Contact a Customer Success Engineer today!