<p>Copy the wallet.dat onto another machine, put it in <a href="https://en.bitcoin.it/wiki/Data_directory" rel="noreferrer">the appropriate folder</a> and either sync your Bitcoin from the Genesis Block with the network, or run it with <code>-rescan</code> <a href="https://en.bitcoin.it/wiki/Running_Bitcoin" rel="noreferrer">option</a>.</p>

CC BY-SA 3.0
2012-05-11T10:07:02.773Z
-rescan is probably unnecessary. According to sipa, from a certain version (much earlier than what the OP is using) the wallet.dat file keeps track of which is the latest block it knows, and automatically rescans from that point onward.
Meni Rosenfeld
CC BY-SA 3.0
2012-05-11T10:18:29.343Z
Since 0.3.21, in fact (april 2011).
Pieter Wuille
CC BY-SA 3.0
2012-05-11T07:00:41.120Z
2012-05-11T07:00:41.120Z
ThePiachu
<p>I have a client/wallet on a work machine of which I cannot control the proxy and allow the client to synchronise properly. Before I knew this however, I sent coins to the wallet. How do migrate this wallet to my home machine, so I can receive the transaction?</p>

<p>I am using <a href="https://en.bitcoin.it/wiki/Bitcoin-Qt" rel="nofollow">Bitcoin-Qt</a>.</p>

<client><wallet>
How do I move a client/wallet to a different machine?
user1354
# How do I move a client/wallet to a different machine?

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

I have a client/wallet on a work machine of which I cannot control the proxy and allow the client to synchronise properly. Before I knew this however, I sent coins to the wallet. How do migrate this wallet to my home machine, so I can receive the transaction?

I am using [Bitcoin-Qt](https://en.bitcoin.it/wiki/Bitcoin-Qt).

**Tags:** client, wallet


---

## 1 answers

### Answer by username_1 on 2012-05-11. Score: 5

Copy the wallet.dat onto another machine, put it in [the appropriate folder](https://en.bitcoin.it/wiki/Data_directory) and either sync your Bitcoin from the Genesis Block with the network, or run it with `-rescan` [option](https://en.bitcoin.it/wiki/Running_Bitcoin).

> **Comments:**
> **username_2**: -rescan is probably unnecessary. According to sipa, from a certain version (much earlier than what the OP is using) the wallet.dat file keeps track of which is the latest block it knows, and automatically rescans from that point onward.  
> **username_3**: Since 0.3.21, in fact (april 2011).  

---

