--- title: "HSM migration considerations" slug: "a3s-pg-hsm-migration-considerations-4-0" updated: 2026-11-11T09:44:50Z published: 2026-11-11T09:44:50Z canonical: "docs.onespan.com/a3s-pg-hsm-migration-considerations-4-0" --- > ## 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. # HSM migration considerations Changing HSM environments after the initial deployment is relatively uncommon, but there are situations where an upgrade or migration becomes necessary. Reasons include scaling an existing deployment, replacing legacy hardware, or migrating from one HSM vendor to another, or between different models within the same HSM product family. Since the exact migration procedure and associated considerations depend heavily on the specific deployment architecture and the way Authentication Suite Server SDK is integrated into the environment, detailed step-by-step instructions are beyond the scope of this documentation. This article provides a high-level overview of the key factors and considerations involved in various upgrade and migration scenarios to help you assess the potential effort, identify possible challenges, and plan your migration or upgrade strategy accordingly. ## Things to consider before migration - BLOB migration across different HSM vendors is **not supported**. However, migrating BLOBs between HSM models of the same vendor is possible, for example, from ProtectServer External (PSEx) to Luna or from nShield XC to nShield 5. - Key management is vendor-specific. For **Thales** HSMs, key migration is performed using the native **Key Management Utility (KMU)**. For **Entrust nShield** HSMs, Authentication Suite Server SDK includes the **Key Management Tool** (manager-xc and manager-5) to facilitate key management and migration. Within the same HSM vendor ecosystem, key migration follows the same general export/import process regardless of the source and target models. Depending on the platform, this process is performed using either the native KMU or the manager-xc/manager-5 utilities. - Because storage keys are typically configured as non-exportable, migrating keys between environments requires the creation of an intermediate storage key that is explicitly marked as exportable and importable. This is used as a temporary key during the export/import process. - To make existing BLOB data usable in the new environment, it must be bound to the exportable/importable storage key using the `AAL2GenMigrateBlobCmd`/`AAL2ProcMigrateBlobRpl` APIs at least once. For additional security, we recommend to bind the BLOB data a second time to a non-exportable storage key in the new environment after the migration has been completed. - HSM migrations often incorporate **security improvements**, such as enabling **FIPS-compliant** operating modes. As a result, legacy cryptographic algorithms such as 2DES and 3DES may no longer be supported. Before migrating, verify that all existing BLOB data is compatible with the target HSM configuration, particularly when migrating to environments with stricter security requirements. The compatibility between HSM-level BLOB storage keys and authenticator applications varies depending on whether you use an [Entrust nShield HSM](https://docs.onespan.com/secsdks/docs/a3s-kmg-nshield-hsm-level-blob-storage-key-4-0#compatibility-of-hsmlevel-blob-storage-key-with-authenticator-application) or a [Thales HSM](https://docs.onespan.com/secsdks/docs/a3s-kmg-ps-hsm-level-blob-storage-key-4-0#compatibility-of-hsmlevel-blob-storage-key-with-authenticator-application).