Account administrators with full-management permissions, and some other admin types with sufficient permissions, can transfer ownership of applications to users in other accounts. In most cases, this means transferring applications to a different realm. This article covers how to transfer apps to a different account and ensure the app continues to work as expected after the transfer.
Requirements
Permission requirements
To transfer applications to a different account, you must have at least one of the following permission types:
Account admins with at least full-management permissions
Account admins with support-level permissions who are also application manager or application admins in the app being transferred
Application managers in the app being transferred
Other requirements
The user you transfer ownership to must have permission to create applications in the destination account.
To complete the transfer, the user whom you are transferring the application to must accept the transfer.
The account the app is coming from and the account the app is going to should have identical configuration. Plan level, entitlements, and available features should match. If they are not the same, there may be discrepancies in app functionality.
Make sure you understand the impact of moving the app to a different realm. Several parts of the app may need to be reconfigured, and it is useful to make notes before transferring the app so you know how to get the app working again after the transfer. See the Reconfigure apps in the new realm section of this article for a list of areas to check before making the transfer.
Restrictions on transferring apps to a different account
Applications that are owned by a trial account or an account that is suspended cannot be transferred to a different account. In these cases, you can submit a request to Quickbase Technical Support to transfer application ownership.
Apps created in paid accounts cannot be transferred to builder accounts. However apps in builder accounts can be transferred to any paid account. To do so, submit a request to Quickbase Technical Support.
How to transfer apps to a different account
Transfer Quickbase apps either through the Admin Console or application settings.
Transfer through the Admin Console
Select Apps.
Select the name of the application you want to transfer.
Select Transfer App.
On certain service plans, you may need to select the change link to the right of the app manager's name instead.Enter the user name or email address of the Quickbase user to whom you want to transfer the application in the text box, then select Next.
Note: The Quickbase user must have app create permissions in at least one account.Verify that the user name or email address you entered is correct, then select Next.
Select Authorize Transfer to transfer the application, and send an alert to the user to whom you are transferring the application.
No application transfer is complete until the user to whom you are transferring the application acts on the alert and accepts the transfer. When the new app manager accepts the transfer, an alert email is sent to the previous app manager.
Transfer through application settings
Open the application you want to transfer.
From app home, select App settings.
Select Application management in the Advanced Features section.
Select Transfer app. It is in the Manage the App section which is the last section on the page.
Enter the username or email address of the Quickbase user to whom you want to transfer the application in the text box, then select Next.
Note: The Quickbase user must have app create permissions in at least one account.Verify that the username or email address you entered is correct, then select Next.
Select Authorize Transfer to transfer the application, and send an alert to the user to whom you are transferring the application.
No application transfer is complete until the user to whom you are transferring the application acts on the alert and accepts the transfer. When the new app manager accepts the transfer, an alert email is sent to the previous app manager.
Reconfigure apps in the new realm
In most cases, transferring apps to a different account means that they move to a different realm. Because of this, anything in the app that references the original realm should be reconfigured.
When a request is made to a valid app or table ID using an incorrect realm URL, Quickbase automatically redirects the request to the correct realm and returns an HTTP 301 Permanent Redirect response. However, it's important to still update incorrect realms wherever you find them because:
Scripts may or may not follow the re-direct
Successful redirects may be rate-limited to protect the Quickbase platform
The following table includes all areas to check to make sure your app is reconfigured and works correctly in the new realm:
Area to check | Redirect behavior | Action to take |
Pipelines | Redirects are not supported | Pipelines exist at the realm level. When an app moves to a different realm, any pipelines set up in the original realm no longer work.
Tip: Make notes about how pipelines and any other automations are set up, especially triggers and actions, before you transfer the app. The YAML converter app from the Exchange can help you transfer pipelines into the new realm without the need to manually recreate pipelines from scratch. |
Connected tables | Redirects are not supported | When an app with a connected table is transferred to a different realm, the connection used by the connected table remains with the app’s original realm, since it may have been used by other connected tables in the original realm. In the app’s new realm:
Note: If the connected table is connecting to a realm that has cross-realm security configured, you may need to confirm that the connected table’s new realm has been included in its list of allowed realms. When an app that is the source for a connected table is transferred to a different realm, update the Quickbase URL of the existing connection to match the source app’s new realm URL. To do so, go to connection settings from the connections list in your user profile. Note: If the realm the connected table is located in has cross-realm security configured, you may need to confirm that the app’s new realm has been included in the list of allowed realms. |
External scripts | External scripts that call the Quickbase XML API redirect to the new realm URL if they respect HTTP 301 redirects. Scripts that call the REST API will not redirect. |
|
Code pages | Code pages redirect in most browsers, though exceptions may occur. | Manually update code pages that contain Javascript, HTML, etc. that reference the URL. |
URL formulas | URL formulas containing the | If you have URL formulas that use the original URL as a literal, manually update them. |
Authentication | N/A | Authenticate using the new realm’s policies. For example, if your app is moved to a realm that uses SSO, you’ll need to sign in with SSO to access it. |
Bookmarks and other saved links | Bookmarks and saved links redirect in most browsers, though exceptions may occur. |
|
FastField | Redirects are not supported for the Quickbase integration. | A realm admin must open a technical support ticket to update the Quickbase realm URL in FastField. |
Actions (retirement announced) | Actions may automatically redirect to the new realm URL, but this functionality is not maintained | Actions call specific URLs, which include the realm’s URL. Manually edit actions to adjust to the correct URL. |
Webhooks (retirement announced) | Webhooks may automatically redirect to the new realm URL, but this functionality is not maintained | Webhooks call specific URLs, which include the realm’s URL. Edit webhooks to use the new realm URL. |
Automations (retirement announced) | Redirects are not supported. | Automations must be converted to pipelines. |
Features that have reached end of life cannot be recreated using the new realm URL.
Contact technical support for any specific concerns.