TL;DR: Bitget's API and CSV importers each have data gaps and are not fully compatible with each other. The recommended approach is to import via API first, verify the result with the ValiCheck pages, and then add missing transactions via CSV. Always create a backup of your account before making bulk changes. Missing FIAT→Coin trades (e.g. EUR→USDT) are the most common cause of incorrect cost basis and tax report errors.
Why can't I use the API and CSV importer together?
The API and CSV importer are not compatible. If you use both importers on the same account, you might get duplicate transactions. Please delete all transactions before importing with another method.
What transactions are missing when using the API importer?
The following transactions won't be imported or only partially imported via the API due to incomplete data provided by Bitget:
- Futures PnL for the last 2 years only
- Margin PnL (missing)
- Grid Bot trades (missing)
- Copy Trading trades (missing)
- Buy with card (partly) – add the sold fiat amount and change the transaction type to a trade
What transactions are missing when using the CSV importer?
The following transactions won't be imported via CSV due to incomplete data in Bitget's export files:
- Margin PnL
- Grid Bot trades (missing)
What is the recommended way to import Bitget data?
Since neither importer alone is complete, we recommend combining both methods in this order:
- Import your Bitget data via API first.
- Check the result against your real exchange balance using the ValiCheck pages, which compare your actual account balance to the balance imported into CoinTracking.
- Create a backup of your account data before making any further changes.
- Delete all previously imported transactions.
- Re-import the same data via CSV to fill in gaps left by the API import.
Even if you only trade Futures, make sure to export and import all account types (Spot, Margin, and Futures), as Bitget's export files can reference data across these account types.
How do I correct or overwrite coin values after import?
After importing, you can use the Bulk Edit feature to overwrite or correct coin values across multiple transactions at once, instead of editing them individually.
How are transfers between Spot and Strategy (Bot) accounts handled?
Please note: Strategy transaction details are not fully supported. Transfers between Spot and Strategy accounts (and vice versa) are only imported as withdrawal and deposit transactions. If necessary, please adjust these deposits/withdrawals manually after the import.
Bot and Strategy transactions (Grid Bot, Copy Trading) are often not fully transmitted by exchanges in either the API or CSV export, which is why they show up as missing or incomplete rather than as proper trades.
Why do I see errors in my tax report or missing cost basis after importing Bitget data?
If a fiat-to-coin exchange trade is missing from your import (for example, an EUR → USDT purchase), the corresponding coin will later appear to be sold without an acquisition cost (cost basis), which causes holdings discrepancies in your balance.
Additionally, any later trades made against that currency cannot be correctly matched or valued if the underlying purchase of that currency is missing. In practice, this means tax report errors typically concentrate on the specific currency whose original purchase transaction is missing from the import.
Recommendation: Before troubleshooting Bot or Strategy trade issues separately, first check for and add any missing FIAT → Coin trades, since these are usually the root cause of downstream errors.
For German tax reporting specifically, a missing cost basis on a FIAT–USDT purchase can lead to the corresponding sale being incorrectly classified under §23 EStG (private sale transaction) instead of §20 EStG (capital gains), since CoinTracking cannot determine the correct holding period or asset classification without the original purchase record.