> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chief.bot/llms.txt
> Use this file to discover all available pages before exploring further.

# Moving a task to another Project

> Move one or more tasks to another Project while keeping their messages and active share links together.

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](/help/chatting-with-chief/how-chats-work), 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.

<Warning>
  ⚠️ **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.
</Warning>

## What moves and what stays

* The conversation, messages, and [active sharing links](/help/sharing-visibility/sharing-a-chat-via-secret-link) move with the task.
* Referenced Project knowledge and connected integrations stay in the original Project.
* The destination Project's [roles and access rules](/help/projects-sharing-teams/roles-access-levels-owner-collaborator-reader) determine who can open the moved task.

## FAQ

<AccordionGroup>
  <Accordion title="Why can't I move a Live Session task?">
    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.
  </Accordion>

  <Accordion title="Do my file references move too?">
    The messages move, but referenced knowledge stays in the original Project. People opening the moved task may not have access to those source files.
  </Accordion>

  <Accordion title="Will an existing secret link still work?">
    Yes. Active share links move with the task. You can [revoke a link](/help/sharing-visibility/revoking-access-to-a-shared-chat) before or after the move.
  </Accordion>
</AccordionGroup>