Skip to main content

Upload a CSV file or Excel template: guide

If no automatic sync is available for your exchange or wallet, or you want to add missing transactions, you upload your data as a file: either as an unmodified exchange CSV or with the standardized Blockpit Excel template. An upload always belongs in the matching integration. Blockpit skips duplicates and, for an existing integration, everything that is not newer than the most recent existing transaction.

​

💡 Use Blockpit Expert Support: Want to hand over data preparation, CSV formatting or the file upload completely? Our experts take over the data migration and reconstruction turnkey for your Blockpit account. Check your effort in advance, without obligation, in the free 15-minute initial call under Expert Service.

​

At a glance

​

👁️ You upload the file with the upload icon (cloud with an upward arrow) on the integration: Integrations › upload icon › tab CSV or Blockpit Template › Next. Blockpit checks every row first against the date limit (only newer than the most recent existing transaction) and then against the duplicate check (same transaction in the same integration). Skipped rows are not imported.

​

You want to …

How

load a file into an existing integration

Dashboard › Integrations › upload icon on the integration (Path A)

add an exchange that does not exist yet by file

+ Integration › search for the exchange › tab CSV or Blockpit Template (Path B)

add a platform that is not listed

+ Integration › filter Blockpit Excel, assign a name, upload the template

add older transactions

choose an earlier start date under Import Time Span

find out why nothing was imported

section What does Blockpit skip during upload?

​

​

How do I upload my CSV or Excel file?

To avoid errors and duplicate integrations, one simple principle applies: every upload belongs directly in the matching integration.

​

📄 File formats: Blockpit reads .csv, .xlsx and .ods (LibreOffice/OpenOffice). So you do not have to convert an .ods file first.

​

Path A (recommended): upload into an existing integration

Use this path for all exchanges, wallets or blockchains that already exist in your dashboard, and when you want to add transactions:

​

1️⃣ In the Dashboard, open the Integrations tab.

​

​

2️⃣ On the integration you want, click the upload icon (cloud with an upward arrow) next to the sync button.

​

​

3️⃣ In the dialog Add <Exchange>, choose the matching tab:

  • CSV: for unmodified original files (only visible if the exchange supports direct CSV upload). You drop the file under Drop Files Here or Browse. If you cannot find it, How to find my CSV file? helps.

  • Blockpit Template: for the import with the Excel template. Download the template, enter your data (labels in English only for now) and upload the file.

​

4️⃣ Check the field Import Time Span below the upload area. If the file contains older transactions that are still missing, then choose an earlier start date under Import Time Span. The options are Full History and Start Date.

​

5️⃣ Click Next to finish the import.

​

🔎 Column B (“Integration Name”) is completely ignored when you upload with the upload icon.

​

So only upload transactions that actually belong to this integration.

​

Path B: create a new integration

Use this path if your exchange or wallet is not yet set up as an integration in your Blockpit account. For a new integration, Import Time Span is set to Full History by default; with Start Date you choose a date.

​

1️⃣ In the dashboard under Integrations, click + Integration.

​

​

2️⃣ Choose your option:

  • Listed exchange: Search for your exchange or wallet. Depending on the exchange, the dialog Add <Exchange> shows the tabs Connect Account, API and CSV. Upload the file in the tab CSV (if available) or in the tab Blockpit Template.

  • Unlisted platform (direct upload): In the filter bar, choose Blockpit Excel, assign a name and upload the filled-in template directly. This creates the new integration automatically.

  • Alternative “Manual Integration” (recommended for maximum control): Create a Manual Integration, name it after your platform and click Next without uploading a file. This creates an empty placeholder in the dashboard, and you then use Path A via the upload icon (column B of the Excel template is ignored).

​

​

The path for the direct upload: Dashboard ▶ Integrations ▶ + Integration ▶ Blockpit Excel

​

​

⚠️ Important note on column B (“Integration Name”)

​

In column B of the Excel template, enter exactly the same name the integration should get.

​

If you accidentally enter the name of an existing integration, the transactions are imported into that integration.

​

​

What does Blockpit skip during upload?

Blockpit checks every row in this order: first the date limit, then the duplicate check. Rows skipped by the date limit never reach the duplicate check.

​

Date limit: only newer than the most recent transaction

If you upload a file into an integration that already has transactions, Blockpit takes only transactions after the most recent stored one. Anything older is skipped without a warning or error message. What counts is the timestamp of the most recent transaction in this integration, and an exactly identical timestamp is skipped too. So a complete or overlapping export only adds what is new since the last import.

​

If an upload imports fewer transactions than expected, or none, then the date limit is usually the reason. Choose an earlier start date under Import Time Span.

​

Upload

Date limit

CSV/XLSX into an existing exchange integration

yes

Blockpit template/Excel into an existing manual integration

yes

Blockpit Excel for several integrations (column B)

yes, each row against the most recent transaction of its integration

Import from Koinly, CoinTracking, Accointing or Binance authority upload (always create a new integration)

no

manually created transactions

no

​

Duplicate check: identical transactions are skipped

Blockpit compares every imported transaction with the transactions already stored in the same integration. On an exact match, the row is skipped. Matches can come from earlier imports and from manually created transactions. Deleted transactions also count as matches.

​

Counts as a match

Does not count

timestamp, incoming (amount/asset), outgoing (amount/asset) and fee (amount/asset)

type/label, note and transaction ID

​

The duplicate check applies …

Not if …

to CSV/XLSX uploads and imports from Koinly, CoinTracking and Accointing

it concerns Bitpanda or Bison (their own duplicate check)

within the same integration, also against manually created transactions

