How to move an encrypted seedless Electrum wallet to Bitcoin Core

By CoinAINews Staff

September 6, 2026

Moving Bitcoin from an older Electrum wallet to Bitcoin Core can be confusing, particularly when the Electrum wallet is encrypted and does not have a recovery seed.

In that situation, the migration is not simply a matter of copying the Electrum wallet file into Bitcoin Core. The two applications use different wallet formats and modern Bitcoin Core uses a descriptor-based wallet architecture.

For a seedless Electrum wallet containing imported private keys, the important question is how to transfer or recreate control of those Bitcoin addresses in Bitcoin Core without exposing the private keys.

There is also an important version difference. Older Bitcoin Core releases supported the legacy importprivkey RPC, while current Bitcoin Core 30.x no longer supports legacy wallets and the legacy-only import commands. Modern installations therefore require a different approach.

What Is a Seedless Electrum Wallet?

Electrum wallets can use deterministic seeds, but an Electrum wallet can also contain imported private keys.

When a wallet consists of imported keys and has no seed that can reproduce those keys, it is commonly described as a seedless or imported-key wallet.

This distinction matters during migration. A seed phrase cannot recreate private keys that were independently imported into an Electrum wallet.

In that case, the relevant private keys themselves—or another compatible representation of their key and script information—are needed to reproduce control of the addresses in another wallet.

Electrum's documentation provides command-line functionality for identifying funded addresses and obtaining their private keys. The exact commands can vary with the Electrum version being used.

Do Not Copy the Electrum Wallet File Into Bitcoin Core

Electrum and Bitcoin Core use different wallet storage formats.

Copying an Electrum wallet file into a Bitcoin Core wallet directory does not convert the file into a Bitcoin Core wallet.

The safer way to think about the process is as a wallet migration, rather than a file-format conversion.

You either transfer the relevant key information into a compatible Bitcoin Core wallet configuration or send the Bitcoin from the old addresses to a new address generated by Bitcoin Core.

Back Up the Electrum Wallet First

Before exporting or changing anything, make a secure backup of the original Electrum wallet.

Do not delete the original wallet simply because the private keys have been exported. Keep the backup until the new Bitcoin Core wallet has been independently verified.

An encrypted wallet password protects the wallet data, but it should not be confused with the Bitcoin private keys. Anyone who obtains an unencrypted private key can potentially spend the Bitcoin controlled by that key.

For that reason, never paste real private keys into websites, online converters, public forums, screenshots or other services that do not need access to them.

Identify the Bitcoin Addresses You Need to Migrate

If the Electrum wallet contains multiple imported keys, first determine which addresses actually contain Bitcoin.

There is little reason to migrate unused addresses unless you specifically want to preserve them for historical or organizational reasons.

Electrum's command-line documentation includes commands for listing funded addresses and retrieving their private keys. For example:

electrum listaddresses --funded

Electrum also documents workflows involving getprivatekeys for obtaining the private keys associated with addresses.

Because command syntax can change between Electrum releases, users should check the documentation corresponding to the version they have installed before running wallet commands.

Export the Private Keys Carefully

For an imported-key wallet, the private key is the critical piece of information that gives spending authority over the associated Bitcoin address.

Export only the keys you actually need and keep them protected while performing the migration.

A private key should be treated like cash. If another person or an untrusted application obtains it, the associated Bitcoin can potentially be spent without your permission.

It is therefore a bad idea to use an online “private key converter” or paste a real key into an online tool simply to make it compatible with another wallet.

Check Your Bitcoin Core Version

This is one of the most important parts of the migration.

Older Bitcoin Core versions supported legacy wallets. In those versions, the importprivkey RPC could be used to import a private key into a legacy wallet.

Bitcoin Core's documentation for older releases describes importprivkey as a legacy-wallet RPC and directs descriptor-wallet users toward importdescriptors instead.

That old workflow should not be copied blindly into a current Bitcoin Core installation.

Bitcoin Core 30.0 removed legacy wallet support and removed legacy-only RPCs including importprivkey, importwallet, dumpprivkey and importmulti.

How Modern Bitcoin Core Handles Wallet Imports

Modern Bitcoin Core uses output descriptors to describe the scripts and keys that belong to a wallet.

Instead of simply placing an isolated private key into an old-style key store, the descriptor tells Bitcoin Core how the relevant key material is used to create and recognize Bitcoin scripts.

