Transfer ownership
Transfer ownership of an organization to another member, or move a single app to a different organization. Two different actions with different mechanics — pick the one that fits your scenario.
Apphud has two different "transfer ownership" actions with completely different mechanics. Pick the one that matches what you want to do.
Two different "transfer ownership" actionsTransfer organization ownership — the Owner role of the whole organization moves to another existing member. The org's apps, team, billing, and integrations stay put. Instant, no acceptance required.
Transfer an app to another organization — a single app moves out of one organization into a different one. The source org loses the app and its data; the destination org gains it. Requires acceptance from the destination org's Owner and expires automatically.
Comparison at a glance
| Aspect | Transfer organization ownership | Transfer an app to another organization |
|---|---|---|
| Who initiates | The current Org Owner | The current App Owner |
| What moves | The Owner role within the same org | The app and all its data into a different org |
| Where to do it | Team and permissions → member ⋯ → Transfer ownership | App settings → General → Danger zone → Transfer ownership |
| Prerequisite | Target member must already be an Administrator | Receiving org must be identifiable by its Organization ID; receiving org needs an active paid plan if the app uses paid features |
| Recipient confirmation | None — instant | Required — recipient's Org Owner approves or declines |
| Notifications | None | In-app notification + email (app_transfer_requested to sender, app_transfer_invitation to recipient) |
| TTL / expiration | None (instant action) | 1 hour auto-expire if not accepted |
| Revoke | N/A (no pending state) | Yes — sender can revoke while pending |
| Previous Owner's role after | Auto-demoted to Administrator (stays in org) | Loses access to the app entirely; team members in the source org also lose access |
| Apps affected | None — all apps stay in the org | One app moves; other apps in source org untouched |
Transfer organization ownership
Use this when the Owner role of the whole organization should pass to another existing member — for example, when the current Owner is leaving the company and another team member should take over.
Before you start
- The new Owner must already be an Administrator of the organization. If they aren't, promote them first in Team and permissions (edit team member → change role to Administrator).
- Only the current Org Owner can perform the transfer.
Steps
- Open the profile menu → Team and permissions.
- Find the target Administrator in the list.
- Click the ⋯ menu on their row → Transfer ownership (red action).
- In the confirmation modal — "Once you transfer organization ownership, you will no longer be able to transfer or delete apps, and your role will be downgraded to admin. Are you sure you want to continue?" — click Transfer ownership.
What happens
- The target member's role becomes Owner immediately.
- Your role is automatically downgraded to Administrator (you're not removed from the org).
- All apps, billing, integrations, team membership, and historical data stay in the organization unchanged.
- No notification is sent to anyone — the swap is silent.
- There is no pending state and no expiration — the role transfer is instant.
If the new Owner wants to remove you from the org afterward, they can do so from Team and permissions like any other member.
Transfer an app to another organization
Use this when one of your apps should belong to a different Apphud organization — for example, when selling an app, splitting a portfolio, or moving an app to a client's org.
Before you start
- You must be the Org Owner of the source org.
- The receiving org must already exist — if the recipient doesn't have an org in Apphud, they need to create one first and share its Organization ID.
- If your app uses paid features (Predictions, Win Back Refunds, etc.), the receiving org needs an active paid plan. Without one, the transfer is blocked.
- Delete any sensitive integration credentials before transferring — all integrations and their credentials move with the app. To protect them, disconnect what you don't want exposed to the receiving org.
Steps
- Open the app you want to transfer.
- Go to App settings → General → scroll to Danger zone.
- Click Transfer ownership (red outlined button) to open the App transfer modal.
- Read the Important notes in the modal (rendered below verbatim — they're part of the legal flow).
- Enter the receiving org's Organization identifier in the input field (example:
acme_apps). - Toggle I have read and understood the important notes ON.
- Click Send request.

App transfer modal — important notes
These appear in the modal exactly as worded:
- All existing integrations and their credentials will be transferred to the new organization. To protect your credentials, please delete any connections before transferring the app.
- Apps that use paid features cannot be transferred until the receiving organization has an active paid plan.
- You can revoke a transfer request anytime before it's accepted.
- After the transfer is completed, only the new organization's owner will be able to transfer the app again.
- Transfer requests expire automatically if not accepted within 1 hour.
After you send the request
- You see a App transfer in progress modal: "App will be transferred to the new organization when the request is accepted by the new organization owner. You can still revoke the request if not accepted yet."
- On the General page, the Transfer ownership button area is replaced with a "Transfer request: pending" line and a Revoke button.
- The receiving org's Owner gets an in-app notification (inbox) plus an email (
app_transfer_invitation):- Body: "{sender-company} initiated an app transfer request to move {app-name} to {recipient-company}."
- Buttons: Approve / Decline.
- If the recipient takes no action within 1 hour, the request expires automatically and the app stays in the source org.
What happens after the recipient approves
- The app and all its data move to the receiving org.
- Both Org Owners get a confirmation notification: "{app-name} has been successfully transferred from {sender-company} to {recipient-company}."
- The app appears in the receiving org's app list with its configuration, integrations + credentials, products, paywalls, audiences, and analytics history.
- Team members in the source org lose access to the app — they would need to be re-invited from the receiving org's Team and permissions if they should keep access.
- You can no longer manage the app. Only the new Owner can initiate another transfer of this app.
What happens after the recipient declines
- You get a notification: "{recipient-company} declined the transfer request for {app-name}."
- The app stays in your org untouched. No data is changed.
Revoking a pending transfer
While the request is pending (within the 1-hour window), open the General page on the app, find the "Transfer request: pending" line, and click Revoke. The request is invalidated immediately and the recipient's pending notification is removed.
FAQ
Which transfer do I need?
If the whole organization should belong to someone else — transfer the organization ownership. If only one specific app should belong to a different organization — transfer the app.
Can I transfer an app to a personal account?
The transfer destination is always an organization, not a user. If the recipient is an individual, they need to create their own organization first; then share the Organization ID with you to use in the transfer modal.
Can I transfer many apps at once?
No. App transfer is per-app — there's no bulk action. If you have many apps to move, send the requests one at a time. Each transfer also has its own 1-hour acceptance window per request.
What happens to team members in the source org when an app is transferred?
They lose access to that app — it's no longer part of their org. They keep access to any other apps that stay in the source org. If they should also have access in the new org, the new Owner needs to invite them.
Why does the new Owner have to accept an app transfer but not an organization-ownership transfer?
App transfer crosses an organization boundary — the receiving org's Owner needs to consent to taking on the app, its data, and any billing implications. Organization-ownership transfer happens within the same org among existing members, where the new Owner is already a trusted Administrator — so no second consent is needed.
My app uses Predictions / Win Back Refunds. Why is the transfer blocked?
Apps that use paid features can't be transferred to an org without an active paid plan — Apphud needs to know the receiving side can support the app's existing paid features. The recipient should upgrade their plan first, then you can re-send the request.
How long do I have to wait for the recipient to accept?
1 hour. If they don't approve or decline within that window, the request expires and you'll need to send a new one.
Can I undo an organization ownership transfer?
No, not directly. The swap is instant and there's no undo. If you handed Owner to the wrong person, the new Owner (you can't initiate again — you're now Admin) needs to transfer it back to you.
Updated 27 days ago
