<h2>Manual Steps</h2>

<ol>
<li>Copy your public receiving addresses from Bitcoin-Qt.</li>
<li>Go to the Bitcoin-Qt console: click <code>Help/Debug Window</code> and then select the <code>Console</code> tab.</li>
<li>Run <code>walletpassphrase [your password] [timeout in seconds]</code> to unlock your password protected wallet.</li>
<li>Run <code>dumpprivkey [Receiving Bitcoin Address]</code> for each receiving address to be migrated to MultiBit. There may be hidden private change addresses in Bitcoin-Qt which don't show up in the receive tab. Run <code>listaddressgroupings</code>.</li>
<li>Copy the results of <code>dumprivkey</code> for each address (which are the corresponding private keys).</li>
<li>Start the Multibit client and create a new wallet.</li>
<li>Click <code>Tools/Export Private Key</code> after selecting the <code>Do not password protect export file</code> option.</li>
<li>Open the exported file in a text editor.</li>
<li>Below the private key generated by MultiBit, paste the private keys you have copied above. Remember to paste them before the <code>End of private keys</code> line.</li>
<li>After each private key, add a date that is prior to when you created the corresponding wallet. (You can check this date in the Bitcoin-Qt <code>Transactions</code> tab and scrolling to the very bottom.)</li>
<li>Repeat for all addresses you want to move to Multibit Client.</li>
<li>Save the key file and import it to the Multibit client using <code>Tools &gt; Import Private Keys</code>.</li>
<li>In MultiBit, you may not see your total until you click <code>Tools &gt; Reset Blockchain and Transactions</code></li>
<li>In order to protect yourself from theft, delete the private key files.</li>
<li>Done!</li>
</ol>

CC BY-SA 3.0
2013-09-14T20:29:20.717Z
Scott's answer above is excellent, but I think there are some final steps missing, which are: After step 8: 9. Save the file that you added the keys to
10. Click Tools/Import Private Key. Find the file you saved and import it.
Velonius
CC BY-SA 3.0
2013-09-22T19:45:38.517Z
By the way, this is a great answer, but besides the comment of @Velonius above, you have to make sure to put a date **prior** to the creation of your wallet when pasting the private key into `multibit.key` file. This ensures the proper replaying of the blockchain which will then pick up all the transactions.
adavid
CC BY-SA 3.0
2014-01-27T18:47:14.687Z
Also missing, if you have a password on your wallet, is before step 3 writing:  walletpassphrase [your password] [timeout in seconds]
Marcelo Mason
CC BY-SA 3.0
2014-03-15T12:24:31.000Z
My transactions were picked up, but my total did not appear in MultiBit until I did "`tools` > `reset blockchain and transactions`" at the end (after step 11).

Also, be aware that the QT-client uses hidden private change addresses that don't show up in the receive tab. `listadressgroupings` in the Qt-debug-console showed my missing addresses which I then followed steps 3-10 for to make ALL of my transactions and money appear in multibit. [Get all addresses from bitcoind](http://bitcoin.stackexchange.com/questions/9077/how-to-get-all-addresses-including-the-change-addresses-from-bitcoind)
Crashthatch
CC BY-SA 3.0
2014-03-16T05:21:40.973Z
Thanks Marcelo Delgado and Crashthatch, I updated the answer.  I hope it helps others and is easy to read.
Scott
CC BY-SA 3.0
2014-10-29T00:33:54.937Z
Simpler now: `bitcoind -daemon; bitcoin-cli dumpwallet wallet-dump.deleteme; grep label= wallet-dump.deleteme | cut -d' ' -f1,2,3 > import-into-multibit.key` -- but don't do it on insecure storage! Those contain raw private keys. I'd like to improve this by importing labels as well, but couldn't figure it out.
I answer wrong - have fun
CC BY-SA 3.0
2014-10-29T01:08:24.217Z
Oh, here's the script and a helper, I'll add more if I need it: https://github.com/timmc/app-1113
I answer wrong - have fun
CC BY-SA 3.0
2016-04-13T21:49:56.173Z
Your link is dead.
mkabatek
CC BY-SA 3.0
2016-04-14T15:47:03.207Z
Thanks, I removed the link.  I'm glad I wrote out the steps here!
Scott
CC BY-SA 3.0
2013-09-14T13:55:03.317Z
2016-04-14T15:46:34.720Z
2016-04-14T15:46:34.720Z
Scott
<p>It does not answer your question of getting your private keys out of bitcoin-qt, but this link explains how you import a single private key into MultiBit:</p>

