
Moving from a single-key wallet to SSP: a careful migration plan
If your coins sit in a wallet controlled by one recovery phrase, moving them to SSP means moving them to new addresses that need two devices to spend. Like any move of money, it goes best slowly: set up first, test small, then move the rest in batches.
Why you send funds instead of importing your old seed
Can you just type your existing recovery phrase into SSP? Technically, SSP Wallet's restore screen will accept a phrase from another wallet. A standard BIP-39 phrase is taken as it is, and a phrase with non-English words or a failing checksum is accepted only after a warning and an explicit confirmation, as long as it has 12, 15, 18, 21 or 24 words.
But restoring does not turn your old wallet into a multisig. SSP Wallet derives its keys on a BIP-48 multisig path, and every address it shows is built from two public keys: one from SSP Wallet and one from SSP Key. For Bitcoin and the other UTXO coins that is a 2-of-2 script; on EVM chains it is a smart account controlled by both keys. None of those addresses is the address your old wallet used, so your existing balance won't appear. The coins stay where they are, still spendable by the old phrase alone.
There is also a security reason not to reuse it. An old phrase has already lived in another app, maybe on another device or in a screenshot. Making it one half of your new setup carries that history along. A fresh setup gives you two new phrases that have never been anywhere else. So the clean path is: create a new SSP wallet, then send your funds to it.
Step 1: set up and back up both devices first
Install SSP Wallet in your browser and SSP Key on your phone, create a new wallet on each, and pair them. Setting up your first SSP wallet covers each screen. By default both apps generate a 24-word phrase, and SSP Wallet won't continue until you confirm you have backed it up.
You now have two recovery phrases, and you need to keep both. A 2-of-2 address can't be spent with one key, so losing one phrase together with the device that holds it can lock funds. Write each down, store them in separate places, and check each backup before any meaningful amount arrives. Testing your backup explains how to do that without exposing the phrase.
Step 2: test with a small amount on every chain
Don't assume that because one chain worked, the others will. For each chain you plan to move:
- Copy the receive address from SSP for that exact chain. On EVM networks, SSP uses a distinct address per chain, so the Ethereum address is not your Polygon address.
- Send a small amount from the old wallet.
- Wait until it shows in SSP and on a block explorer.
- Send a small amount out of SSP, approving on both devices. That is the real test: it proves you can spend, not just receive.
Step 3: move the rest in batches
Once each test round trip works, move the remaining balance in a few transfers rather than one. A batch that goes wrong costs less, and you check the address on every send.
Things to watch along the way:
- Fees and minimums. Every send pays a network fee, and very small UTXO amounts can fall below a chain's dust limit. Leaving a tiny remainder behind in the old wallet is often cheaper than chasing it.
- Tokens need the native coin for gas. To send USDC on Ethereum from your old wallet, that wallet needs some ETH. Move tokens first and the native coin last, or you'll strand tokens with nothing to pay for their transfer. The same applies inside SSP: EVM vaults pay gas in the chain's native coin, and on Solana the fee is reimbursed from the vault in SOL. Coins vs tokens explains why.
- Network match. Send each asset on the chain the SSP address belongs to. A token on Base goes to your SSP Base address, not to the Ethereum one.
Step 4: decide what happens to the old wallet
When the balance is moved, the old wallet still exists. A few loose ends:
- Approvals. Token approvals you granted from the old address stay on-chain. They only matter while that address holds tokens, but if you plan to keep using it, revoke the ones you no longer need. Revoking token approvals from SSP explains how approvals work and what revoking does.
- Dust. Small leftovers can be ignored, or swept once a fee makes sense.
- Keep or retire the old phrase. Payments, refunds or airdrops can still arrive at old addresses for months. Many people keep the old phrase safely stored for a while and check those addresses now and then.
Step 5: update addresses everywhere you receive funds
The last step is the one people skip. Update your new SSP addresses with exchanges you withdraw to, employers or clients who pay you, mining pools, payment processors and anyone who saved your old address as a contact. Use the right chain for each.
The honest summary
You can type an old phrase into SSP Wallet, but it won't bring your old addresses or balance with it: SSP's addresses are 2-of-2 multisig built from both devices' keys, and a reused phrase carries its history with it. The careful route is a fresh setup with two tested backups, a small round trip on every chain, then batched transfers with enough native coin left for gas. Afterwards, tidy up approvals, decide what to do with the old phrase, and update every place that sends you funds. The result is a wallet where no single device or phrase can move your coins.


