Importing from CoinTracker

Checked against app build 2026-08-26-01-41 on 2026-08-26.

CoinTracker users move over with one file, and the import follows the same contract as every other source, nothing is added until you have seen what was read.

Which CoinTracker export should I use?

Export your full transaction history as CSV, not a tax report and not a single year.

CoinTracker’s tax documents are summaries of a calculation, and a summary cannot be recomputed. The transaction export is the raw history, and the raw history is what the engine needs. Take everything from your first crypto purchase onward, because section 104 pooling means your earliest acquisitions price your latest disposals, and a partial history produces confidently wrong numbers. See the UK rules for why the whole history matters.

How do I import the CoinTracker CSV?

Open Import in the sidebar, choose the file, and read the preview before confirming.

The preview reads the file and shows the arithmetic before anything joins your workspace, how many rows the file held, how many were read, how many tax events they become, and every difference itemised line by line. A money-only fee row set aside here, a transfer pair linked there. CoinTracker counts rows, gains.tax counts tax events, and the difference is always shown, never assumed, which is the habit explained in the reconciliation count.

Rows the import cannot honestly use are refused with the reason named per row rather than dropped without a word. If the preview matches what you expect, confirm the add. If it does not, do not confirm, read the refusal list first.

Undo in the top bar reverses a whole import in one step if the file was not the one you meant, and every imported row is editable afterwards in Transactions.

What carries over from CoinTracker and what does not?

Your transactions carry over. CoinTracker’s tax calculation does not, deliberately.

Trades, transfers, income receipts and fees come across with their dates, amounts and GBP valuations where the file carries them. The engine then recomputes everything under the UK matching rules, section 104 pooling, same-day, and the 30-day rule, and shows its working per disposal with the rule named and the legislation cited. If the two tools reach different figures, the working paper makes the disagreement inspectable rather than a coin toss between two black boxes, and the rules themselves are published with their proofs on the verification page.

What should I check after the import?

Open Reconcile before Reports, and give it ten minutes.

Anything the engine could not settle on its own is queued there for your judgment rather than guessed behind your back, ambiguous classifications, transfers missing their partner, and near-duplicates where an overlapping export describes the same trade twice, covered in duplicates. If the transaction count differs from what CoinTracker showed you, count mismatch walks through the five honest reasons in the order worth checking, and if the engine flags units it never saw you acquire, missing acquisitions covers the fixes.