Bitcoin Core provides the importdescriptors RPC for importing descriptors into descriptor wallets.

However, an imported-key Electrum wallet does not necessarily provide a ready-made descriptor that can simply be copied into Bitcoin Core. The appropriate descriptor depends on the address type and the way the private key is used.

This is why users migrating an older Electrum wallet should identify the exact address and script type before constructing or importing descriptor information.

Why the Bitcoin Address Type Matters

Bitcoin uses several different address and script formats.

An older wallet may contain legacy P2PKH addresses that commonly begin with 1. P2SH addresses commonly begin with 3, while native SegWit addresses commonly use bc1q. Taproot addresses use the bc1p format.

The private key alone does not always tell Bitcoin Core which script type you want the wallet to monitor.

For example, using the correct key with an incorrect script or descriptor can cause Bitcoin Core to watch the wrong output type and fail to display the expected balance.

Address type should therefore be verified before attempting a descriptor-based migration.

What Happened to importprivkey?

The command still appears in many older Bitcoin wallet tutorials, which is why users can encounter conflicting instructions online.

In an older compatible Bitcoin Core release, the historical command looked like this:

importprivkey "PRIVATE_KEY"

That command belongs to the legacy wallet workflow.

It is not a universal command for current Bitcoin Core. Bitcoin Core 30.0 removed legacy wallet support and the associated legacy-only RPCs.

Therefore, a guide written for an older version of Bitcoin Core can be technically correct for that version while being completely unsuitable for a current installation.

Modern Bitcoin Core: Descriptor-Based Migration

For a current Bitcoin Core installation, the migration should be planned around descriptors rather than the old legacy import commands.

The general process is:

Back up the original Electrum wallet.
Identify the funded Electrum addresses.
Determine the script/address type used by each address.
Securely obtain the corresponding private-key information.
Construct the appropriate descriptor for the key and script type when a descriptor-based import is appropriate.
Create or use a descriptor wallet in Bitcoin Core.
Import the descriptor using the supported Bitcoin Core wallet tools.
Allow Bitcoin Core to scan the blockchain for relevant transactions.
Verify the address, transaction history and balance.

The exact descriptor syntax depends on the address type and key structure. Users should not blindly substitute a private key into a descriptor without understanding the script being described.

An Alternative: Send the Bitcoin to a New Bitcoin Core Address

In many cases, the simplest migration is not to import the old private keys at all.

Instead, create a new address in a fresh Bitcoin Core wallet and send the Bitcoin from Electrum to that address.

This creates a normal Bitcoin transaction and transfers the coins to a new output controlled by Bitcoin Core.

Once the transaction receives sufficient confirmation, the old Electrum keys are no longer required to control those newly transferred coins.

This approach can be easier to understand because the old wallet and new wallet remain completely separate.

Importing vs. Sending to a New Wallet

Method	What Happens	Main Consideration
Descriptor import	Bitcoin Core gains knowledge of the existing wallet scripts and keys	Requires the correct descriptor and script type
Legacy private-key import	Older Bitcoin Core could add the key to a legacy wallet	Not available in current Bitcoin Core 30.x
Send to new address	Bitcoin moves to a fresh Bitcoin Core address	Requires an on-chain transaction and network fee
Watch-only setup	Bitcoin Core can monitor addresses without spending authority	Private keys are still needed to spend

Why Sending to a Fresh Address Can Be Cleaner

If the purpose of the migration is to retire an old wallet, sending the Bitcoin to a newly generated Bitcoin Core address is often easier to verify.

The old Electrum wallet controls the original output, while the new Bitcoin Core wallet controls the new output after the transaction confirms.

This avoids maintaining imported legacy keys in the new wallet.

The disadvantage is that an on-chain transaction is required and therefore a transaction fee may apply.

It also creates a new publicly visible transaction linking the old and new addresses through blockchain data. Moving the Bitcoin does not erase the historical transaction record of the old address.

What Does Encryption Change?

An encrypted Electrum wallet can still be migrated if its owner can unlock the wallet and access the necessary key information.

The encryption password protects the wallet's stored data. It is not a replacement for the underlying Bitcoin private keys.

Bitcoin Core will also have its own wallet encryption and security mechanisms. Encryption from Electrum does not automatically transfer to Bitcoin Core.

After creating the Bitcoin Core wallet, users should configure its security separately and protect the wallet data and credentials appropriately.

