[DONE] Convert Entity to another Type

Hi again,

I wanted to request the ability to move an entity to another type, perhaps by drag and drop or copy/paste? I have reorganized my Apps from time to time, and had some entities that were built out with descriptions, comments, and some related stuff, that were now in the wrong Type due to this reorganization. I would really like to be able to not lose this entity, or many entities if they all need to move to the correct Type. Right now the only way I can see to do this is to delete the Entity and re-enter it in the new Type.

This is related to:

however, in this case I’m not talking about moving an entity all the way to another app…although I guess if you could move it to any other type in Fibery, not just a type in the same app, this would be the same thing as moving it to another app.

Thanks Guys!

1 Like

Hi Guys,

Wanted to bump this up as I am hoping it is something we will see in the future. The reason I am asking again is that as I build my Fibery, I am both working in it, and evolving the set up at the same time. So I am seeing a few situations where I’d like to adjust the set-up of Types and Apps, but in a few cases there are tens of entities I’d need to recategorize to do this.

Here is an example: I am tracking both “ideas” and “questions” for my team as entities. I set this up to try to capture thoughts and questions my team has on a daily basis, that would previously get buried in Slack or Email. Initially I was using one entity to track this, as I thought that was sufficient, with a select list to choose whether the entity is an “idea” or “question.” But this is really working well, to the point now that I can see I should really have an entity for both “ideas” and “questions.” One reason is that as the current entity that contains both gets filled, we are seeing a different dynamic about how we handle ideas vs. questions, for example they should go through different workflows. But if they are in the same entity, I have to use the same workflow.

What I’d like to do is filter the entities that are now categorized as “ideas,” and move them to a new entity type just for “ideas.” If I can’t do that, I’m faced with copying and pasting 10s of entities that are already built out with relations, comments, attachments, etc. that I don’t want to lose.

Moving entities across Types is like moving tasks between Folders in Wrike, or issues between Projects in Jira, which I consider basic functionality of a work management tool. So I’m hoping this is something you guys also plan and consider a basic feature.

Thanks as always for the consideration!

1 Like

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:

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.

1 Like

Guys, just wanted to try to find out again if you have thoughts on this. I imagine as the user base of Fibery grows I won’t be the only one with this issue.

For more context, this is a big piece of Jira, which I’m sure many Fibery converts have dealt with, and because of the massive customization you can do in Jira issues - which in many ways is one of the ways it closely resembles Fibery - there is an actual wizard that does the mapping, you can see it discussed in this article:

Here is a highlight:

Thanks for the consideration and hoping to hear from you on this!

Hey, I just wanted to add one more point of context to this feature. I realize there are complexities given the mapping around different Types, but it is a need that arises a lot, that’s why I think Jira has a complex, but no question well-thought out, process around this.

What I wanted to mention is that this is also a downside of Notion and Coda, so again an opportunity to get out in front of them. With Notion in fact, you will lose all relations and properties, and it happens without practically any alert. If you click “move” your Page will just appear in the new Table, like one of the Pages in that table, and if there are no common properties, it will be empty. I’m sure that is not something that is helpful to Notion users who want to move Pages around dB’s!

Thanks guys and eager for any guidance on this one as I run up against it frequently!

Hey Guys, just wanted to bump this one too as I have not seen any official response to this. Seems like a common need. Just about any other tool I’ve used allows for moving the data record from one “area” to another:

  • The above Jira Example
  • Moving between Tables in Notion
  • ClickUp - easily moving between lists/Folders and converting those to respective entities

As my Fibery instance grows, I have several situations where I’d like to move one or many Entities around as they are better served elsewhere. I think evolving your set up freely is one of the benefits of Fibery, and you guys let users do this more readily than other tools due to your flexibility. But it seems that you should also be able to evolve your data set up as well, and now, since Entities are locked essentially permanently to an initial structure, this is impossible.

You recently released

…so it would be great if you could also have the option with the Batch view to move Entities to another Type, with the remapping dialogue perhaps a part of that.

Hope you guys intend to bring this functionality out soon, would greatly appreciate guidance!

1 Like

It also occurs to me that this could be handled if you guys were able to implement the excellent “Import Data” dialogue. I just used this now for the first time as I was building my Fibery Instance “clean” up till now. And I notice that it has all the re-mapping functionality already there.

So I’m hoping you guys could potentially utilize that more “in-app” in Fibery and with the existing Batch Select feature, there will be an option to simply move Entities to other Types. I could really use this as my Fibery evolves and I see new ways to optimize Entities, but they are stuck in the wrong Type. Thanks!

1 Like

Yes! I thought about this too, that the “remap” functions are already there and well implemented (better than in many other apps!), but hardly get use, at least for me. Moving between types with a similar approach would make a lot of sense, I think.


Exactly, I just discovered this whole tool and the remap stuff is really well-executed. And you are right, I can’t use all of them because I’ve been using this to try to move my stuff in and out of Fibery, so those fields that can’t show up in “Table View” I can’t use the mapping for!

1 Like

We have this in our backlog, but so far no estimates about possible dates.


+1. Ability to convert to another type would be very helpful. Especially for converting tasks to projects.

For now, we just use references to create task. Then, so in theory ― this still works since we can keep a record of where it came from.


1 Like

Done already, you can check the details here :muscle:

This is “done” but not all valuable features are actually there for converting. For example this:

But also this from another, seemingly identical or quite similar topic:

Emphasis is mine. I have a new, related feature request for that, one possible way to implement it:

1 Like

Just adding here that we need the Convert action in automations.

1 Like

@Yuri_BC Totally agree.

1 Like

yes - convert entities to another type should offer some way of mapping.

I am currently trying to convert clickup stuff into my fibery setup and this seems to be impossible in the current setup without coding …

1 Like