# Koinly keeps records of deleted records. That's bad

**URL:** <https://discuss.koinly.io/t/koinly-keeps-records-of-deleted-records-thats-bad/21541>\
**Category:** Site Feedback\
**Created:** [August 23, 2024, 3:57pm UTC](https://discuss.koinly.io/t/koinly-keeps-records-of-deleted-records-thats-bad/21541 "2024-08-23T15:57:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![haltlos](https://yyz2.discourse-cdn.com/flex052/user_avatar/discuss.koinly.io/haltlos/32/12213_2.png) [@haltlos](https://discuss.koinly.io/u/haltlos)\
**Post date:** [August 23, 2024, 3:57pm UTC](https://discuss.koinly.io/t/koinly-keeps-records-of-deleted-records-thats-bad/21541/1 "2024-08-23T15:57:24Z")

</div>

This is what I did:

1. Imported records from .csv
2. Bulk deleted all records
3. Tried to import a subset of the records from step 1. The import fails because Koinly flags these records as duplicates and skips them.

This means that Koinly keeps records of deleted records. Why? Apparently, Koinly deliberately wants to prevent you from importing data more than once. I don’t even know what to say – this is just stupid.

---

<div class="post-metadata">

**Author:** ![Aria\_Koinly](https://yyz2.discourse-cdn.com/flex052/user_avatar/discuss.koinly.io/aria_koinly/32/9150_2.png) [@Aria\_Koinly](https://discuss.koinly.io/u/Aria_Koinly)\
**Post date:** [August 27, 2024, 2:43pm UTC](https://discuss.koinly.io/t/koinly-keeps-records-of-deleted-records-thats-bad/21541/2 "2024-08-27T14:43:07Z")

</div>

Hi @haltlos

This is because you have soft-deleted the transactions. If you want them removed in order to re-import the transactions, you should select them and permanently delete them:

 ![image](https://canada1.discourse-cdn.com/flex052/uploads/koinly_app/original/2X/4/4bc3be4357a46578f8c4dfddb463f1dfde421970.png)

---

<div class="post-metadata">

**Author:** ![haltlos](https://yyz2.discourse-cdn.com/flex052/user_avatar/discuss.koinly.io/haltlos/32/12213_2.png) [@haltlos](https://discuss.koinly.io/u/haltlos)\
**Post date:** [August 31, 2024, 3:57pm UTC](https://discuss.koinly.io/t/koinly-keeps-records-of-deleted-records-thats-bad/21541/3 "2024-08-31T15:57:05Z")

</div>

![Screen Shot 2024-08-31 at 17.52.10](https://canada1.discourse-cdn.com/flex052/uploads/koinly_app/original/2X/c/cfc607d9f979ea6eba72d3b2ae27b6005c26f90f.png)  
Go to Wallets, select a wallet, click on “Import history”, select an import and then set the checkmark on “Delete permanently”. I may expect that to mean what is says, right?

Well, upon re-import, your system still skips transactions.

---

<div class="post-metadata">

**Author:** ![haltlos](https://yyz2.discourse-cdn.com/flex052/user_avatar/discuss.koinly.io/haltlos/32/12213_2.png) [@haltlos](https://discuss.koinly.io/u/haltlos)\
**Post date:** [August 31, 2024, 4:07pm UTC](https://discuss.koinly.io/t/koinly-keeps-records-of-deleted-records-thats-bad/21541/4 "2024-08-31T16:07:01Z")

</div>

> [@Aria\_Koinly](#):
>
> you should select them

When selecting rows in the transactions list one by one, the system lets me delete them okay. (Why is there no function to select multiple rows at once?)

When using the bulk delete function, deleting permanently doesn’t work. The system returns a “0  
Transactions were not found” message, even though the soft-deleted rows are listed right there in the transactions list.

Sorry guys, if I have to fuss around with such basic tasks, how am I supposed to cope with Koinly, once there are thousands of transactions? This is not trustworthy.

---

<div class="post-metadata">

**Author:** ![Aria\_Koinly](https://yyz2.discourse-cdn.com/flex052/user_avatar/discuss.koinly.io/aria_koinly/32/9150_2.png) [@Aria\_Koinly](https://discuss.koinly.io/u/Aria_Koinly)\
**Post date:** [September 5, 2024, 1:22pm UTC](https://discuss.koinly.io/t/koinly-keeps-records-of-deleted-records-thats-bad/21541/5 "2024-09-05T13:22:36Z")

</div>

@haltlos

That should also work if you select “delete permanently” and confirm, they should be deleted with no record kept.

If you believe this is not the case, please reach out to our support team sharing a screen recording.
