Switching from Koinly to Blockpit works via a CSV export: you download your transaction history in Koinly and upload it in Blockpit under + Integration › Tax Tool › Koinly. Afterwards you map assets, labels and integrations.
Phase | What you do |
1 Export | Koinly › Transactions › Export/Import › Download (CSV) |
2 Prepare | Add NFT IDs in the comment field, create wallets in advance and delete them again |
3 Upload | Dashboard › “+ Integration” › “Tax Tool” › “Koinly”, upload the CSV file |
4 Mapping | Confirm Asset Mapping, Label Mapping and Integration Mapping one after the other |
5 Check | Check integrations, balance and transfers |
How can I download my Koinly CSV history?
Guide: download your Koinly history as a CSV file
1️⃣ Log in to your Koinly account.
2️⃣ Open the menu item Transactions and select Export/Import.
3️⃣ Use Download to download your transaction history as a CSV file.
4️⃣ The file is now in your download folder.
Things to consider in advance
Important: does my Koinly CSV file contain NFT transactions?
The export does not contain NFT IDs, only the collection ticker. So enter the specific NFT IDs in the comment field of the respective transaction in the user interface before the export, so that Blockpit can read them from the file. The rules:
▸ Incoming AND outgoing, both sides different NFTs: OUT-NFT#124; IN-NFT#125;
▸ Incoming AND outgoing, only one side is an NFT: OUT-NFT#124 or IN-NFT#125;
▸ Incoming OR outgoing OR transfers: NFT#123
Why should I add my blockchain wallets to Blockpit once in advance?
Add your blockchain wallets in advance as standalone integrations in Blockpit. Our database then creates all assets and especially specific NFTs automatically, and your assets are selectable in the asset mapping.
Delete the integrations you created in advance before you start the migration (upload of the CSV file). Then start the migration process again.
How can I upload my Koinly CSV history to Blockpit?
➡️ General steps
1️⃣ Dashboard: Start on the Blockpit dashboard.
2️⃣ Add integration: Open the Integrations tab (Dashboard) and click + Integration. Click Tax Tool and select Koinly.
3️⃣ Upload your full transaction history: Upload your full history from Koinly, either by browsing for the file or by drag and drop.
4️⃣ After the CSV file has uploaded successfully, click Continue to go to the Asset Mapping.
🔍 Asset Mapping
1️⃣ On the Asset Mapping page, you match the assets from your CSV file to the assets supported by Blockpit.
2️⃣ Check the asset recognition: Blockpit identifies most assets automatically. Check that everything is correct and adjust it manually if needed.
💡 For more exotic assets, the safest way to map them is to paste the token or contract address.
3️⃣ Save your configuration: Save your selection once everything is correct.
4️⃣ Click Continue to go to the Label Mapping.
Unable to map a specific scam token?
If you cannot map a scam token because it is not available for selection, map it to the placeholder SCAM - Scam Token Placeholder.
Specific assets or NFT IDs not selectable?
If you cannot assign an asset or an NFT ID, this helps: our database creates assets automatically when you set up the integration as a Synced Wallet first. So you can temporarily cancel the migration process and add the wallets with the unknown assets one by one as blockchain/wallet integrations. Your assets are then selectable, and you can delete the integrations you created in advance again. Afterwards, start the migration again.
If your asset is still not selectable, use generic assets as placeholders.
Special case: LUNA & LUNC
In the CSV file (not in the user interface), Koinly uses only one shared ticker for LUNA and LUNC. Blockpit corrects this during the import, so there are no wrong asset assignments.
🔍 Label Mapping
1️⃣ On the Label Mapping page, you match the labels of your old transactions to Blockpit labels.
2️⃣ Adjust and confirm labels: Blockpit presets common labels by default. Check the presets and adjust them if needed.
💡 Blockpit labels most transactions automatically. You can change them.
Merged trades from Koinly are imported directly as Trade, and Blockpit also takes over custom values directly.
Blockpit presets deposits and withdrawals to Unlabeled so that the auto-merging of transfers can take effect after the migration dialog. Income gets the label Mining for now, until an income label is implemented.
3️⃣ Confirm labels: Save your selection once everything is correct.
4️⃣ Click Continue to go to the Integration Mapping.
⚙️ Integration Mapping
1️⃣ On the Integration Mapping page, you assign your old data precisely.
2️⃣ Check the recognized integrations: Blockpit reads your CSV file and shows the integrations it recognized. Check that everything was captured correctly.
3️⃣ Set up the sync: Here you set up an auto-sync (Setup Sync) for new transactions and balances.
💡 In the Setup Sync, you enter your API credentials or your public key and set the import period. By default, the start date of the import is the date of your latest existing transaction.
⚠️ Important: You can also set up the Setup Sync later in the dashboard for individual integrations.
4️⃣ Click Continue to finish the migration process.
🎉 Finish the migration
1️⃣ Check your integrations: Open the Integrations tab in the dashboard and check that everything is displayed correctly.
2️⃣ Check the status and balance: Look at the status of each integration, e.g. Synced: 1 minute ago for exchange and wallet integrations, and check the asset balance as soon as they are synced.
♻ Balances of manual CSV/Excel integrations (not synced) are always displayed instantly.
3️⃣ Completion notification: A notification appears on your dashboard once the migration was successful.
4️⃣ Auto-merging of transfers: It can currently take a few hours until auto-merging combines your Unlabeled deposits (incoming) and withdrawals (outgoing) into a Transfer automatically. It is best to wait with your analysis until all transfers have been detected, and to start a review of your transactions before you look at the dashboard.
💡 Next, read the First steps with Blockpit article to get to know further features.
Typical mistakes and how to avoid them
Typical mistakes
✗ Did not add NFT IDs in the comment field → Blockpit only knows the collection ticker, individual NFTs cannot be assigned
✗ Created API integrations for the same exchange in addition to the migration → transactions appear twice (duplicates), use a start date or stick to one way
✗ Import period in the Setup Sync starts earlier than your last migrated transaction → transactions can appear twice
✗ Did not delete pre-created wallet integrations before the upload → assets and transactions appear twice, delete them and start again
✗ Evaluated transfers right after the upload → deposits and withdrawals are still Unlabeled, wait for the auto-merging (a few hours)
How do I start the migration completely from scratch?
If you made a mistake during the migration, you have three options: edit individual transactions afterwards, delete individual integrations and add them again (to do this, delete all other exchanges/wallets from your file and start the migration again), or start the migration completely from scratch by deleting all existing integrations. To do so, go to the account settings and select Delete Data.