Skip to main content
Move a task when its conversation belongs in another Project. Its messages and active share links move with it, while referenced knowledge and integrations stay in the original Project.

​
Move one task

  1. Open the task’s ⋯ menu and select Move to project.
  2. In Move chat to another project, search for and select a destination Project. You must have access to it, and it must belong to the same Organization.
  3. Click Move chat.
  4. After Move complete, choose whether to stay where you are or go to the destination Project.

​
Move several tasks

From the Tasks list, select multiple tasks and choose Move to project. Select the destination, then confirm the move. This bulk dialog still uses “chats” in its labels: for example, Move 3 chats to another project as the title and Move 3 chats on the confirmation button. Chief moves the eligible tasks together.
⚠️ Important: Tasks attached to a Live Session, transcription, or automation Action cannot be moved. Chief also refuses the move if you cannot access the destination Project.

​
What moves and what stays

  • The conversation, messages, and active sharing links move with the task.
  • Referenced Project knowledge and connected integrations stay in the original Project.
  • The destination Project’s roles and access rules determine who can open the moved task.

​
FAQ

Chief keeps tasks attached to a Live Session in their original Project so the meeting record and conversation remain connected. Create a separate task in the destination Project if needed.
The messages move, but referenced knowledge stays in the original Project. People opening the moved task may not have access to those source files.