Import Tokens from Another Deployment
You can import tokens that were exported from another deployment. Custom token attributes will not be imported with the token data. Standard token attributes are imported.Software token profiles are not imported. The association between the profile and the token is imported if theexact same profiles exist on the source and target deployments.For information on how importing tokens affects software token profile association, see Exporting and Importing Users and Tokens Between Deployments. Duplicate tokens that are not assigned in the source deployment are not imported to the target deployment.
This topic describes how to import tokens that were exported from a different deployment. To import a new token record file, see Import a Token Record File.
Before you begin
Export the tokens from the source deployment. See Export Tokens.
RSA recommends that you create a new security domain on the target deployment for the tokens being imported. This makes it easier to isolate the new data and to verify its accuracy. After you are satisfied that the import is correct, you can move this data to another suitable security domain.
Procedure
In the Security Console of the target deployment, click Administration > Export/Import Tokens and Users > Import Tokens and Users.
In the Import Job Name field, specify the name of the import job.
Select the import file location.
Click Next.
On the Security Domain Selection page, select the target security domain for the imported tokens. You can only select one security domain.
Click Next.
On the Pre-Import Summary page, review the import operation details for accuracy.
Click Import. You are directed to the Export/Import Status page. The status of the import is automatically refreshed.
When the import is complete, the tokens are in the security domain that you selected in an unassigned state.
Run a report to view the results of the import job. Use the Imported Users and Tokens Report template. For more information, see Reports.
Note: In the Imported Users and Tokens Report template, in the Job Name field, RSA recommends that you do not select a name of the import job in the template. Only select the name of the import job when you run the report. If you select a name of the import job in the template, every report you run will have the same name.
Related Articles
How to import tokens into Authentication Manager 8.x 133Number of Views Exports and Imports Tokens and Users Between Deployments 17Number of Views Delete Export and Import Tokens and Users Jobs 39Number of Views Token import job fails with an error and 0 tokens imported in RSA Authentication Manager 341Number of Views Exporting and Importing Users and Tokens Between Deployments 249Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x