Move a project to another account

You can hand a project to your personal account or to an organization where you manage listening. Nothing moves until two emails are answered: you confirm the request, then an owner or admin of the receiving account accepts it.

Before you start

• You need the right to delete the project (listening.manage on the account that owns it).
• Moving a project out of an organization is limited to its owners and admins.
• The receiving account must be one where you have listening.manage, and its plan must have room for one more project and for the project's sources.
• A project can have only one open transfer at a time.

Move the project

1. Open the project's Settings tab and go to Danger zone → Move to another account.
2. Choose an account: your Personal account or an Organization. Accounts without room on their plan say why.
3. Review what Goes with it, what Stays here and what is Removed.
4. Type the project name to confirm and click Request the move.
5. Check your email and open the confirmation link within 1 hour.
6. The owners and admins of the receiving account receive an email with the project name, who asked, the number of sources and mentions, and what moves. One of them accepts within 7 days.
7. The project moves when they accept. Both accounts are notified.

While a transfer waits, the project settings show it with Resend email (a new link; the old one stops working) and Cancel the transfer. The receiving account can also decline; you get an email when it does.

What moves

Data	On transfer
Sources, mentions and images, metric history, creators, campaigns, alerts, attributes, reports	Go with the project
Guests the project is shared with	Go with the project
Report schedules	Go with the project but are paused until the new account checks their recipients
Project roles of the old account's members	Removed
Webhooks and Google Sheets connections of the old account for this project	Removed
Past collection runs and their datasets, creator lists, access settings	Stay with the old account

After the move, collections run, are billed and use the data source keys of the new account.

Transfer statuses

Status	Meaning
awaiting_confirmation	Waiting for you to confirm by email (1 hour)
awaiting_acceptance	Waiting for the receiving account to accept (7 days)
completed	The project has moved
declined	The receiving account turned it down
cancelled	Withdrawn before it completed
expired	A link ran out
failed	Refused at acceptance, for example because the plan had no room any more or a collection was running

With the API

Endpoint	Purpose
GET /listening/projects/{project}/transfer	Accounts the project can move to, with room on their plan, and any open transfer
POST /listening/projects/{project}/transfer	Request the move: account_id. Answers 202 with the transfer
GET /listening/transfers/{transfer}	One transfer
POST /listening/transfers/{transfer}/confirm	Step 1, by the requester, with the emailed token
POST /listening/transfers/{transfer}/accept	Step 2, by an owner or admin of the receiving account, with the emailed token
POST /listening/transfers/{transfer}/decline	Turn it down, with the emailed token
POST /listening/transfers/{transfer}/cancel	Withdraw a waiting transfer
POST /listening/transfers/{transfer}/resend	Send the current step's email again (once a minute)

A second request while one is open answers 409 with the code transfer_pending. An expired link answers 410 (transfer_expired).