# \[DONE\] Convert Entity to another Type

**URL:** <https://community.fibery.io/t/done-convert-entity-to-another-type/528>\
**Category:** Ideas & Features\
**Created:** [January 23, 2020, 5:45pm UTC](https://community.fibery.io/t/done-convert-entity-to-another-type/528 "2020-01-23T17:45:10Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**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:** [March 14, 2020, 7:01pm UTC](https://community.fibery.io/t/done-convert-entity-to-another-type/528/3 "2020-03-14T19:01:22Z")

</div>

Hey guys, @mdubakov sorry to bother you but I wanted to bump this up again. Very curious about your thoughts here. I know this might involve some mapping that needs to happen because types have different fields, etc. But I am seeing this need a lot now as my team gets active in Fibery.

One situation is we have things that go in as a “Project” and it turns out they are really “Tasks” and need to be changed, but a lot of work has already gone into building the entity.

One idea here would be to “convert” the entity to another type, and then popping up a modal that would allow the user to select which fields map over. If you could in fact tie the two together via automation, you’d have a very powerful feature I’ve also requested:

> [@\[DONE\] Convert entities of one Type to another Type](https://community.fibery.io/t/convert-entities-of-one-type-to-another-type/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…

This is great for something like Idea or Feature Request tracking. The original entity can have its state tied to the “created” entity. So for example with the Feature Request:

- You have a Feature Request entity, with notes and related entities for customer feedback

- You click “promote to another entity.” You have a modal in which you can copy over the data you need from the original “Feature Request”

- via a relation controlled by automation, you can then leave the “Feature Request” in a state of “promoted,” but not close it until the new entity, the “feature” itself, is “done”

- you could then track multiple feature requests and see how far along they are from the time of when you “promote” them to features that you’re working on.

Thanks guys and really grateful for any insight you can provide, even if you don’t plan to allow moving Entities to different Types.

---

_[View the full topic](https://community.fibery.io/t/done-convert-entity-to-another-type/528)._