Prepare the source. Review the rows. Confirm only when they make sense.
Exchange export formats can change. Keep the original source file, use the matching importer and inspect every warning before confirmation.
Preserve the original
Keep an untouched copy of the exchange export or screenshot set outside CryptoTracka.
Select the matching source
A Binance file should use the Binance importer; a neutral migration should use CryptoTracka CSV.
Review before confirmation
Check dates, duplicates, fees, unsupported assets and transfer warnings.
GCrypto
GCrypto currently uses screenshot and manual workflows rather than a dedicated GCrypto CSV importer. Capture the transaction history clearly enough to show each transaction date, type, asset, quantity and peso value.
Coinbase
Use a Coinbase account statement or custom transaction report CSV containing transaction type, asset, quantity and timestamp columns. Buys and sells also need a supported fiat value.
Binance
Use Spot Trade History for buys and sells. Use Asset Transaction History for deposits, withdrawals and rewards. Do not import trade legs from both reports or the portfolio could be double-counted.
Binance Spot sample · Binance history sample
Kraken
Use the Kraken Trades export for buys and sells and the Ledgers export for transfers or rewards. Ledger trade legs are intentionally skipped when the Trades export should be used.
Kraken Trades sample · Kraken Ledgers sample
CryptoTracka generic CSV
Use the neutral format for unsupported exchanges or controlled migration. Required concepts are date, transaction type, asset and quantity. Buy and sell rows also require a supported fiat total and currency.
| Column | Purpose | Example |
|---|---|---|
| Date | Transaction timestamp | 2026-06-11 09:30:00 |
| Type | BUY, SELL, REWARD, DEPOSIT, WITHDRAWAL or ADJUSTMENT | BUY |
| Asset | Supported symbol | BTC |
| Quantity | Positive crypto quantity | 0.0042 |
| Total | Fiat value for buys and sells | 15000 |
| Currency | PHP, USD, GBP or EUR | PHP |
Checks before confirmation
- Does every buy and sell have the correct quantity and fiat value?
- Are report dates being mistaken for transaction dates?
- Does the preview identify duplicates from an earlier import?
- Are deposit and withdrawal cost-basis warnings understood?
- Are unsupported assets excluded rather than silently renamed?
- Does the resulting quantity match the source account?
Download the complete sample pack
Includes all supported synthetic CSV examples plus a GCrypto screenshot checklist and a README.