# "Archive" items before Deleting permanently and later allow "Restore" of archived items **URL:** \ **Category:** Ideas & Features\ **Created:** [April 16, 2019, 1:48pm UTC](https://community.fibery.io/t/archive-items-before-deleting-permanently-and-later-allow-restore-of-archived-items/207 "2019-04-16T13:48:46Z")\ **Posts on this page:** 1\ **Showing post:** 20
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [November 23, 2019, 7:18am UTC](https://community.fibery.io/t/archive-items-before-deleting-permanently-and-later-allow-restore-of-archived-items/207/20 "2019-11-23T07:18:55Z")
@mdubakov, thanks for the tip, and I am impressed with the sophistication you already have built into the current filters! This also occurred to me as a makeshift solution for the question I posed earlier here: > [@\[DONE\] Convert entities of one Type to another Type](https://community.fibery.io/t/moving-individual-entity-to-another-type-or-app-possible-feature-request/428): > > Hi again, I was wondering about what might be a common situation with teams onboarding into Fibery, that I will for sure have: I’d like to first start “potential” entities in a flow - things like “employee candidate” or “Sales lead,” then as they get converted to “employee” or “Customer,” not lose the whole activity that has accumulated in the entity up till then. It strikes me that creating a related entity, so say a new entity of “customer” is created with the “sales lead” is closed, is a b… Where you would set up a view with a filter for just the last column that is the “done” state of a candidate that is potentially going to be hired, or a client prospect that you have now won. It occurred to me however this still wouldn’t solve that problem, as if I wanted to add relations across entities, and I have in the same type both CRM prospects, and CRM actual clients, I will always get a list of both. I suppose it’s not in the works to have variants of type lists available in other types that would be filtered? Either way, as I think this through more thoroughly, I still think it would be a terrific feature to be able to convert/promote an entity from one type to another, and key being to bring all the data across, and note in the new entity a reference that it originated via a different type initially. Thanks again for listening! --- _[View the full topic](https://community.fibery.io/t/archive-items-before-deleting-permanently-and-later-allow-restore-of-archived-items/207)._