Which transfer records are worth keeping

A situation that genuinely happens: three months ago you withdrew from some platform, and now the numbers do not reconcile, or support has asked you to provide the transaction hash. You go through your messages, your photo library, your inbox. Nothing. The money arrived at the time, so you never thought about it again.

Record-keeping has this property: by the time you need it, it is too late to create. And doing it takes a couple of minutes.

The four things worth keeping

The transaction hash is the important one. It is the transfer's unique identity on-chain, and anyone holding it can look up sender, recipient, amount, time and status. Without it support does not know where to start; with it, a lot of questions resolve in a minute.

The fourth is the most overlooked. A screenshot can be doubted — anyone can edit an image, while an original email carries a server timestamp and a signature. Everything the platform sends during a migration: the notice, withdrawal confirmations, review outcomes — should stay in the mailbox rather than being swept up in a tidy-up.

Storing it so it counts

Stored but unfindable is the same as not stored. Three principles:

One place, not five

Hashes in browser bookmarks, screenshots in the photo library, emails in the inbox, reference numbers on a sticky note: that is the common state and the useless one. Make a folder, or one note, and put everything in it. The method does not matter; the consolidation does.

One line per transfer, with the date

My format is one row containing: date, from where to where, which coin, how much, which chain, hash, reference. It reads like a lot and it is a minute of copy-paste. The payoff is that it becomes searchable, by coin, by date, by chain name.

Do not store the sensitive things alongside

Hashes and addresses are public information and can live anywhere. Recovery phrases, private keys and API secrets must not be in the same place, and must not be in any connected note at all. Those two categories are different in kind, and mixing them ties the convenience of the first to the risk of the second.

Taking a screenshot that is actually usable

The most flexible of the four, and the easiest to waste. The usual failures are capturing the balance without the time, or capturing a whole screen where the relevant part is illegible.

A few practical points:

• Get the system clock in frame. It sits at the edge of the screen already; include a bit more and you have it. Stronger than relying on a file modification date afterwards;
• Capture the whole page, not a crop. A crop lacks context and a reader cannot tell which platform or which page it came from;
• Redact what needs redacting. Account ID, identity details, bound phone number — cover them before sending the image to anyone. Whether to hide balances and addresses depends on the recipient: fine for official support, redact for anything public.

There is also a timing question: take the portfolio screenshot before you start moving anything. Taken afterwards it is just a picture of a new account and proves nothing about what was there. That is why it is step one of the migration handbook.

Exports beat screenshots

Most platforms offer a history export, usually as CSV. Three advantages over images: searchable, filterable by date, and directly usable by accounting tools. One export also covers a whole period rather than needing a shot per row.

Two things to watch when exporting:

• There is usually a date-range cap. Some platforms allow three months or a year at a time, so a longer span needs several passes. Do not discover this at the moment you need the older data;
• Trade history and withdrawal history are separate files. The first has prices and fees, the second has hashes and references. They cover different ground and you want both.

Rename the files to something like "platform-type-period" before filing them. Three months on, export_1724832000.csv will mean nothing to you.

Finding and reading a hash

This is not a matter of opinion. Binance’s guide to recovering a deposit with a wrong or missing tag/memo spells out what a retrieval application asks for: the coin, the deposit amount, and the TxID. The same page states that retrieval carries a fee (that coin’s transfer fee) and that if what remains after the fee is below the minimum withdrawal amount, they cannot help (checked 2026-08). Two of those three exist only in your own records — whether you can assemble them on the day you need to comes down to whether you kept them.

After a successful withdrawal, the history usually shows a clickable link or a long hexadecimal string, that is the hash. Clicking through opens the relevant chain's block explorer.

Worth reading on that page:

• Status, success or failure. A failed transaction usually does not move your money, though the fee may already be spent;
• Confirmations — how many blocks have confirmed it. The receiving platform counts to its own threshold, so "success on-chain" is not "credited";
• From and To: check the destination matches what you entered;
• Amount, check it is the post-fee figure.

Each chain has its own explorer. Bitcoin's and Ethereum's are easy to find; for anything less familiar, the link in the platform's withdrawal record is the correct entrance — just click it.

Why the few minutes are worth it

Three concrete situations:

1. Something is stuck and you need support

   "I withdrew a while ago and it never arrived" versus "on [date] I withdrew N of coin X over chain Y, hash is this, reference is this": the second lets them start searching immediately, the first costs three rounds of questions.

2. You went to the wrong chain and want it recovered

   These tickets essentially always require the hash. Without one you are blocked at the first step. The odds for each variant are tabulated in which chain to withdraw on.

3. You have to explain where funds came from

   Some compliance reviews ask you to account for a sum. "Transferred from my own account on another platform" becomes a real statement when accompanied by the hash and both sides' records; on its own it is just an assertion.

How long to keep it

No universal answer, because it depends on the reporting rules where you live: some places require several years of transaction records, others say nothing specific. This varies a great deal, and if you have a filing obligation the specific retention period is worth confirming separately.

Ignoring compliance, my rule of thumb: keep transfer records until you are confident that transfer can never be disputed, and keep trade records for as long as you can. They occupy essentially no space, and reacquiring them can be expensive — export functions have range limits, and once an account is closed the history is gone entirely.

Which gives one more rule: before closing any account, export everything exportable. That is the last opportunity.