A user has accumulated cryptocurrency across accounts and transaction history on an older Trezor device. The hardware has served reliably, but a newer model offers better durability, faster processors, or additional features. The practical question is how to migrate to the new device without losing account structure, re-entering the recovery seed manually, or repeating months of transaction data entry. The answer depends on understanding what Trezor Suite tracks on the device itself, what it stores locally, and what can be safely transferred between hardware versions.
The upgrade path is not simply “plug in the new device and start over.” Trezor Suite maintains a clear separation: the hardware wallet stores cryptographic keys and signs transactions, while the software interface manages accounts, displays balances, and coordinates communication with the blockchain. That architecture makes migration straightforward in principle but requires careful execution in practice. The recovery seed itself never leaves the device, yet the account derivation paths, label history, and transaction records depend on how the software is configured and where it retrieves its data.
Why the recovery seed is sufficient but not the complete upgrade story
The Trezor recovery seed is a 12- or 24-word phrase that generates all private keys for a given device. When a user initializes a new Trezor device with the same seed, it derives the same private keys and therefore can sign transactions on the same accounts. This is the foundation of the upgrade process: the new device and old device become cryptographically equivalent.
However, having identical private keys does not automatically restore the visible wallet state. Trezor Suite stores metadata separately from the keys themselves. That metadata includes account labels (such as “Savings” or “Trading”), hidden accounts, custom Bitcoin node settings, Tor preferences, and the complete transaction history for each account. None of this information is stored on the recovery seed. If a user restores only the seed to a new device and connects it to Trezor Suite, the software will recognize the same addresses and balances, but account names and custom settings will be lost unless they are preserved or re-created.
Additionally, the derivation path used to generate accounts matters. Standard Trezor accounts follow BIP44 conventions for Bitcoin, Ethereum, and other assets, meaning the same seed will produce the same addresses on the same network. Non-standard paths or custom account structures, if they were created through advanced settings or a previous wallet migration, may require additional configuration to be recognized correctly. The recovery seed is therefore the irreplaceable core; the metadata and configuration are the details that make the upgrade seamless.
A user upgrading from an older Trezor One to a newer Trezor Model T or Safe, or between newer models, faces the same basic workflow: initialize the new device with the old recovery seed, restore the software configuration, verify that accounts appear with the correct balances, and then retire the old device. The process should take minutes if the necessary backups exist beforehand, or hours if backups are absent and account structures must be manually reconstructed.
Preparing for the upgrade: backup steps before the old device leaves your hands
The most critical preparation happens while the old device is still in use and all accounts are visible. Before disconnecting it, a user should export account metadata in a format that Trezor Suite recognizes. The software provides an export function under account settings that generates a file containing labels, hidden-account flags, and metadata for each connected account. This file should be saved in a secure location on the computer running Trezor Suite, because it will be imported into the software after the new device is connected.
Users should also document any custom settings they have configured. These include: Bitcoin backend preferences (if they have specified a custom node), Tor settings, passphrases used with specific accounts (if applicable), and any accounts that are intentionally hidden rather than displayed by default. Trezor Suite’s coin control settings and custom fee structures are transaction-level configurations that do not need separate export, because they are applied when a payment is created rather than stored permanently.
If the old device is being replaced due to damage or loss of physical access, this preparation step is impossible. In that case, the user must rely on the recovery seed alone, re-create account labels and settings from memory or documentation, and accept a temporary loss of transaction history visibility until the Trezor wallet backup is restored or the account metadata is manually re-entered. This is why regular backups matter: they compress what would otherwise be a tedious manual process into a single file import.
A Trezor wallet backup is distinct from a recovery seed backup. The seed is the cryptographic foundation and should be written down and stored offline, separate from any electronic device. The wallet backup is the software-level state file that Trezor Suite can save and restore. While not a substitute for the seed, it preserves the convenience details that make daily wallet use efficient.
Initializing the new device with the existing recovery seed
When the new Trezor device arrives, the initialization process begins by choosing the option to “Restore from Recovery Seed” rather than creating a new wallet. This is the critical divergence: restoring from seed means the new device will generate the same addresses and accounts as the old one, preserving the ability to sign transactions on existing balances. Creating a new seed would result in a completely separate wallet with no connection to existing funds.
During the restore process, the user enters the recovery seed word by word. Trezor devices mitigate the risk of this exposure by offering word-selection screens that require only confirming the correct word from a limited set, rather than typing the entire phrase. This reduces the risk of keyboard logging or accidental network exposure, but it still requires that the user have the seed written down, accessible, and be in a location where entering it is reasonably private.
Once the seed is entered and verified, the device will request a PIN setup if one was not already configured. The PIN protects access to the device itself, though it does not encrypt the recovery seed. If the old device had a non-empty passphrase configured, the new device should be set up with the same PIN structure to match the old device’s user experience; however, passphrases themselves are entered differently and should be prepared before initializing accounts.
After the device initializes, it should display the Trezor Suite connection interface. At this point, the device has the same private keys as the old one but no account history or labels in the software. The new device can now access the same cryptocurrency addresses and balances as the old device. Trezor Suite will recognize Bitcoin accounts, Ethereum accounts, and other supported blockchains based on the standard derivation paths.
Restoring account metadata and transaction history
The metadata export file created from the old device can now be imported into Trezor Suite on the new device. The import function is typically found under Settings or in the account management panel, and selecting the backup file will restore account labels, hidden-account settings, and other non-cryptographic state. This is where the earlier preparation step becomes invaluable: a few seconds of file selection can restore hours or days of manual labeling work.
Transaction history is handled differently. Trezor Suite retrieves transaction records from blockchain data sources—public nodes, block explorers, or custom backends—rather than storing them within the device itself. When the new device is connected to Trezor Suite, the software queries the blockchain for all transactions associated with the restored addresses and re-populates the transaction history. This happens automatically in the background, though depending on the number of accounts and the age of the wallet, it may take minutes to hours to fully synchronize.
During synchronization, users may notice that balances and transaction counts are initially incomplete or that some accounts load before others. This is normal. Trezor Suite prioritizes the standard accounts (Bitcoin account 1, Ethereum account 1, etc.) and then discovers additional accounts on demand. If the old device had many custom accounts or accounts on less common blockchains, the synchronization may require explicit navigation to those accounts to trigger the data retrieval.
If the old device used a custom Bitcoin backend—such as a private full node, an Electrum server, or a specific block explorer—that configuration must be re-entered in Trezor Suite on the new device. Account balances will still be correct, but if the custom backend is not restored, the software may switch to the default public backend, potentially changing the data source and latency characteristics. Users who value privacy or have strong preferences about node selection should document their backend settings before retiring the old device and re-apply them immediately after the new device is initialized.
Verifying the migration before retiring the old device
Before the old device is set aside or destroyed, several verification steps should be performed. First, compare the account list and balances on both devices. Open Trezor Suite with the old device connected, note the total balance and the structure of accounts, then switch to the new device and confirm the values match. Discrepancies usually indicate incomplete synchronization or a mismatch in backend settings, not a cryptographic problem.
Second, test a small transaction from the new device to confirm that it can sign and broadcast payments correctly. This should be a low-stakes movement, such as sending a small amount to a known personal address. The purpose is to verify that Trezor Suite recognizes the new device, that the signing interaction works as expected, and that the blockchain accepts the transaction. A successful test transaction confirms that the private keys have been correctly derived and the device is operational.
Third, verify that any passphrase-protected accounts are accessible. If the old device had accounts created with a passphrase (a feature that allows multiple independent wallets from a single seed), the new device must have the same passphrases entered correctly to derive the same accounts. This is a manual step because passphrases are not stored on the device; they are combined with the seed during key derivation. If a passphrase is forgotten, the account is cryptographically inaccessible, even with the recovery seed.
Fourth, confirm that hidden accounts have been restored correctly. Trezor Suite supports marking accounts as “hidden,” which prevents them from appearing in the default account list. If this feature was used on the old device and the metadata export was successful, hidden accounts should re-appear as hidden on the new device. If they appear as visible, the import may have been incomplete, and they should be hidden again manually.
Handling the old device after a successful migration
Once the new device has been verified and all accounts and balances are confirmed, the old device can be safely retired. There is no need to erase it; simply storing it in a safe location or physically destroying it is sufficient. The old device cannot pose a security risk to the new device because they derive from the same seed: if the old device were compromised, the attacker would have access to the same addresses and keys as the new device anyway.
However, do not re-initialize the old device with a new recovery seed unless you are certain you no longer need to access any accounts associated with the original seed. Initializing with a new seed will overwrite the old cryptographic material and make the previous accounts inaccessible from that device, though the blockchain records and the accounts themselves remain intact and accessible from the new device.
For maximum security, consider securely erasing the metadata export file after the import is complete. The export file contains account labels and settings but not the recovery seed or private keys. If this file is lost, the only consequence is that account labels and settings would need to be manually re-created; the funds themselves are protected by the recovery seed and remain accessible. Treat the metadata file as convenient but not critical, unlike the recovery seed, which is irreplaceable.
If the old device was a Trezor One and the new device is a Model T, Safe, or other newer variant, the upgrade also offers an opportunity to review and update security practices. Newer Trezor devices may offer improved firmware, faster signing, additional supported blockchains, or enhanced durability. Take advantage of the migration moment to review whether Trezor Suite download from the official source is current, whether firmware on the new device is fully updated, and whether the backup strategy for the recovery seed still meets your needs.
Troubleshooting common migration issues
If the new device shows different balances than the old device after restoration, the most common cause is incomplete blockchain synchronization or a backend mismatch. Wait for Trezor Suite to fully sync with the blockchain, which may take several minutes to an hour depending on the number of accounts. If balances remain different after synchronization, check whether the custom Bitcoin backend or other node settings from the old device have been restored. If they have not, restore them and allow the software to re-synchronize.
If account labels are missing after metadata import, the export file may not have been imported correctly or may be incompatible with the version of Trezor Suite running on the new computer. Verify that the backup file exists and is readable, and check the Trezor Suite version on both the old and new installation. If the software versions differ significantly, consider updating to a current version before attempting import again. Manual re-labeling is the fallback option and is less time-consuming than it may initially appear.
If a passphrase-protected account is not visible on the new device, verify that the passphrase has been entered correctly in Trezor Suite’s settings. Passphrases are case-sensitive and must be entered exactly as they were on the old device. If the passphrase is uncertain, and no records exist of its exact form, the account is cryptographically inaccessible without the correct passphrase, even with the recovery seed. This is by design, to protect accounts that may be isolated or hidden.
If the new device fails to initialize with the recovery seed, verify that each word is spelled correctly and selected from the official Trezor word list. Some similar-sounding words can cause confusion during manual entry. If the device rejects the seed after multiple attempts, ensure that the correct number of words (12 or 24) is being entered and that no extra spaces or typos are present. If the device still rejects the seed, verify that the seed itself is correct by checking it against the written record.
Migration best practices for long-term wallet management
The upgrade process demonstrates the value of maintaining organized backups and documentation. Create a simple record that includes: the number of words in your recovery seed (12 or 24), the date the seed was created, the list of blockchain networks your wallet actively uses, and any custom account structures or passphrases (without writing the passphrases themselves). This information, stored separately from the seed itself, can substantially reduce migration time if you need to upgrade or recover your wallet in the future, to see below for additional official resources on device configuration and recovery.
Consider performing a test migration on a non-critical device or in a controlled environment before upgrading your primary wallet. If you have access to an older Trezor device that is no longer in active use, restoring it with a test seed (not your real seed) can familiarize you with the initialization and metadata import process, reducing the risk of procedural errors when you perform the migration with real funds.
Set a reminder to periodically verify that your recovery seed and backup files are still accessible and readable. Store the recovery seed in at least two physically separate secure locations, and store a copy of the metadata export file in a secondary location as well. This redundancy protects against the loss of a single backup location due to theft, fire, or other physical damage. Annual verification ensures that the backups remain intact and that you have not forgotten the storage locations or the methods needed to access them.
Finally, keep Trezor Suite updated to the current version. Software updates often include improved blockchain compatibility, performance enhancements, and security patches. Updating before performing an upgrade ensures that the migration process runs smoothly and that the new device benefits from the latest features and protections. Updates do not affect the recovery seed or private keys; they only improve the software interface and its interaction with the blockchain.
Frequently asked questions
Do I need to re-enter my recovery seed when upgrading to a new Trezor device?
Yes, you must enter the recovery seed into the new device during initialization to restore access to the same accounts and private keys. However, you should choose the “Restore from Recovery Seed” option rather than creating a new wallet. The seed itself never leaves the device; it is used only to generate the private keys needed to access your existing accounts.
Will my account labels and transaction history transfer automatically to the new device?
Account labels and metadata can be transferred if you export them from the old device and import them into Trezor Suite on the new device. Transaction history is retrieved from the blockchain automatically as Trezor Suite synchronizes with the network, so it will appear without manual action, though this may take several minutes to an hour depending on the size of your wallet.
Is it safe to keep the old device after I upgrade to a new one?
Yes, keeping the old device is safe because it derives from the same recovery seed as the new one. If the old device is compromised, an attacker has no more access than they would from the new device. You can store it as a backup or securely destroy it. Do not re-initialize it with a new seed unless you have permanently abandoned the original accounts.