Confirm the recovery first
Verify that the recovered wallet reproduces expected historical addresses using the correct wallet family and derivation settings. Preserve the original files and record the tools and versions used. A green success message alone is not enough evidence to retire the old backups.
Choose a current destination carefully
Use the replacement wallet’s official documentation and distribution channel. Verify the download using the method that project provides. Avoid using an advertisement, a private support message or an old blog download as the sole authority for software handling recovery material. The MultiBit repository’s retirement notice recommends moving away from the discontinued software.
Keep observation separate from spending
Checking addresses, reviewing history and preparing a migration are distinct from signing or broadcasting a transaction. Make the destination and fee decisions consciously. This website never performs either action. A migration checklist should document the destination’s provenance, backup method and verification process before any funds are moved.
Retain the historical evidence
Keep the old wallet folder, backup inventory and recovery notes after migration. Historical addresses can still matter for bookkeeping or later incoming payments. Store recovery secrets separately from a shareable incident report. A public write-up should contain methodology and redacted examples, not live wallet material.
What this guide does not claim
We have not tested every modern wallet, every MultiBit release or every hardware configuration. There is no single import instruction that covers all of them. Use the source-backed wallet-types guide to identify the case, then consult the destination project’s current documentation before attempting an actual migration.