HQ Wealth and CoinTracker: Import and Export Guide

CoinTracker is one of the most widely used crypto tax tools in the United States. HQ Wealth is a full double-entry wealth accounting platform — crypto and traditional assets in one ledger, with wallet and exchange reconciliation, FIFO/LIFO/HIFO/AVCO cost basis, staking and LP tracking, IFRS-ready reports, and tax packs. Plenty of people need both, or need to move cleanly from one to the other. That is why HQ Wealth ships a tailor-made, two-way CoinTracker adapter instead of a generic CSV dump.

This guide covers both directions: how to convert transactions to CoinTracker CSV from HQ Wealth without a single rejected row, and how to migrate from CoinTracker into HQ Wealth with every transaction mapped to a proper journal entry.

Who this guide is for

You will get value from this article if you are in one of two camps:

You are consolidating into HQ Wealth. CoinTracker did the job for tax season, but you now want a real books-of-record system — double-entry journals, multi-entity structure, reconciliation against on-chain and exchange data, and reports an accountant or auditor will accept. You need your CoinTracker history in, once, correctly.
You are keeping CoinTracker for US tax filing while HQ Wealth becomes your day-to-day accounting system. You book everything in HQ Wealth, then push a clean, importer-safe CSV to CoinTracker before filing. For this workflow the export has to be right every time, because a single malformed row can invalidate an entire upload.

Either way, the mechanics below are the same.

Exporting HQ Wealth to CoinTracker

CoinTracker's preferred ingestion path is automatic wallet and exchange sync. Manual CSV import is the documented fallback for anything CoinTracker cannot sync directly — and it is the path a third-party platform like HQ Wealth uses. In CoinTracker, you upload the file via Wallets, then Add wallet, then CSV, using CoinTracker's own template.

That template is strict. Per CoinTracker's official guide (https://support.cointracker.io/hc/en-us/articles/4413071299729-Convert-your-transaction-history-to-CoinTracker-CSV, last updated July 2026) and the official sample file (https://s3-us-west-1.amazonaws.com/coin-tracker-public/static/files/cointracker_csv_import_v4.csv), the file must contain exactly eight columns, in a fixed order, with a header row that matches the template exactly. No added columns, no deleted columns, no renamed headers.

HQ Wealth's CoinTracker exporter emits precisely this v4 template. Here is the full column specification:

| # | Column name | Required? | Format | Example | |---|-------------------|-----------------------------|------------------------------------------------|---------------------| | 1 | Date | Yes | MM/DD/YYYY HH:MM:SS — time optional, 24-hour, UTC | 06/14/2026 09:30:00 | | 2 | Received Quantity | Yes, when you received an asset | Positive number, no sign | 0.5 | | 3 | Received Currency | Yes, when Received Quantity is set | Ticker symbol | BTC | | 4 | Sent Quantity | Yes, when you sent an asset | Positive number, no sign | 15000 | | 5 | Sent Currency | Yes, when Sent Quantity is set | Ticker symbol | USD | | 6 | Fee Amount | No — blank if no fee | Positive number, no sign | 0.0005 | | 7 | Fee Currency | No — blank if no fee | Ticker symbol | BTC | | 8 | Tag | No — optional | Must exactly match a supported CoinTracker tag | staked |

The positive-amounts rule

This is the single biggest conceptual difference from most other formats: CoinTracker CSV never uses negative numbers. Direction is encoded by which side of the row is filled, not by a sign.

A trade fills both sides in a single row: Received Quantity/Currency for what you got, Sent Quantity/Currency for what you gave up.
An incoming-only event — a staking reward, an airdrop, a deposit — fills only the Received side and leaves Sent blank.
An outgoing-only event — a withdrawal to an external wallet, a gift sent — fills only the Sent side and leaves Received blank.
Fees go in the dedicated Fee Amount and Fee Currency columns, also positive, or stay blank when there is no fee.

Paste signed amounts into a CoinTracker template and the importer rejects the file. HQ Wealth's exporter decomposes every journal entry into the correct one-sided or two-sided row shape automatically, so nothing signed ever reaches the file.

Dates: US-style and UTC, or rejection

CoinTracker's importer enforces the date format. Dates must be MM/DD/YYYY, optionally followed by a 24-hour HH:MM:SS time in UTC. A wrong date format is a documented, hard rejection — the importer answers with an invalid-date-format error. ISO dates (2026-06-14), European day-first dates, and AM/PM times all fail.

Timezone matters just as much as format. If your source timestamps are in local time, they must be converted to UTC before export, or trades near midnight will land on the wrong day — which can shift a lot across a tax-year boundary. HQ Wealth stores all transaction timestamps in UTC internally, so the exporter writes UTC natively; no manual conversion step exists to get wrong.

The tag whitelist gotcha — one bad tag kills the whole file

Column 8, Tag, is optional but dangerous. The tag text must exactly match CoinTracker's supported CSV tag list, including capitalization and underscores. This is not a soft failure: depending on the case, an unsupported tag either fails the import outright or silently drops the row. In one documented real-world case, a user tagged rows with the word Interest — not on the supported list — and the entire import failed, not just the offending rows (https://feedback.cointracker.io/features/p/tag-for-interest-not-allowed-in-csv-upload).

