The address you won't recognize is called a change address. You won't be able to actually see what your change addresses are as they are handled internally by the wallet and typically never shown to the user. Just because you don't recognize it does not mean that you don't control the address.
To make sure that the address is yours, go to Help > Debug Window and click on the console tab. Then type
where
is the address in question. Then hit enter.
In the output, look for the field "ismine". If that is true (will look like "ismine": true,), then the address is yours and is controlled by your wallet.
Double check that your balance is actually what you expect it to be. The transactions list should say that you are sending 3 BTC, not 3.2.
Yes, the amount sent was -3 BTC, which means the other 0.2 should have returned under (change)
You can see the (change) addresses using Coin Control feature.
https://bitcoin.org/img/bitcoin-core/coin-control.pngI tried
and I got ""ismine": true," this gives me a peace of mind that I least I control the key, but the funds are not showing up.
I suspect the problem may be related to what I was talking about:
http://bitzuma.com/posts/five-ways-to-lose-money-with-bitcoin-change-addresses/Alice uses Bitcoin-Qt. Understanding the importance of backups, she created an encrypted wallet backup long ago and stored it in a safe place. After making dozens of transactions with Bitcoin-Qt, Alice's hard drive crashed.
Alice bought a new hard drive and then re-installed Bitcoin-Qt on it. She then restored her wallet backup. To her horror, Alice discovered the restored wallet was empty.
Explanation: Alice generated enough change addresses to overflow the original pool of 100. On the 100th spending transaction, Bitcoin-Qt moved Alice's change (which happend to be her entire balance) into an address not in the backup. Restoring the backup only restored empty addresses.
Recovery: Even if a hard drive can't boot an operating system, individual files can still be recovered. Using data recovery tools, Alice may be able to salvage the Bitcoin-Qt wallet from the faulty hard drive, and with it her lost funds.
Prevention:
Count the number of manually-created addresses and spending transactions since your last backup. If this number is greater than about 80, back up again. Weekly backups might be enough for most users.
Set a very high value (e.g., 10,000) for the -keypool option, either as a command line parameter, or in the bitcoin.conf file.
Switch to a deterministic wallet.
What should I do? im scared to screw something up.
And how do I properly migrate to HD format? I create a new wallet, then generate addresses and send the BTC there with the previous wallet?
In this case I waste a bit of money in transactions since I will need to do several different transactions to preserve privacy (if I sent it all at once, all my inputs will be joined which is stupid, since you wasted your time using 1 different address each time as recommended, since you will be telling the world "I own all those addresses" with 1 single transaction of the entire wallet)