the same transaction is in two integrations: then it stays in both

with the fingerprint of the row stored during import

identical rows are in one file: they are all kept

—

transactions were synchronized via API or blockchain: there is no comparison with the file

​

A transaction you edit manually after the import still counts as a duplicate if you upload the same row again. Creating a transaction manually never blocks Blockpit.

​

📁 Automatic duplicate detection for file uploads

​

Our importer automatically compares new uploads with existing CSV, Excel and manually created transactions and so prevents duplicate entries.

​

✂ Focus on overlapping periods: For integrations with existing exchange (API) or blockchain transactions, data is technically not matched automatically. So remove periods that are already synchronized from your file beforehand, or choose a start date after the synchronized period under Import Time Span to avoid duplicate transactions.

​

Common mistakes when uploading

Situation

Result

How to proceed

Corrected faulty rows and uploaded the same file again into the same integration

0 transactions imported, because the rows are older than the most recent transaction

Choose an earlier start date under Import Time Span; the duplicate check recognizes rows that already exist

The exchange books rows later (e.g. staking payouts or late-credited deposits) with an older date

The rows are skipped

Adjust Import Time Span; gaps show up as the tip Missing History or, for synced integrations, Mismatched Balance

New transaction with exactly the same timestamp as the most recent one (e.g. second fill of the same trade; exchanges that export only the date without a time)

It is skipped

Adjust Import Time Span

Deleted a transaction and uploaded the same file to bring it back

It is skipped as a duplicate of the deleted transaction

Restore it with the filter View (Deleted)

Changed a label or note and uploaded the file again to overwrite the change

The row counts as a duplicate, nothing changes

Edit the change directly in Blockpit: Edit transactions

Uploaded the same file into two integrations

Duplicate transactions (no check across integrations)

Remove the duplicate transactions in one of the integrations

Uploaded a CSV covering a period the API already delivers into an API integration

Duplicates (no comparison with API data)

Remove overlapping periods from the file beforehand or choose a later start date

File contains the same row twice

Both rows are imported

Clean up the file beforehand

​

  • If a repeated upload imports 0 transactions, then the date limit is usually the reason: Blockpit only takes transactions after the most recent existing one. Choose an earlier start date under Import Time Span.

  • If you want to bring back a deleted transaction, then restore it with the filter View (Deleted). A new upload skips it as a duplicate.

  • If you upload the same file into two integrations, then duplicates appear. The check only applies within one integration.

  • If you import large histories step by step, then upload the oldest section first: after you import newer transactions, the date limit skips older ones.

​

​

How do I transfer CSV/Excel data into the Blockpit Excel template?

1️⃣ Download the template: Download the Blockpit Excel template. Save a copy in Google Sheets or download the template as an .xlsx file for Microsoft Excel.

​

​

mceclip1.png

​

2️⃣ Enter data (required fields): Transfer your transactions row by row using the sample rows. Fill in the correct side for each booking: Incoming Asset for inflows, Outgoing Asset for outflows. The columns Fee Asset, Fee Amount, Comment and Trx. ID are optional.

​

Screenshot 2024-05-22 at 13.43.24.png

​

⚠️ Transaction types/labels: For the column Transaction Type / Label, preferably use the predefined English original terms from the dropdown menu (e.g. Deposit, Withdrawal, Trade, Gift, Staking etc.).

​

3️⃣ Mind the formatting & timestamps:

  • Timestamp: Use UTC timestamps in the format DD.MM.YYYY hh:mm:ss for all dates.

  • Decimal separator: Use either a comma or a dot consistently throughout.

​

4️⃣ Several integrations in one file (column B): If you upload the file via Path B (Blockpit Excel), you can bundle transactions from different platforms. In column B (“Integration Name”), use exactly the spelling of the integration you want. With an upload via Path A, column B is ignored.

​

5️⃣ Upload & asset check: Upload the finished .xlsx file. In the following window, check the automatically recognized assets, correct wrongly recognized assets and confirm with Next.

​

6️⃣ Check after the import: Sort your transaction list by Newest imported and, if needed, filter by the integration concerned to check the result right away. For large histories it is worth importing data in test steps beforehand (oldest first, see date limit).

​

​

Numbers or dates formatted wrongly?

If numbers or dates are formatted wrongly, then set the columns to Plain text beforehand or switch the locale of your spreadsheet app to English.

​

​

Sorting.png

​

​

✂ This Excel guide and this Google Sheets guide help you with splitting your Excel data into several columns.

​

🧑‍💼 Expert Service: no time or desire to prepare and import data yourself?

​

Manually transferring transaction histories into the Excel template, cleaning faulty CSV files or reconstructing closed exchanges takes time and accuracy. With the Blockpit Expert Service (DE / AT / CH), we take over this work completely: we check your raw data, transfer your history without errors into our templates and carry out the full import directly in your account.

​

You can find detailed information on booking, process and joining the in-app call in the guide: Blockpit Expert Support – Everything about Expert Check & Expert Service. [EN-Titel pruefen]

​

💡 Optional - The free 15-minute initial call: discuss scope, process & a targeted cost estimate for your account in advance

Do you want the Expert Service to prepare your account, but you are unsure before booking about the exact time required or about missing data?

​

Simply put our free 15-minute initial call before the Expert Service. In the appointment we review your starting point and create a tailored, reliable Expert Service offer with a time and cost frame for the preparation, without you having to buy an hours package in the shop beforehand.

​

Your advantage: You do not have to select a service package in the shop beforehand. If our offer suits you, our expert books the suitable package directly with you during the appointment and starts the preparation right away.

​

Did this answer your question?