<p><a href="http://multibit.org/help_importASingleKey.html" rel="nofollow noreferrer">http://multibit.org/help_importASingleKey.html</a></p>

<p>If you have more than one private key it is simply more rows in the import file.</p>

<p>The date alongside each key is a bit non-obvious. It has to be before the date of the first transaction using that key so that the blocks with the transactions in can be found. I recommend just finding the first transaction in your wallet and putting the date one day before it in on every row. (Using a day earlier avoids any time zone problems).</p>

<p>Note that the import only knows about the sipa format private keys (the ones beginning with a 5). It does not understand compressed keys. ( <a href="https://bitcoin.stackexchange.com/questions/3059/what-is-a-compressed-bitcoin-key">What is a compressed Bitcoin key?</a> )</p>

CC BY-SA 3.0
2012-11-11T19:33:36.933Z
Still strange to see people name the base58 private key format after me. I'd prefer them adding support for compressed public keys (which I also came up with, including the base58 format...).
Pieter Wuille
CC BY-SA 3.0
2012-11-11T19:44:49.853Z
Hi Pieter, yes I will no doubt get round to adding parsing of compressed keys - it is in my issues list. As the export files are mainly to backup the MultiBit keys it is not top of the list though. I think you will probably have to get used to being famous. :-)
jim618
CC BY-SA 3.0
2012-11-11T17:28:52.977Z
2012-11-11T17:28:52.977Z
2017-04-13T12:47:33.743Z
jim618
<p>I wrote this a while ago and used it to convert all my wallet.dat s to multibit.key to be able to import them to multibit.</p>

<p><a href="https://github.com/shayanb/Open-Wallet-Format" rel="nofollow">https://github.com/shayanb/Open-Wallet-Format</a></p>

CC BY-SA 3.0
2014-07-19T07:33:50.740Z
2014-07-19T07:33:50.740Z
Shayan
<p>Question says it. I spent 20 mins Googling. Saw several links on bitcointalk.com but amazingly found no solution to this. Am I the first one trying to do this? 
Note the following are <strong>not</strong> the solutions I am looking for:</p>

<ol>
<li>Transfer the BTC from Bitcoin-qt to Multibit by making a transaction</li>
<li>Some commandline geeky stuff</li>
</ol>

CC BY-SA 3.0
2012-11-11T21:54:57.480Z
> Some commandline geeky stuff

Well, that's the way it is done.  You could pay someone to do that process for you -- but then you would need to trust them as they have your private keys.
Stephen Gornick
CC BY-SA 3.0
2012-11-11T21:56:35.963Z
That "commandline geeky stuff" can be done through the debug window / console that is available with the Bitcoin.org client v0.7.
Stephen Gornick
CC BY-SA 3.0
2013-09-14T14:18:28.527Z
Unfortunately there are some `commandline geeky stuff` commands that you will need to execute.  Please see my answer below.
Scott
<bitcoin-core><import><multibit>
How do I import private keys from Bitcoin-qt to Multibit client?
Jus12
# How do I import private keys from Bitcoin-qt to Multibit client?

(Asked by: username_0 on 2012-11-11)

Question says it. I spent 20 mins Googling. Saw several links on bitcointalk.com but amazingly found no solution to this. Am I the first one trying to do this?
Note the following are **not** the solutions I am looking for:

1. Transfer the BTC from Bitcoin-qt to Multibit by making a transaction
2. Some commandline geeky stuff

**Tags:** bitcoin-core, import, multibit

> **Comments:**
> **username_1**: > Some commandline geeky stuff  Well, that's the way it is done.  You could pay someone to do that process for you -- but then you would need to trust them as they have your private keys.  
> **username_1**: That "commandline geeky stuff" can be done through the debug window / console that is available with the Bitcoin.org client v0.7.  
> **username_2**: Unfortunately there are some `commandline geeky stuff` commands that you will need to execute.  Please see my answer below.  

---

## 3 answers

### Answer by username_2 on 2013-09-14. Score: 20

## Manual Steps