Two more rules from CoinTracker's documentation worth internalizing:

Untagged rows are fine. CoinTracker infers Sent, Received, Trade, or Transfer defaults from which columns are filled.
Tags are not memo fields, and they must not be applied to plain trades or transfers. They exist solely to classify special income and disposal events.

HQ Wealth's exporter whitelist-validates every tag against CoinTracker's supported list before a single byte is written. Anything HQ Wealth cannot express as a supported tag is emitted untagged with the correct row shape, so the CoinTracker importer classifies it by its defaults instead of choking on it. You will never lose a 3,000-row upload to one bad label.

Importing CoinTracker into HQ Wealth

The reverse direction is deliberately built against a different file: CoinTracker's own export CSV, not the 8-column import template. CoinTracker maintains a separate, wider CoinTracker-generated CSV format for data leaving the platform (documented in their help center, article 23924019248657), and that richer file — with CoinTracker's own transaction typing — is what HQ Wealth's importer consumes. Export your full transaction history from CoinTracker, upload the file to HQ Wealth, and review the staged rows before anything posts.

During staging, HQ Wealth maps CoinTracker's transaction types and tags to native HQ Wealth transaction types. This is our mapping — HQ Wealth's design decision, not CoinTracker's specification:

| CoinTracker type or tag | HQ Wealth transaction type | Notes (our mapping) | |--------------------------------|-----------------------------|--------------------------------------------------| | Trade: fiat to crypto | BUY | Cost basis opens a new lot | | Trade: crypto to fiat | SELL | Disposal against your chosen cost-basis method | | Trade: crypto to crypto | CRYPTO_TRADE | Disposal plus acquisition, one journal entry | | Received / transfer in, untagged | DEPOSIT | Matched to on-chain or exchange records where possible | | Sent / transfer out, untagged | WITHDRAWAL | Internal transfers reconciled to the receiving side | | Staking reward tags | STAKING_REWARD | Income at fair market value on receipt | | Airdrop, mining, payment tags | INCOME | Income at fair market value on receipt | | Gift sent | GIFT_OUT | Non-taxable disposal treatment configurable | | Fee-only rows | FEE | Expensed, or capitalized into the related lot |

After you confirm the mapping, HQ Wealth posts every row as a double-entry journal entry, rebuilds cost-basis lots under your selected method (FIFO, LIFO, HIFO, or AVCO — independently of CoinTracker's method), and runs its reconciliation engine so imported balances can be checked against live wallet and exchange data. Anything ambiguous is flagged for review rather than guessed.

Quick reference: why CoinTracker rejects a CSV

| Rejection or failure | Cause | Fix | |-------------------------------|--------------------------------------------|--------------------------------------------------| | Invalid date format error | ISO or day-first dates, AM/PM times | Use MM/DD/YYYY with optional 24-hour UTC time | | Import fails on amounts | Negative numbers in any quantity column | All amounts positive; direction comes from which side is filled | | Import fails on structure | Header edited, columns added or removed | Keep exactly the 8 template columns and the exact header text | | Whole import fails on a tag | Tag not on CoinTracker's supported list | Use only whitelisted tags, exact spelling and case, or leave blank | | Wrong-day transactions | Local-time timestamps exported as-is | Convert every timestamp to UTC before export |

One broader point: every platform's CSV dialect is different, and they collide. CoinTracker wants US-style dates and positive-only amounts; Koinly wants ISO dates and signed amounts. A single generic CSV cannot satisfy both — which is exactly why HQ Wealth ships a dedicated, validated adapter per platform instead of one export-to-CSV button and a shrug.

Frequently asked questions

What is the CoinTracker CSV format? It is an 8-column template — Date, Received Quantity, Received Currency, Sent Quantity, Sent Currency, Fee Amount, Fee Currency, Tag — with US-style UTC dates, positive-only amounts, and an exact-match header, documented in CoinTracker's help center and downloadable as an official sample file.

How do I import a CSV into CoinTracker? Go to Wallets, choose Add wallet, and select CSV. Upload a file built on CoinTracker's template. Manual CSV import is the fallback for anything CoinTracker cannot sync automatically — including data exported from HQ Wealth.

How do I migrate from CoinTracker to HQ Wealth? Export your full transaction history from CoinTracker as a CSV, then upload it to HQ Wealth's CoinTracker importer. HQ Wealth stages the rows, maps CoinTracker types and tags to double-entry transaction types, rebuilds cost-basis lots under FIFO, LIFO, HIFO, or AVCO, and reconciles the result against your live wallets and exchanges.

Why did my CoinTracker CSV import fail? The four usual suspects: a non-US or non-UTC date format, negative amounts, an edited header row, or an unsupported value in the Tag column. Note that one unsupported tag can fail the entire file, not just one row — validate tags before uploading.

Bring your CoinTracker data with you

Whether you are looking for a CoinTracker alternative with real double-entry accounting or you just want your HQ Wealth books to flow into CoinTracker at filing time, the adapter works in both directions and validates everything before a file ever leaves or enters your books.

Sign in at wealth.hq-fs.com, open Imports and Exports, and pick CoinTracker. Your first round-trip takes minutes — and no row gets rejected on the way.