# Improve Convert feature with Mapping Menu

**URL:** <https://community.fibery.io/t/improve-convert-feature-with-mapping-menu/10663>\
**Category:** Ideas & Features\
**Created:** [March 30, 2026, 5:50pm UTC](https://community.fibery.io/t/improve-convert-feature-with-mapping-menu/10663 "2026-03-30T17:50:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [March 30, 2026, 5:50pm UTC](https://community.fibery.io/t/improve-convert-feature-with-mapping-menu/10663/1 "2026-03-30T17:50:04Z")

</div>

I can’t remember the last time using the native convert function actually worked as expected. My data is never in the target database and it’s usually on some weird technicality that you don’t know because there’s no dialog, no popup or mapping menu so you can see what fields are not copying over.

I’ve tried connecting select fields to both databases, renaming fields, etc. The UX creates a lot of room for error and it’s not practical to assume fields across databases are named the same thing.

This feature request is for a popup that will prompt us users to confirm/update the mapping between fields when converting entities to other databases.

---

<div class="post-metadata">

**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\
**Post date:** [March 31, 2026, 2:10am UTC](https://community.fibery.io/t/improve-convert-feature-with-mapping-menu/10663/2 "2026-03-31T02:10:38Z")

</div>

this is a cool idea, and reminds me of uploading a random CSV full of data to Mailchimp, where you’re asked to assign each column to a field that Mailchimp expects.

A little UI here could go a long way. Although it’s worth discussing – should this dialog be shown every time? What about conversions that you’ve done multiple times using these settings… should they be “remembered” somehow so you don’t have to re-map it everytime you want to convert an Email into a Task (or whichever)?

---

<div class="post-metadata">

**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\
**Post date:** [March 31, 2026, 6:18am UTC](https://community.fibery.io/t/improve-convert-feature-with-mapping-menu/10663/3 "2026-03-31T06:18:27Z")

</div>

I was thinking it could be a one-time setup between databases. The first time you convert from Database A to Database B, there’s a conversion mapper module. Then subsequent conversions will remember this mapping. Though this may need to be modified if fields are ever added to either database.