How to Transfer Meta Ad Account Ownership Between Business Portfolios

What Meta lets you transfer and what it does not

Decision first:

• Already owned by another business portfolio: distinguish shared partner access from ownership. Sharing leaves the account in its existing portfolio; check the options Meta actually offers before planning a change.
• Not yet owned by a business portfolio: an eligible admin can claim it once into the intended long-term portfolio.
• Nobody trusted has full control of the owning portfolio: use Meta's official support or control-recovery route; Meta controls eligibility and outcome.

Meta gives businesses three ways to bring an ad account into a business portfolio in Meta Business Suite: create a new ad account, claim an existing ad account (which moves it into your portfolio), or request to share an ad account — where, in Meta's words, "the account will remain in their portfolio, but access will be shared with your portfolio."

Two distinctions shape the handoff:

• Claiming is one-way. Meta's Business Management API documentation describes claiming as "a one-time procedure," after which "you can only manage the ad accounts in that Business Manager."
• Sharing preserves ownership. Meta’s add-account guidance says a shared account remains in its existing portfolio. Confirm account-specific eligibility before treating any access change as an ownership move.

Related constraints:

• A business cannot remove an ad account from its own portfolio while its relationship to that account is OWNER and the status is CONFIRMED; only PENDING claims or accounts held with AGENCY access can be removed.
• Personal ad accounts with no history of activity are not eligible for migration into a business manager at all (Graph API error 3994).

What this means in practice: Do not assume that sharing transfers ownership. Meta’s add-account guidance distinguishes claiming an eligible account, requesting shared access while ownership stays where it is, and creating a new account. Check eligibility and the available actions before choosing among them. If an organization has lost control of the portfolio itself, Meta documents a request process to regain full control — but Meta publishes no timeline and no guaranteed outcome for that review.

Ownership versus partner access

Meta's asset model separates owning an ad account from accessing it.

• Ownership (OWNER). The portfolio the account belongs to. The owner's people hold the account-level tasks, and an ad account admin (MANAGE, ADVERTISE, ANALYZE) "can manage all aspects of campaigns, reporting, billing and ad account permissions."
• Partner/agency access (AGENCY). Meta defines an agency as "a type of business entity that can manage or access assets owned by another business," performing tasks on the client's behalf. The API reports which role your business plays through the access_type field on the business-to-account relationship.

Access also stacks across two levels — Meta Business Suite has full control and partial access, applying both to portfolios and to the individual assets inside them. Two rules matter whenever an account changes hands:

1. If a partner shares an asset with your organization, "you're limited to the specific permissions that your partner assigned" — which can prevent you from granting anyone full control of that asset.
2. Full control of the asset alone is not enough to manage people: "You can't edit people's permissions in Meta Business Suite if you have full control of a business asset but not the business portfolio."

This separation is why Meta's developer documentation tells agencies that "most marketing companies won't need to claim ad accounts from their clients" and should instead use business-to-business access requests. Partner access delivers operational capability — building campaigns, reading reporting, administering billing where granted — without moving ownership, and either side can end the relationship. For most agency-client engagements, that is the model Meta expects you to use.

Transferring an ad account between business portfolios

Meta documents claiming as a mechanism that changes which business owns an eligible ad account, and it is designed for accounts that live outside any business portfolio: "If you manage ad accounts outside of a Business Manager with the Admin role, you can claim them for your business."

How a claim works

1. The requester must be an admin of the claiming business. In Meta Business Suite, go to the Ad accounts section in Settings and click Add; Meta's help documentation lists "claim an existing ad account" as one of the three add options. Via API, POST the act_### ID to /<BUSINESS_ID>/owned_ad_accounts.
2. If the requester is already an admin of the ad account, Meta approves immediately and returns access_status = CONFIRMED.
3. If not, Meta sends an ownership request to the ad account's admins and the claim sits at PENDING. To accept it, an ad account admin must log in and accept the request in Ads Manager.

If the account is already inside another portfolio, the documented options narrow:

• Ask the owning business to share the account with yours (partner access) — ownership does not move.
• Create a new ad account in the correct portfolio and share it as needed. Note the platform constraints here: ad account creation via API is limited to five accounts, and all accounts in the business must be in good standing before new ones can be created.
• For structural breaks — for example, reclaiming a portfolio after losing full control — use Meta's request flow and expect a review whose timeline and outcome Meta does not document.

Because a claim is permanent, treat the destination portfolio as a one-way door: confirm the long-term home, the billing arrangement, and who will hold full control before anyone clicks claim.

What breaks when an account changes hands

Plan for these failure points before the account moves:

