Meta App Ownership Transfer: Moving an App to a New Business Portfolio Without Breaking Access (2026)
A client handover, an acquisition, a move from a freelancer's developer account into the company's own portfolio — they all end at the same screen, and there is no transfer button on it. A Meta app can be linked to only one business portfolio at a time. The current owner has to let go before anyone else can take hold, and everything gated on the old portfolio goes quiet in the gap.
There is not one transfer flow — there are three
Most of the confusion in a handover comes from people doing the wrong one of these and assuming the job is done. Meta's own developer documentation describes three separate scenarios with three different menu paths.
New individual admin
App Dashboard → App roles → Roles. This changes who administers the app. It does not change which business portfolio owns it. This is the step most often mistaken for a completed transfer.
Claim into a managed account
App settings → Basic → Business portfolio ownership. This sends an asset claim request to the destination portfolio's Requests inbox. Meta states plainly that once the request is approved, the action cannot be undone.
Move to a different business
Remove first, re-attach second. Newer Use Case apps do this under Review → Verification; older App Type apps under App settings → Basic → Verification. Same outcome, different screens.
The UI itself is unstable
Meta's documentation gives at least three menu locations for what looks like one action, and the Help Center describes the re-attach as a claim by the receiving business while the developer docs describe it as a selection made by the app admin. Any screenshot-driven tutorial is wrong for somebody.
Who has to be in the room, and in what order
- Check the destination portfolio before you touch anythingMeta states that if the Business Manager claiming the app is not connected to a verified business, the app will not be able to use permissions that require business verification. Verifying this first is the single cheapest thing anyone can do, and it is almost always skipped.
- Line up both sets of administratorsDetaching requires an Administrator role on the app and an Administrator role on the original business. Only business admins can add or remove apps at all. If either side is a single unavailable person, the handover stops there.
- Detach from the current portfolioThrough Business Settings → Accounts → Apps, or from the App Dashboard verification panel, depending on which generation of app you have. The app is now owned by nobody.
- Attach to the new portfolioDocumented two ways — the receiving business claims it, or the app admin selects the destination from a popup. Which one appears depends on the app type and where you started from.
- Rebuild everything that was tied to the old portfolioVerification state, Tech Provider status, system users, assets. This is the step nobody budgets for, and it is where the real timeline lives.
What the handover actually breaks
The move itself takes minutes. The consequences are the project. Each of these is documented by Meta, not inferred.
| What is affected | What Meta documents |
|---|---|
| Tech Provider / Access Verification status | A business stops being treated as a verified Tech Provider when the app becomes disconnected from the business that created or claimed it. Until the new portfolio clears verification, other businesses cannot use your app at all. |
| Business-verification-gated permissions | Apps requesting advanced access, and apps that let other businesses reach their own data, must be connected to a business that has completed Business Verification. Until then, app users from other businesses cannot grant those permissions and the features stay inactive. |
| System users and their tokens | Meta requires the system user and the app to belong to the same portfolio, and states that apps can only target businesses that have claimed them. System users stay behind in the old portfolio; new ones have to be created and the app reinstalled on the new side. |
| WhatsApp Business Account | A hard stop, in Meta's own words: a WABA must belong to only one Business Manager, and you cannot migrate a WABA from one business to another. The WhatsApp side is a separate plan, not a side effect. |
| The error you will actually see | Meta documents the symptom as error code 100 — object does not exist, cannot be loaded due to missing permissions, or does not support this operation. It reads like a bug in your integration. It is an ownership problem. |
Where handovers stall
- The receiving portfolio has not completed Business Verification, and nobody checked before the app was detached.
- The receiving portfolio is restricted — Access Verification requires that there be no restrictions on the business account.
- Only one side has an available admin, so the detach or the claim waits on a person, not a process.
- The app was built under a personal developer account with no portfolio behind it, so there is nothing to transfer and the client is expecting a handover that does not exist in that shape.
- WhatsApp numbers were assumed to travel with the app. They do not.
- Live integrations keep calling the API with system user tokens issued by the old portfolio.
- Someone approves the managed-account claim request before realising Meta treats that approval as irreversible.
What Meta does not publish — and what that means for the advice you read
- Whether existing App Review approvals or Advanced Access grants survive an ownership change. There is no official statement in either direction. Any article that promises they carry over — or insists you must redo everything — is guessing.
- Any downtime window for the gap between removal and claim.
- Whether app roles, ad account links, Pages, catalogs or pixels move with the app. Assets are claimed separately, per asset type.
- Any end-to-end turnaround time. The only figures Meta prints anywhere nearby are roughly five days for an Access Verification decision, and a 60-day window for existing businesses to complete verification. Numbers beyond those were invented by whoever wrote them down.
Why this is more than a settings change
An app handover looks administrative and behaves like a migration. The order of operations matters, the verification state of the receiving portfolio matters more, and the pieces that refuse to move — WhatsApp accounts, system users, Tech Provider status — decide whether the client wakes up to a working integration or an outage they will blame on you. Getting the sequence right, confirming the destination is actually able to hold the app before anything is detached, and rebuilding the verification and access layer on the new side is the work — and it is the part that is difficult to undo if it goes wrong.
If you are handing an app to a client, taking one over from an agency, or moving your own app into a properly verified portfolio, that sequencing and the verification work behind it is what I do.