Using Inherit Catalogue as a Parent User

If you are a Parent user, you can use the Inherit Catalogue functionality to sync catalogue items into another client automatically. This can help you manage multiple accounts while keeping catalogue data consistent without duplicating work.

Where to switch it on

This feature is only accessible when your Curve client belongs to a Parent account.

Go to Clients > edit the target client > open the Inherit Catalogue panel. From there, select the source client, assign an optional Catalogue Group if needed, and check the applicable item types.

How It Works

Once enabled, the Inherit Catalogue feature automatically pulls in relevant items from the original (source) client into the new (target) client. However, for the sync to trigger successfully, there's an important step to be aware of:

The sync only triggers when items in the original client are saved.

This means if the items have not been saved in the source client after the new client has been created, they won’t sync over to the new client - even if the Inherit Catalogue setting is enabled.

When an item syncs, the copy in the target client stays linked to the original item in the source client. Any later changes you save to the original are then applied to the linked copy as well. Because of this, all catalogue updates should be made in the source client. Changes made directly in the target client are not synced back to the source.

Forcing the Sync

To force the sync to run and copy catalogue items into your new client:

Go to the relevant page in the original (source) client - e.g., the Works or Tracks/Releases page.
Ensure no search filters are applied to your view.
Click Export to download the full list of items.
Without making any changes to the export file, go to the same page in the original client and Import the file back in.

This re-import will bulk “re-save” all items, which triggers the Inherit Catalogue sync to copy them over into the new (target) client. Ensure you do Tracks before Releases, so that the Releases correctly link to their associated Tracks during sync.

Multiple sources are allowed, and Cat Group must match the group name exactly.

Things To Be Aware Of

Existing items aren’t linked automatically. If the same Track or Release was created separately in both clients, the two entries aren’t connected.
May create a duplicate if the target item has different identifiers.
Deleting is not synced. Deleting an item in the source client doesn’t delete it in the target client. If you need to remove it from both, delete it in each client separately.
Catalogue Identifiers must be unique. If a Catalogue item in the target client already uses the same Identifier (ISRCs and Alternative ID for Tracks, Cat No/Barcode per Distribution Channel, and Aliases for Releases), the sync would simply fail, and the error shows on the source item's edit page.
Edits made in the target to synced fields are overwritten by the next save in the source. Aliases are merged, not replaced, so removing one in the source doesn't remove it in the target.
Contracts and royalty data are not copied when syncing Catalogue.