Use this guide to import supported crypto transactions into Navexa from a spreadsheet, review the extracted activity, and fix common import issues before saving.

Use the crypto spreadsheet import workflow when you have crypto transaction data in a CSV or Excel file.

This is useful when:

If your exchange is supported by a dedicated importer, use that option first. Dedicated importers are designed for that provider’s export format and usually give the cleanest result.

The crypto spreadsheet importer supports common crypto trading activity and selected income or transfer records.

Depending on the file format, supported activity can include:

The importer does not support every activity type from every exchange export.

Unsupported or limited activity can include card payments, card top-ups, cashback, reversals, internal transfers without clear asset details, and rows without enough information to determine their value.

Navexa’s AI-assisted importer can analyse many CSV and Excel files automatically, but support depends on the exchange format and the information supplied in each row.

Upload the original export where possible. The review screen lets you check recognised buys, sells, swaps, staking rewards and supported transfers before saving them.

Check every extracted transaction against the source file. Rows that are not recognised or do not contain enough information may need to be corrected, excluded or added manually.

For the most reliable format, click Start from a template inside the importer and download the Crypto template.

Templates are downloaded from inside Navexa rather than attached to this article. This keeps the latest templates in one place and helps ensure you are always using the current version.

The Crypto template is designed for buys, sells and swaps. To import staking rewards, upload a supported exchange transaction file or add the rewards manually. See Track Staking Rewards.

Use the Crypto template when:

If you use the Crypto template, keep the column names unchanged.

The Crypto template includes these fields:

Use the date format YYYY-MM-DD where possible, such as 2026-07-03.

The Market Pair field uses the format BASE/QUOTE.

Examples:

Use Buy or Sell as the trade type.

For crypto-to-crypto swaps, you still use Buy or Sell.

Think of it this way:

Example:

After import, Navexa may display swaps as Trade In and Trade Out inside the relevant holdings. This is expected because Navexa is showing both sides of the crypto-to-crypto trade.

In the Crypto template:

This means Amount Traded is not the total value of the trade.

Example:

You buy 0.10 BTC for AUD $9,500.

The unit price is:

9,500 ÷ 0.10 = 95,000 AUD per BTC

The template values should be:

If you enter 9500 as Amount Traded, Navexa will read it as AUD $9,500 per BTC, not the total trade value.

Use Fee for the fee amount.

Use Fee Currency Code for the currency the fee was charged in, such as:

Keep fees in their real fee currency where possible.

If the fee is charged in a coin that does not have an earlier balance in Navexa, that coin may show as negative until you add the earlier trade or transfer that created the balance.

To import your crypto spreadsheet:

Navexa supports .csv, .xlsx, and .xls files.

After you upload your file, Navexa will analyse it and show a review screen with the extracted transactions.

Before importing, check:

Click into editable fields to correct any values before importing.

Use Only show errors to quickly find rows that need attention.

If Navexa detects the wrong source, or shows Unknown broker, click the source field near the top of the review screen.

Use the side panel to search for and select the correct provider if one applies.

If your file is a generic crypto spreadsheet or template file, it is fine for the source to remain generic as long as the extracted trades are correct.

Once the review screen looks correct, click Import Trades.

Navexa will add the imported crypto transactions to your portfolio.

After importing, compare the transaction count, crypto quantities and staking reward values with the source file before relying on the portfolio totals.

When the import is complete, click View transactions. Navexa will take you to the Transactions page with an Imported trades filter applied, so you can review the transactions that were just added.

Crypto import errors often happen when a coin is spent before Navexa has a record of how you acquired it.

For example, if you buy SOL using USDT, but Navexa does not have an earlier USDT buy or transfer in, Navexa may show an error such as:

Insufficient shares to sell

This means Navexa needs an earlier balance for the coin being spent.

To fix this, use one of these options:

If you need to add a starting balance for a crypto holding:

You can use Transfer Out the same way if you need to record a withdrawal or movement out of Navexa.

For the best crypto import result:

Use these checks when extracted crypto transactions do not look right.

Crypto quantities are usually wrong when the total trade value has been entered where the coin quantity or unit price should be.

In the Crypto template:

For example, if you bought 0.10 BTC for AUD $9,500, the Amount Received is 0.10 and the Amount Traded is 95000.

A coin can show as negative when Navexa has a record of you spending that coin, but no earlier record of you acquiring it.

To fix this, add an earlier buy, import more historical data, or manually add a Transfer In before the first spend.

A crypto-to-crypto swap may show as Trade In on the coin received and Trade Out on the coin spent.

This is expected. Navexa is showing both sides of the swap inside the relevant holdings.

Rows may be skipped if they are not recognised as supported crypto transaction activity or do not contain a clear token, quantity, date or fiat value.

Compare the extracted transactions with the source file. Correct or remove unsupported rows, and add any missing activity manually.

Navexa may show Unknown broker when the file is not recognised as a specific exchange export.

You can still continue if the extracted trades are correct. If the source is wrong, click the source field and select the correct provider.