# Enhance the Export/Import Mechanism to not import un-used columns by the app been imported

**URL:** <https://community.tulip.co/t/enhance-the-export-import-mechanism-to-not-import-un-used-columns-by-the-app-been-imported/13324>\
**Category:** Product Suggestions\
**Created:** [December 11, 2024, 8:21pm UTC](https://community.tulip.co/t/enhance-the-export-import-mechanism-to-not-import-un-used-columns-by-the-app-been-imported/13324 "2024-12-11T20:21:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ecarpena](https://avatars.discourse-cdn.com/v4/letter/e/8e7dd6/32.png) [@ecarpena](https://community.tulip.co/u/ecarpena)\
**Post date:** [December 11, 2024, 8:21pm UTC](https://community.tulip.co/t/enhance-the-export-import-mechanism-to-not-import-un-used-columns-by-the-app-been-imported/13324/1 "2024-12-11T20:21:56Z")

</div>

I have observed that when migrating new applications form a development instance to QA and then to PROD, the Export/Import mechanism copies columns that are not being used by the app being imported. This led to have unused columns from other apps that were in-progress on QA and PROD instances.

It would be great if the Export/Import mechanism be revised to assure that only columns that are being used on the app are the ones that gets created.

---

<div class="post-metadata">

**Author:** ![shep](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/shep/32/8231_2.png) [@shep](https://community.tulip.co/u/shep)\
**Post date:** [December 18, 2024, 5:59pm UTC](https://community.tulip.co/t/enhance-the-export-import-mechanism-to-not-import-un-used-columns-by-the-app-been-imported/13324/2 "2024-12-18T17:59:09Z")

</div>

Hi @ecarpena, thank you for the post. Could you share more about the un-used columns? Are these columns in a table used by multiple apps, and therefore you would like only specific columns to be imported, such as ones used by only a specific app?