This guide explains some of the most common reasons for failed imports.
Mistakes Exporting the File
The most common issue for an import error is that your transaction history files are not in the format that CoinLedger requires.
Please refer to our step-by-step guides for exporting your transaction history from each exchange and follow them EXACTLY as seen. Many times, users skim them and miss very important steps. This often leads to errors.
We are always working to keep our guides up to date. If spot something in our guides that does not makes sense, please reach out to our customer support team and we will get that updated.
Exchanges Adding New Transaction Types
The crypto space is always changing, and it's pretty common for exchanges to roll out new products and add new transaction types to the files they export. If you see an error message that says "Unexpected Transaction Type" this most likely means that the exchange has made a change to the file they export, and we will need to update our importer read the new file.
In these cases the fastest solution is to send a copy of the file (un-opened and un-edited) to our customer support team, and we will make sure it gets to our engineering team for their review.
Unsupported Transaction Types
There are some transaction types that CoinLedger does not yet support. This includes margin trades, futures trades, and loan transactions. We are working hard to add full support to these transaction types in the near future. If you would like to receive an update by email when we roll out support for these transaction types, send in a feature request to our customer support team and we will add you to the specific email list for that feature request.
The most common issue for an import error is that your CSV files are not in the format that CoinLedger requires.
Please refer to our guides for exporting your trading history from each exchange and follow them EXACTLY as seen. Many times, users skim them and miss very important steps. This often leads to errors.
There is also currently a known issue in Safari where file uploads aren't handled properly. Please try using Chrome/Firefox to upload your trading history file on this step.