Moving Projects

You can move a project from one Project application to another when organizational changes require it — for example, when a project changes scope or when you're setting up a new Project application and want to redistribute existing work into it.

Before moving a project, be aware that some data will be permanently lost, and other items may be modified, because parts of a project are tied to its source application's configuration. Review the sections below to understand what will and won't carry over, and use that to decide whether to move ongoing projects or complete them where they are.

Moving projects is designed for occasional organizational needs, not as a routine step in any workflow.

What Changes When a Project Is Moved

What Moves With the Project

The following items move to the new application with the project:

• Announcements
• Calendar Events and Feeds
• Time & Expense entries
• Feed
• Issues and Issue Categories
• Links and Link Categories
• Plans and Tasks
• Resources, schedules, and resource requests — for users who are members of the destination application
• Risks and Risk Categories
• Role Forecasts
• Stakeholders

Issue and Risk statuses will be matched first by name, then by status class. If no match is available, the default status will be used.

What is Permanently Lost

The following data will be permanently lost:

• Benefits
• Goals
• Organizational Risks
• Processes
• Scorecards
• Systems
• Document Workflows

These are primarily project-request–related items defined within each application. Because different options may be configured in the destination application, these values cannot be carried over.

Resources Not in the Destination Application

Resources who are not members of the destination application will be removed from the project during the move. Their associated materials and future resource schedules will be handled according to the option you select during the move (see step 6 below). One project member will receive the materials and schedules of all removed resources. To assign items to multiple delegates, do this before moving the project. In the project, navigate to Resources, and select Actions > Remove Resources.

Custom Attributes

Custom attribute values are not transferred to the destination application. Instead, the values are copied into a feed entry on the project for reference — the same behavior as when a ticket is moved between applications.

Issue and Risk Statuses

When the project moves, issue and risk statuses are automatically mapped to the destination application using the following logic:

1. If an active status with the same name exists in the destination application, that status is used.
2. If no name match is found but an active status with the same status class exists, the active status in that class with the lowest Order value is used.
3. If no match exists by name or status class, the default status is used.

Moving a Project

To move a project from one application to another: 

1. Open Work Management (TDNext), click View Applications, and open the source Project application.
2. In the left navigation under Projects, select the project you want to move.
3. From the Project Details page, select Actions > Move to Application. This will be visible only to users who meet all these criteria:
   • You have project management access (as project manager, alternate manager, or via Manage All Projects or Manage Projects in My Portfolios and Programs).
   • You are a member of the source Project application with the Move Projects to other project applications permission.
   • You are a member of the destination Project application.
4. Choose the destination Project application. (This step will only appear if there are more than two Project applications.)
5. On the Move to [Application Name] page, review the help text, which summarizes what will and will not be carried over.
6. Fill in the following fields:
   • Comments — Enter any notes about the move.
   • Type (required) — Select the project type in the destination application.
   • Status — You may select a different status, but you cannot switch between open and closed statuses during the move.
   • Health — Optionally update the project health indicator.
   • Resources to Remove — Optionally choose resources to remove from the project. 
   • Delegate To — Select one project member to receive the materials and schedules of all removed resources.
     • If you need to assign items to multiple delegates, do this before moving the project. In the project, navigate to Resources, and select Actions > Remove Resources.
   • Associated Materials and Schedules — Choose how to handle materials and schedules for the removed resources:
     • Delete associated materials and future resource schedules
     • (Default) Transfer associated materials and future resource schedules to the selected delegate
7. Click Move in the page toolbar.
8. Confirm the move in the dialog. The page will reload, displaying the project in its new application.