• Permissions management moves. Once an ad account is connected to a business portfolio, "you won't be able to edit permissions from ad account settings in Ads Manager" — everything runs through Meta Business Suite Settings.
• People access has to be rebuilt. Task assignments are granted per business-scoped user, and an ad account supports a maximum of 25 people with access. Anyone who worked on the account through the previous business needs a new assignment in the new setup.
• Billing can silently stop delivery. Without a payment method on the account, "it will still be possible to create ads but these ads will get no delivery." Confirm the funding source before assuming the transfer worked.
• Shared invoicing entities don't re-share. If the account used a partner's shared legal entity as its bill-to party, note that "you can't share the legal entity of your partner business with another business" — the new arrangement needs its own billing path, and liability still follows the owner of the line of credit.
• Structural fields are locked. Once end_advertiser — and likewise media_agency or partner — is set to a real value, it cannot be changed, so a mismatch cannot be edited away after the fact.
• Shared assets may need re-granting. Pixels and custom audiences are shared to specific ad accounts, and Meta's API includes explicit operations to dissociate an ad account from a shared pixel or a shared custom audience. Audit what the account depends on and re-share what it still needs.
• Spend caps only look forward. A newly set spend cap "only applies to spend AFTER the time at which you set it" — historical spend under the old setup does not count against it.

None of these is a reason to avoid a needed transfer, but each one can stall delivery or lock the wrong people out even when the transfer itself technically succeeds.

Sequencing a transfer without pausing spend

Meta does not document a guaranteed zero-downtime transfer, so the goal is to remove every known cause of interruption in advance. A defensible sequence:

1. Audit the current state. Confirm the account is active (API account_status = 1), and record the funding source, the people assigned and their tasks, and any shared pixels or audiences the campaigns depend on.
2. Choose the lightest mechanism. If the engagement is ongoing, sharing keeps ownership stable and is reversible; reserve claiming for accounts that genuinely need a new permanent home.
3. Stand up billing first. Add and confirm the payment method in the destination setup before changing access — remember, no payment method means no delivery.
4. Add before you remove. Assign the incoming team's people their tasks while the existing team still has access, and assign only the level of access people need: ANALYZE for reporting, ADVERTISE + ANALYZE for operators, MANAGE only where admin is required.
5. Execute the claim or share. For claims, have an ad account admin ready to accept the ownership request in Ads Manager so the account does not sit in PENDING limbo.
6. Verify delivery, then offboard. Confirm campaigns are serving before removing the previous partner. Meta's developer best practices describe the end state plainly: "the Marketing Partner can remove the ad account or page from the Marketing Partner's Business Manager to reduce liability. Alternatively the customer can revoke access."

Two sequencing traps to avoid: don't change billing mid-flight (a partner's shared legal entity bill-to cannot be transferred onward to another business), and don't assume a claim is reversible — it is a one-time procedure, so a mistake becomes a support request with an undocumented timeline.

Verifying the transfer completed

Verify from four angles before declaring the transfer done:

1. Portfolio membership. In Meta Business Suite, the account should appear in the Ad accounts section of the destination portfolio. Via API, GET /<BUSINESS_ID>/owned_ad_accounts should list it, with access_type showing OWNER (or AGENCY if the account was shared rather than moved). GET /<BUSINESS_ID>/pending_owned_ad_accounts should not list it — a lingering PENDING entry means an ad account admin still needs to accept the ownership request in Ads Manager.

2. People and permissions. GET /act_<AD_ACCOUNT_ID>/assigned_users shows who holds which tasks. Confirm the intended admins carry MANAGE, that departed staff and the former partner no longer appear, and that permission changes now happen in Business Suite — remembering that only people with full control of the portfolio, not merely the asset, can edit other people's permissions.

3. Billing. Confirm the funding source is present and, for monthly-invoicing setups, that the bill-to legal entity and invoicing emails reflect the new arrangement rather than the old partner's.

4. Delivery. Check that active campaigns are actually serving and that the account status reads active (1). Delivery is the real proof: an account can look correctly transferred while ads sit undelivered for want of a payment method.

If verification fails because nobody in your organization has full control of the portfolio, Meta's documented remedy is to submit a request to regain full control. Meta does not publish how long that review takes or what it decides, so build that uncertainty into any client-facing timeline.

Choose the next step for your handoff

For an existing agency handoff, start with the ownership and access audit and record who owns the portfolio, who has access and who pays. If you are evaluating an ongoing provider relationship, compare the Meta agency account guide for ownership, billing and permissions questions before discussing fit. A provider conversation does not guarantee account access or a platform outcome.

Keep legitimate access changes separate from enforcement. Meta prohibits trading administrative access and helping others evade enforcement; separate clients need separate ad accounts, and an established account must not be repurposed for a different advertiser. A handoff does not erase a restriction or authorize a replacement account to bypass it.