Transfers
Step 1. Open the transfers list
The goal of this stage is to review the history of ad node transfers and find the transfer you need, or prepare to create a new one.
- Navigate to the Transfers page.
- The table shows completed and ongoing transfers: ID, ad node name, team, operation ID, type, and status.
- If needed, filter the list by status, type, team, or parent MCC using the filters at the top of the page.
A transfer is a structural change to the hierarchy: moving an ad node (MCC, Sub-MCC, or account) under a different node. A transfer can be made both from one root (parent) MCC to another and within the same root MCC.
Step 2. Create a transfer
The goal of this stage is to move the selected ad node from its source location to the target location.
- Click the Create transfer button in the top-right corner of the page.
- The Create transfer modal opens with two sections — source and destination.
- In the Transfer from source MCC section, specify what is being moved:
- Parent MCC — the root manager account the node is moved from;
- Sub-MCC — a child manager account, if you're moving it or a node under it;
- Account — an ad account, if that's what's being moved.
- In the Transfer to target MCC section, specify where the node goes:
- Parent MCC — the target root manager account;
- Sub-MCC — the target child manager account, if the node is moved under it.
- Click Create.
Step 3. Verify the transfer status
The goal of this stage is to ensure the transfer was processed successfully by the system and that the hierarchy has been updated.
- After creation, the transfer appears in the table with its status, and the Transfer details open so you can track the transfer process.
- If the status is Manual action required, the transfer can't be completed automatically: a corresponding task appears in Operator tasks, where it must be completed manually.
- You can track the related operation by the Operation ID in the transfer row or on the Operations page.
- After a successful transfer, you can verify the updated hierarchy on the Actual tree page: the node appears under its new parent.