--- title: "App configurations" slug: "dpo-export-and-import-app-configurations" updated: 2026-10-27T20:13:31Z published: 2026-10-27T20:13:31Z canonical: "docs.onespan.com/dpo-export-and-import-app-configurations" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # App configurations To copy a client app's configuration from a source tenant to a destination tenant, export the app's configuration from the source tenant, and then import it into the destination tenant. You can export and then import one or more configured apps, and you can optionally include any of the app's dependencies. ## Exporting #### Using the Admin Console 1. Login to the Admin Console and, if needed, switch to the source tenant. This is the tenant that already has the app configured. Navigate to **Configuration > Apps**. 2. The **Apps** page appears. - To export all apps, click **Export All**. - To export a specific app, locate the app in the table and, in the same row, click the Export icon in the **Actions** column. 3. The **Export App** dialog appears. ![](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/Screenshot 2026-03-04 at 3.28.00 PM.png?sv=2026-02-06&spr=https&st=2026-10-29T02%3A04%3A53Z&se=2026-10-29T03%3A04%3A53Z&sr=c&sp=r&sig=yHT%2FA78SlYeTC2F7iU6egBXDmgjhKYXeg0NMnB2OZko%3D) If you assign a default Adaptive Ruleset to an app, that Adaptive Ruleset has dependencies that need to be exported. Those dependencies include FIDO policies, authenticator groups, country lists, device model lists, geofence lists, IP address lists, and WiFi network lists. Check **With dependencies** to export these objects. You can optionally **Include authenticator metadata** to export authenticator metadata. This option is only valid if you checked **With dependencies**. Use this option in limited situations, such as when you intend to use authenticator metadata that was only in a development deployment in a production deployment. Remember, authenticator metadata is accessible to all tenants in an DigipassONE installation. Normally, you should use the instructions in [Update Authenticator Metadata](/dpoa/docs/s3suite94-update-authenticator-metadata-1) to import metadata. 1. Click **Export**. - If you are exporting one or more apps without dependencies or authenticator metadata, the Admin Console saves the app(s) in a JSON file. - If you are exporting app(s) with their dependencies, the Admin Console saves all the objects in a ZIP file. #### Using nnl-mgmt.sh The syntax below shows how to export the configuration for the app with from into a file. If no is specified, the app is exported from the default tenant. The or specifies where the system stores the app's configuration. ```plaintext ./nnl-mgmt.sh app export -name [-dir | -file ] [-with-dependencies -include-metadata -tenantid ] ``` For more information, see [*App Commands*](/dpoa/docs/s3suite94-app-commands-1) in the reference to *Command Line Interface*. ## Importing #### Using the Admin Console 1. Login to the Admin Console and, if needed, switch to tenant2. This is the tenant into which you want to import the app configurations. Navigate to **Configuration > Apps**. 2. On the Apps page, click the **Import…** button. 3. The **Import Apps** dialog appears. ![](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/Screenshot 2026-03-04 at 3.28.54 PM.png?sv=2026-02-06&spr=https&st=2026-10-29T02%3A04%3A53Z&se=2026-10-29T03%3A04%3A53Z&sr=c&sp=r&sig=yHT%2FA78SlYeTC2F7iU6egBXDmgjhKYXeg0NMnB2OZko%3D) 4. To overwrite apps in the current tenant that have the same package name, check **Overwrite any existing app with the same package name**. Note that if your zip file contains dependent objects, this option also overwrites any dependent objects with the same name. Check **Import and overwrite metadata as well from zip file** to import authenticator metadata from zip file. Use this option in limited situations, such as when you intend to use authenticator metadata that was only in a development deployment in a production deployment. Authenticator metadata is accessible to all tenants in an DigipassONE installation. Normally, you should use the instructions in [Update Authenticator Metadata](/dpoa/docs/s3suite94-update-authenticator-metadata-1) to import metadata. 5. Choose the json or zip file that contains the app configuration and click **Import**. By default the file size can be up to 512 KB. To change the maximum file size for an app configuration file, refer to [Admin Tenant Properties](/dpoa/docs/s3suite94-authentication-server-properties-1#admin-tenant-properties)*.* #### Using nnl-mgmt.sh The syntax below shows how to import an app's configuration file into . If no is specified, the default tenant is used. ```plaintext ./nnl-mgmt.sh import -file [-overwrite -include-metadata -tenantid ] ``` For more information, refer to [App Commands](/dpoa/docs/s3suite94-app-commands-1). Formerly known as Digipass S3.