Migrating app versions between environments
If your organization uses more than one AI Hub environment, you can migrate a published app version from the source environment to a target environment.
App migration copies the selected app version package and its metadata to the target. The source app version stays unchanged. Linked automation projects, ground truth datasets, deployments, and workspace settings aren’t migrated.
App migration requires admin permissions.
What migration does and doesn’t include
Migration includes:
- The selected source app version package
- App version metadata you provide or confirm, such as name, description, icon, version number, release notes, and AI runtime update settings
Migration doesn’t include:
- Changing or deleting the source app version (it remains in the source environment)
- The source automation project and its editable project configuration
- A linked project on the target, unless you choose Migrate to an existing project
- Ground truth datasets
- Deployments, integrations, or human review settings
Migrating an app version
Ensure the App portability feature is enabled in both the source and target environments.
Generate a credential in the target environment
Migration requires an API credential issued from the target environment. This token must belong to an account with admin permissions; tokens for non-admin accounts fail target validation.
-
Sign in to the target environment as an organization admin.
-
On the target environment, create an API credential to use during migration.
-
AI Hub token — In the target environment, open Settings > APIs, then create a token for an admin account. Copy the token value before you close the dialog.
-
OAuth provider token — If your organization uses an external OAuth provider for API access, request an access token from that provider for an admin-mapped account on the target environment. Paste the access token, not the OAuth client secret.
-
Migrate an app version from the source environment
-
In the source environment, open the Hub, then the app to migrate.
-
Select the Versions tab.
-
For the app version to migrate, click the overflow icon (More actions), then select Migrate to another environment.
-
In the Migrate app dialog, complete information about the target environment.
-
In Target environment URL, enter the full target AI Hub URL. For example,
https://target-environment.instabase.com. -
In Token type, select AI Hub token or OAuth provider token.
-
Enter the Token value (for an AI Hub token) or Access token (for an OAuth provider token).
-
Click Fetch organization. Verify the target organization details.
-
Click Next.
-
-
On the App info tab, select an App migration type.
-
Migrate as a new app — Creates a new app in the target environment. Enter the App name, App description, and App icon. Migrating as a new app doesn’t create a linked project on the target.
-
Migrate to an existing app — Adds a new version to an existing app in the target environment. Enter the App ID in target environment, then click Fetch data. Confirm the resolved Target app name.
You can find an app ID in the app URL, such as https://aihub.instabase.com/hub/apps/528c36e8-ac5b-490d-a41b-7eec9c404b87. -
Migrate to an existing project — Enter the Project ID in target environment, then click Fetch data. Confirm the resolved Target app name. Use this option when you want the migrated version linked to that project on the target.
You can find a project ID in the project URL, such as https://aihub.instabase.com/build/528c36e8-ac5b-490d-a41b-7eec9c404b87.
Advanced apps have additional restrictions: you can’t migrate an advanced app onto a standard (non-advanced) app, and Migrate to an existing project isn’t available. In that case, migrate as a new app or onto an existing advanced app. -
-
Click Next.
-
Complete Version info:
-
Version — If you’re updating an existing target app, select Major, Minor, or Patch. If you’re creating a new app on the target, enter a semantic version such as
0.0.1. -
AI runtime updates — Select whether the app adopts the latest AI runtime version automatically as soon as it’s released, or when the current version expires, which allows time for testing and manual deployment.
-
Release notes — Describe what changed in this app version.
Migrated apps use private visibility. Manage access through the app’s sharing settings after migration. For more details, see Sharing apps.
-
-
Click Migrate. Migration can take some time, a Migration complete alert indicates success.
If migration fails, you see Migration failed. Click Try again to restart the process. A failed migration doesn’t leave orphaned files or a partial app on the target.
After a successful migration, the app on the target behaves like any other newly created app or newly published app version. You can filter for migrated apps in the Hub using the Migrated filter. Continue your usual workflow there:
-
Review sharing and visibility for the migrated app.
-
Run accuracy tests or manual app runs in the target environment. Recreate ground truth datasets on the target if you need them.
-
Create or update deployments that use the migrated app version.
-
For linked development and production deployments in the same environment, continue using deployment promotion. App migration is for moving app versions across separate AI Hub environments.
