Getting Your Data Out

The question to ask about any tool that will hold years of your financial history is not what it does. It is what happens when you want to stop using it.

Most people never ask. They connect accounts, accumulate three years of records, and only discover the answer at the worst possible moment: the week their accountant asks for something, or the month the product changes in a way they dislike, or the day it shuts down. By then the history has become a hostage.

Portability is not a feature you use often. It is a property that determines how much you should trust a tool with, and it is worth checking before you commit rather than after.

Why should I be able to export at all?

Because the data is yours, and because none of it originates in the tracker.

A portfolio app is a lens. It reads balances from exchanges over read-only keys, reads addresses from public chains, and holds whatever you typed in by hand. It does not custody anything, which means the raw facts still exist at their sources even if the app disappears. What a tracker can see covers the limits of that access.

What the tracker does own, in practice, is the assembly: which addresses you decided belonged to you, what you entered as cost basis for a purchase no API recorded, the manual positions covering an OTC trade or a cold wallet, the corrections you made when a transfer imported as a deposit. That work took hours, it exists nowhere else, and it is the part you actually lose.

So the honest test is not "can I get a list of my coins." It is "can I get back the work I put in." A tool that returns balances but not your entered cost basis has handed you the cheap half.

What is actually in an export?

Formats vary, but the useful ones contain some combination of four things.

A holdings snapshot: each asset, the quantity, where it is held, and its value at the moment of export. This is the simplest export and the least interesting, because it is the thing easiest to reconstruct from the sources.

A transaction list: buys, sells, transfers, dates, quantities, prices, fees, and which account each one touched. This is the valuable file. It is what tax software consumes and what an accountant will ask for.

Cost basis records: what you paid per lot, which matters enormously and is the field most likely to be missing or incomplete. Transfers between your own accounts routinely arrive with no acquisition price attached, and a tracker that assumed zero will export a zero. Cost basis vs. market value covers spotting and repairing that before you export rather than after.

Account structure: which exchanges and addresses were connected, and how they were grouped. Nobody thinks about this until they rebuild in a new app and cannot remember the fourth wallet.

CSV is the common format because everything reads it: spreadsheets, tax packages, an accountant's software, and a text editor when something has gone wrong and you need to look at the raw rows. JSON turns up too and is better for structure and worse for the person who just wants to open it.

What is an export good for?

Four jobs, and they are genuinely different.

Your accountant. Whoever prepares your return would rather receive one file than a login. A transaction export in a plain format is the fastest thing you can hand them, and it keeps your accounts out of a third party's hands.

Tax software. Specialist packages compute gains under a specific jurisdiction's rules, apply an accounting method, and produce a form. A tracker's profit figure is not that, and treating it as though it were is a common and expensive mistake. Rules on what counts as a disposal, how crypto-to-crypto trades are treated, and which currency gains are measured in differ substantially between countries, so confirm locally rather than assuming. Tracker vs. tax software explains why the two tools answer different questions.

Your own records. A quarterly export dropped into a folder costs nothing and gives you something no live app can: a historical snapshot that does not change when the app does. If a coin gets renamed, a price feed gets revised or an exchange closes and its API vanishes, your old file still says what things looked like at the time. Auditing your tracker pairs naturally with this, since a stored snapshot is what you audit against.

Leaving. Which is the point that matters most.

What does it mean if I cannot leave?

It means the tool has a hold on you that has nothing to do with whether it is good.

This is worth being direct about. Any product can stop being the right one. It can get slower, get more expensive, drop a feature you depend on, change hands, or simply be overtaken. When that happens you want the decision to turn on which product is better, not on how many hours of re-entry the switch would cost. A tool you cannot leave gradually converts your loyalty from a judgement into a sunk cost, and that is bad for you and, in the long run, bad for the product too, because it stops having to earn anything.

The practical version of this principle is a habit rather than a stance. Export once a quarter. Keep the files. Before you commit years of manual entry to any tracker, spend five minutes finding out how the data comes back out, and treat evasiveness on that question as informative. Switching trackers covers doing the move properly when you decide to, and the tracker buyer's checklist puts portability alongside the other questions worth asking before you sign up.

If your history currently lives only in a spreadsheet, you already have the portable version and are missing the automation; tracker vs. spreadsheet covers that trade in both directions.

Start with the export you do not need yet. Pull one this week, open it, and check whether your cost basis is actually in there. If it is not, you have found a problem worth fixing now rather than in April.