1. Copy your public receiving addresses from Bitcoin-Qt.
2. Go to the Bitcoin-Qt console: click `Help/Debug Window` and then select the `Console` tab.
3. Run `walletpassphrase [your password] [timeout in seconds]` to unlock your password protected wallet.
4. Run `dumpprivkey [Receiving Bitcoin Address]` for each receiving address to be migrated to MultiBit. There may be hidden private change addresses in Bitcoin-Qt which don't show up in the receive tab. Run `listaddressgroupings`.
5. Copy the results of `dumprivkey` for each address (which are the corresponding private keys).
6. Start the Multibit client and create a new wallet.
7. Click `Tools/Export Private Key` after selecting the `Do not password protect export file` option.
8. Open the exported file in a text editor.
9. Below the private key generated by MultiBit, paste the private keys you have copied above. Remember to paste them before the `End of private keys` line.
10. After each private key, add a date that is prior to when you created the corresponding wallet. (You can check this date in the Bitcoin-Qt `Transactions` tab and scrolling to the very bottom.)
11. Repeat for all addresses you want to move to Multibit Client.
12. Save the key file and import it to the Multibit client using `Tools > Import Private Keys`.
13. In MultiBit, you may not see your total until you click `Tools > Reset Blockchain and Transactions`
14. In order to protect yourself from theft, delete the private key files.
15. Done!

> **Comments:**
> **username_3**: username_2's answer above is excellent, but I think there are some final steps missing, which are: After step 8: 9. Save the file that you added the keys to 10. Click Tools/Import Private Key. Find the file you saved and import it.  
> **username_4**: By the way, this is a great answer, but besides the comment of @username_3 above, you have to make sure to put a date **prior** to the creation of your wallet when pasting the private key into `multibit.key` file. This ensures the proper replaying of the blockchain which will then pick up all the transactions.  
> **username_5**: Also missing, if you have a password on your wallet, is before step 3 writing:  walletpassphrase [your password] [timeout in seconds]  
> **username_6**: My transactions were picked up, but my total did not appear in MultiBit until I did "`tools` > `reset blockchain and transactions`" at the end (after step 11).  Also, be aware that the QT-client uses hidden private change addresses that don't show up in the receive tab. `listadressgroupings` in the Qt-debug-console showed my missing addresses which I then followed steps 3-10 for to make ALL of my transactions and money appear in multibit. [Get all addresses from bitcoind](http://bitcoin.stackexchange.com/questions/9077/how-to-get-all-addresses-including-the-change-addresses-from-bitcoind)  
> **username_2**: Thanks username_5 Delgado and username_6, I updated the answer.  I hope it helps others and is easy to read.  
> **username_7**: Simpler now: `bitcoind -daemon; bitcoin-cli dumpwallet wallet-dump.deleteme; grep label= wallet-dump.deleteme | cut -d' ' -f1,2,3 > import-into-multibit.key` -- but don't do it on insecure storage! Those contain raw private keys. I'd like to improve this by importing labels as well, but couldn't figure it out.  
> **username_7**: Oh, here's the script and a helper, I'll add more if I need it: https://github.com/timmc/app-1113  
> **username_8**: Your link is dead.  
> **username_2**: Thanks, I removed the link.  I'm glad I wrote out the steps here!  

---

### Answer by username_9 on 2012-11-11. Score: 3

It does not answer your question of getting your private keys out of bitcoin-qt, but this link explains how you import a single private key into MultiBit:

<http://multibit.org/help_importASingleKey.html>

If you have more than one private key it is simply more rows in the import file.

The date alongside each key is a bit non-obvious. It has to be before the date of the first transaction using that key so that the blocks with the transactions in can be found. I recommend just finding the first transaction in your wallet and putting the date one day before it in on every row. (Using a day earlier avoids any time zone problems).

Note that the import only knows about the sipa format private keys (the ones beginning with a 5). It does not understand compressed keys. ( [What is a compressed Bitcoin key?](https://bitcoin.stackexchange.com/questions/3059/what-is-a-compressed-bitcoin-key) )

> **Comments:**
> **username_10**: Still strange to see people name the base58 private key format after me. I'd prefer them adding support for compressed public keys (which I also came up with, including the base58 format...).  
> **username_9**: Hi username_10, yes I will no doubt get round to adding parsing of compressed keys - it is in my issues list. As the export files are mainly to backup the MultiBit keys it is not top of the list though. I think you will probably have to get used to being famous. :-)  

---

### Answer by username_11 on 2014-07-19. Score: 0

I wrote this a while ago and used it to convert all my wallet.dat s to multibit.key to be able to import them to multibit.

<https://github.com/shayanb/Open-Wallet-Format>


---