Blockchain Rescanning Matters

When wallet information is imported, Bitcoin Core needs to identify the relevant historical transactions and unspent outputs.

Older Bitcoin Core import procedures could trigger a blockchain rescan. Descriptor imports can also involve scanning for transactions matching the imported descriptors.

A wallet may therefore temporarily show an incomplete or zero balance while synchronization or scanning is still in progress.

Users should wait for the relevant process to finish before concluding that the migration failed.

How to Verify the Migration

Never delete the original Electrum wallet immediately after completing the migration.

First verify that Bitcoin Core recognizes the expected address or descriptor.

Then check:

The expected Bitcoin address.
The transaction history.
The expected unspent balance.
Whether the wallet has spending capability rather than being watch-only.
Whether Bitcoin Core is fully synchronized with the Bitcoin network.

If the migration involves a transfer to a new address, verify the transaction on the Bitcoin blockchain and wait for the expected confirmations.

Only after the destination wallet has been independently verified should the old wallet be considered for retirement.

Common Mistakes to Avoid

Copying the Electrum wallet file into Bitcoin Core: The two wallet formats are different.
Using an old tutorial without checking the Bitcoin Core version: Commands available years ago may no longer exist.
Using importprivkey on Bitcoin Core 30.x: This is a legacy-wallet RPC that was removed with legacy wallet support.
Using the wrong descriptor: The descriptor must match the relevant Bitcoin script and address type.
Assuming a seed can recreate imported keys: A seedless imported-key wallet may require the actual private keys.
Deleting the original wallet too soon: Keep a secure backup until the migration is verified.
Exposing private keys: Never paste real private keys into websites, forums, screenshots or untrusted software.

Frequently Asked Questions

Can I directly import an Electrum wallet file into Bitcoin Core?

No. Electrum and Bitcoin Core use different wallet formats. The migration requires transferring compatible key or descriptor information, or sending the Bitcoin to a new Bitcoin Core address.

Can I use importprivkey in the latest Bitcoin Core?

No. The legacy importprivkey RPC was removed along with legacy wallet support in Bitcoin Core 30.0. Modern Bitcoin Core uses descriptor-based wallets.

Can an encrypted Electrum wallet be migrated?

Yes. If you can unlock the wallet and access the required private keys or compatible key information, the wallet's Bitcoin can be migrated using an appropriate workflow.

What if my Electrum wallet has no seed?

If the wallet contains independently imported private keys, the seed cannot necessarily recreate those keys. The relevant private keys or compatible wallet information must be preserved.

Is sending Bitcoin to a new Bitcoin Core address easier?

For many users, yes. It creates a clean on-chain transfer to a fresh Bitcoin Core address and avoids importing the old wallet's keys. The trade-off is the transaction fee and the public blockchain record of the transfer.

Does importing a private key move the Bitcoin?

No. Importing key information does not move coins on the blockchain. It gives the destination wallet the ability to recognize and potentially spend the Bitcoin associated with the relevant address. An actual transaction is required to move the coins to another address.

Why does Bitcoin Core show no balance after an import?

The wallet may still need to scan the blockchain, or the imported descriptor may not match the actual script type. Synchronization and the exact wallet configuration should be checked before assuming the funds are missing.

Bottom Line

Moving an encrypted seedless Electrum wallet to Bitcoin Core is not a simple wallet-file conversion.

The correct procedure depends heavily on the type of keys in the Electrum wallet and the version of Bitcoin Core being used.

For older Bitcoin Core releases, importprivkey was part of the legacy-wallet workflow. Current Bitcoin Core 30.x has removed legacy wallets and their legacy-only RPCs, so that old method should not be followed on a modern installation.

For current Bitcoin Core, descriptor-based wallet management is the relevant architecture. However, the descriptor must accurately represent the original Bitcoin script and address type.

For users who simply want to move their funds into a new Bitcoin Core wallet, creating a fresh Bitcoin Core address and sending the Bitcoin there can be a straightforward alternative.

Whatever method is chosen, the most important security rule remains the same: protect the original Electrum backup and never expose real private keys to untrusted websites or people.

Sources

Security note: The commands and examples in this article are provided for educational purposes. Wallet software and RPC behavior can change between versions. Always verify the documentation for the exact Electrum and Bitcoin Core versions being used, and never disclose a real private key or wallet password.

How to Move an Encrypted Seedless Electrum Wallet to Bitcoin Core