# Add 'convert' option to automations so references, comments and files are kept

**URL:** <https://community.fibery.io/t/add-convert-option-to-automations-so-references-comments-and-files-are-kept/4288>\
**Category:** Ideas & Features\
**Tags:** automations\
**Created:** [April 10, 2023, 10:50am UTC](https://community.fibery.io/t/add-convert-option-to-automations-so-references-comments-and-files-are-kept/4288 "2023-04-10T10:50:10Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [May 20, 2025, 10:28pm UTC](https://community.fibery.io/t/add-convert-option-to-automations-so-references-comments-and-files-are-kept/4288/6 "2025-05-20T22:28:27Z")

</div>

@YvetteLans, not necessarily related to using automations for this, but would something like this, where there is basically a wizard that helps when you need to convert an entity to another db, be useful? This is one of the better examples I’ve seen out there (from Jira):

> [@\[DONE\] Convert Entity to another Type](https://community.fibery.io/t/done-convert-entity-to-another-type/528/4):
>
> 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](https://confluence.atlassian.com/jiracoreserver073/moving-an-issue-861257345.html?_ga=2.12784062.869910720.1592530414-1775210009.1592530414): Here is a hi…

What you’re saying here is our biggest pain point - sometimes after some months we see we need to move something to another db, but it’s accumulated a bunch of valuable history we don’t want to lose in the current way you move an entity from one db to another.

> [@YvetteLans](#):
>
> Unfortunately I missed the references, comments and files.
> 
> - In the current automations I create the applicable entity and delete the braindump entity
> - But comments, references and files get lost in this set-up.

Thanks!

---

_[View the full topic](https://community.fibery.io/t/add-convert-option-to-automations-so-references-comments-and-files-are-kept/4288)._