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

# Transfer Project

> How to move a project from one organization to another

## Overview

Transferring a project moves it — along with all its data — from the current organization to a different one. The project keeps all its contracts, catalog, statements, and settings intact.

<Note>
  Transferring does not copy the project. It moves it entirely out of the source organization and into the target.
</Note>

***

## Who Can Transfer Projects

| Role       | Can Transfer |
| ---------- | ------------ |
| **Admin**  | Yes          |
| **Member** | No           |

You must be an **Admin** in the current organization to initiate a transfer. The list of target organizations is limited to other organizations where you also hold an **Admin** role.

<Note>
  Royaltyport system administrators can transfer projects to any organization.
</Note>

***

## Transferring a Project

<Steps>
  <Step title="Locate the Project">
    Find the project card on your organization's Projects page.
  </Step>

  <Step title="Open the Menu">
    Click the menu (three dots) on the project card.
  </Step>

  <Step title="Select Transfer Project">
    Click **Transfer Project**. A dialog will open showing your eligible target organizations.
  </Step>

  <Step title="Search and Select a Target">
    Browse or search the list of organizations. Select the one you want to transfer the project to.
  </Step>

  <Step title="Confirm Transfer">
    Review the transfer summary showing the project name and destination organization, then click **Confirm Transfer**.
  </Step>
</Steps>

***

## What Gets Transferred

All project data moves with the project to the new organization:

| Data Type                                    | Status      |
| -------------------------------------------- | ----------- |
| **Contracts & extracted data**               | Transferred |
| **Catalog items** (recordings, compositions) | Transferred |
| **Royalty statements & insights**            | Transferred |
| **CRM data** (entities, artists, relations)  | Transferred |
| **Custom views & tags**                      | Transferred |
| **Agent configurations**                     | Transferred |
| **Project settings**                         | Transferred |

***

## Before Transferring

<AccordionGroup>
  <Accordion title="Notify team members">
    Members of the source organization who are not in the target organization will lose access to the project.
  </Accordion>

  <Accordion title="Check integrations">
    Verify that any external integrations (like Curve) will still work correctly in the new organization context.
  </Accordion>

  <Accordion title="Confirm admin access">
    You need Admin role in both the source and target organizations to complete the transfer.
  </Accordion>
</AccordionGroup>

***

## Permission Denied

If the **Transfer Project** option is grayed out:

1. **Check your role** — only Admins can transfer projects
2. **Contact an Admin** — ask someone with the appropriate permissions to transfer the project

If no organizations appear in the transfer dialog:

1. **Check your memberships** — you can only transfer to organizations where you are also an Admin
2. **Request admin access** — ask to be promoted to Admin in the target organization

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Projects Overview" icon="folder" href="/projects/overview">
    Understanding projects and how to use them.
  </Card>

  <Card title="Projects in Your Organization" icon="building" href="/organizations/projects/overview">
    How organizations and projects relate.
  </Card>

  <Card title="Delete Project" icon="trash" href="/projects/delete-project">
    How to permanently delete a project.
  </Card>

  <Card title="Member Roles" icon="users" href="/organizations/settings/members/roles">
    Understanding organization roles and permissions.
  </Card>
</CardGroup>