Transferring apps between accounts

At a glance: Sender and receiver admins agree to transfer apps between AppsFlyer accounts that have a status of Active.

5638-Transfering-an-app-NEW1.gif

Transfer types

Full self-service app transfer: The sender and receiver admins independently (without AppsFlyer involvement) complete an app transfer from one account to another.

Assisted self-service app transfer: The sender admin successfully submits an app transfer request. However, due to financial, commercial, or legal issues, the transfer needs the assistance of an AppsFlyer Customer Success Manager (CSM) or Customer Engagement Manager (CEM).

Intro.JPG

Prerequisites

image__12_.pngReview these sections before submitting an app transfer request.

Permissions

Only the account admin can submit or accept an app transfer request.

  • Sender admin must have the receiver's email address; it must be valid and listed in the AppsFlyer system. 
  • Sender admin starts and submits an app transfer request.
  • Receiver admin agrees to accept transferred apps.
  • Both admins can choose to cancel an app transfer request. See Cancel a request

Apps and accounts

Apps must belong to accounts with ZeroGrowth, or Enterprise plans. This capability is not available during the account Welcome stage.

One or more apps can be transferred between 2 accounts as follows:

  • From a primary account to 1 of its subaccounts and vice versa.
  • From 1 subaccount to another subaccount within the same primary account.
  • Between 2 primary accounts.

Full self-service app transfers

The sender and receiver admins independently (without AppsFlyer involvement) complete a full self-service app transfer—from one account type to another—per these criteria:

  • Apps belong to accounts with ZeroGrowth, or Enterprise plans; this capability is not available during the account Welcome stage.
  • Plans have Active status.
  • Neither account has outstanding invoices.
  • App/s status is Available or Pending.
  • App/s selected for transfer comprise less than 30% of an account's traffic over the last 90 days.

Assisted self-service app transfers

The sender admin successfully submits an app transfer request. A popup indicates the request was created and that a CSM or CEM will contact them soon.

Assisted self-service app transfers occur due to these circumstances:

  • Accounts have ZeroGrowth, or Enterprise plans, but there are financial, commercial, or legal issues with one or both accounts. Example: One or both are suspended or pending suspension due to overdue invoices.
  • App/s selected for transfer comprise more than 30% of an account's traffic over the last 90 days.

Legal terms and conditions

The sender and receiver must each acknowledge terms and conditions relating to the app transfer.

Sender and receiver

Both the sender and receiver must review and accept terms and conditions that appear in the user interface.

Upon acceptance, they are emailed a copy of the legal text and the status of the app transfer is updated as follows:

  • On both the sender and receiver's My apps pages.
  • In an email sent to both the sender and receiver admins. 

App transfer checklists

The sender and receiver should review and act on the listed best practices before starting an app transfer.

Sender

Review the implications table and its related best practices. Ensure necessary app-related actions are handled before the transfer is finalized.

Important information

Topic Transfer status Sender best practices
App settings Transferred

Did the Receiver ask you to transfer app settings?

  • If not, remove the Firebase/GCM server key.
Integrated partners

Transferred: Integration, cost, and revenue configurations

 

Not transferred: Ad network and agency integration permissions

Did the Receiver ask you to transfer integrated partners?

  • If not, deactivate them and delete their configurations and credentials, including cost and ad revenue configurations.
Link management

Not transferred

  • App is removed, but the link remains.
Delete obsolete link configurations.
OneLink

Not transferred

  • OneLink continues to work as-is.

Do you want to transfer a OneLink?

  • Then, stop the transfer process and contact your CSM or Support.
Push API Transferred

Did the Receiver ask you to transfer your Push API configurations?

  • If not, delete them or your data may continue to flow to an endpoint not owned by the Receiver.
Smart Banners

Not transferred

  • App is removed, but the creative remains.

Check if related creatives are needed.

  • If not, delete them.

 Related information 

Topic Transfer status
Agencies

Not transferred

  • Agencies lose access to the app.
Audiences

Not transferred

  • Deleted from the sender account.
Cost ingestion

Not transferred

  • Cost-ingestion files remain but aren't accessible.
Data Locker

Not transferred

  • App is removed from the Data Locker configuration.
  • Sender account stops getting app data.
