# Catalog transfers
Source: https://docs.aden.space/docs/help/make-music/catalog-transfers

Move a catalog (tracks, albums and everything attached to them) from one team to another in one step, with the record in both teams' activity logs.
{/* Generated by `bun docs:publish` from docs/features/catalog-transfers.md: edit the spec, not this file. */}

## What it is [#what-it-is]

When a catalog changes hands, an artist moves to a new management org, two
labels merge rosters, or you reorganise your own teams, the songs are only
half the story. Versions, artwork, project files, release plans, splits and
contracts all have to arrive with them, and both sides need a record of what
actually moved. Catalog transfers do that in one step: pick the tracks and
albums (or the whole catalog), pick the receiving team, and everything
attached to those songs moves together.

Nothing is sold or duplicated. The catalog changes owner inside Aden, links
keep working, and both teams get the transfer in their activity log.

## Using it [#using-it]

Go to your team's settings and open "Catalog transfers". Hit "New transfer",
pick the receiving team (the picker lists the teams you administer),
choose the whole catalog or specific tracks and albums, and confirm.

You need to manage both sides: as a team admin, or as an admin of the
organisation the team belongs to. That's what makes org-to-org handovers
work like team-to-team ones: an organisation admin moves a roster team's
catalog to a team in another organisation they manage. For a handover
between two separate parties, the receiving side makes you an admin first,
then you transfer.

After the transfer, the sending team stays visible on each track as a
previous collaborator, so credits and history read correctly, and both
teams' activity logs carry the record of what moved.