Historical data

Transferred

Live alerts

Not transferred

  • App is removed, but the alert template remains.
PBA brand bundles

Not transferred

  • A bundle is no longer available if any of its related apps are transferred.
Protect360 data Transferred
Raw & aggregate data Transferred
SDK dev key Transferred
Validation rules Transferred

Receiver

Review the implications table. Ensure necessary actions are handled before the transfer is finalized.

 Important information

Topic Transfer status Receiver best practices
App settings Transferred

Check for the Firebase/GCM server key.

  • If unneeded, delete it.
Integrated partners

Transferred: Integration, cost, and revenue configurations

 

Not transferred: Ad network and agency integration permissions

Did you receive unneeded activated integrated partners?

  • If so, delete their configurations and credentials, including cost and ad revenue configurations.
Push API Transferred

Did you receive unneeded Push API configurations?

  • If so, be sure to delete them or the third-party sender may receive user-level data.
Validation rules Transferred Check that the transferred validation rules are configured to your needs.

 Related information 

Topic Transfer status
Agencies

Not transferred

  • Agencies lose access to the app.
  • Necessary to configure all agencies (former and new) that need access to the app.
Audiences

Not transferred

  • Deleted from the sender account.
Cost ingestion

Not transferred

  • Cost-ingestion files remain but aren't accessible.
Data Locker

Not transferred

  • App is removed from the Data Locker configuration.
  • Sender account stops getting app data.
Historical data

 

Transferred

  • Historical data is fully retained and accessible even if the SDK dev key is reset.
Link management

Not transferred

  • App is removed, but the link remains.
Live alerts

Not transferred

  • App is removed, but the alert template remains.
OneLink

Not transferred

  • OneLink continues to work as is.
PBA brand bundles

Not transferred

  • A bundle is no longer available if any of its related apps are transferred.
Protect360 data Transferred
Raw & aggregated data Transferred
SDK dev key  Transferred
  • Account- or app-specific SDK dev key must be set in the SDK of all new apps to enable attribution.
  • Keep the existing dev key or reset it to your account’s dev key.
  • If an app has an active user base, it is recommended to keep the original dev key. If reset, new data will only be collected for new app installs (those that have the new dev key set in the app's code).
Smart Banners

Not transferred

  • App is removed, but the creative remains.

Submit or cancel a request

To make a full self-service transfer of 1 or more apps to another AppsFlyer account, simply start the process and you will be guided, step-to-step, through the wizard feature. 

Sender procedures

  1. To transfer 1 app: 
    Go to My apps > Available apps > Open app action menu (...) > Select Transfer app.

    To transfer 2 or more apps: 
    Go to My apps > Open page action menu (...) > Select Transfer apps.

  2. Read and act on relevant recommendations in the best practice's table.
  3. Choose the app or apps to transfer. 
  4. Enter the receiver-admin's email address.
  5. Read and sign the terms and conditions.
  6. Sender and receiver are notified (email) when the request is submitted successfully.
    Sender is notified (popup) if the request requires CSM/CEM handling.
  7. App/s appear on your My apps page as Pending transfer to <receiver email>. At this stage, it is still possible to delete the request.
    App_transfer_sender_side.JPG

Receiver procedures

  1. On the My apps page, click Review request; a request can include 1 or more apps.
    App_transfer_receiver_side.JPG
  2. Review and approve a given request; at this stage, it is possible to reject the request.
  3. Read and act on relevant recommendations in the best practice's table.
  4. Read and sign the terms and conditions.
  5. Sender and receiver are notified (email) that the request is accepted.
  6. App/s appear on your My apps page.   

Cancel a request

An app transfer process can be canceled by either the sender or the receiver. This can be done at any time before the transfer is finalized.

Sender

The sender can cancel or delete an app transfer as follows:

  • To cancel: Simply exit the app transfer wizard.
  • To delete: Go to My apps > Pending transfer to [email] section > Click Delete request.
    Both the sender and receiver admins are notified (email).

Receiver

The receiver can reject an app transfer as follows.

  • To reject: Go to My apps > Apps pending transfer section > Click Reject.
    Both the sender and receiver admins are notified (email).
Was this article helpful?