# No option to skip empty source fields when updating existing target data via CSV **URL:** \ **Category:** Bugs & Issues\ **Tags:** import\ **Created:** [October 20, 2025, 5:42pm UTC](https://community.fibery.io/t/no-option-to-skip-empty-source-fields-when-updating-existing-target-data-via-csv/9853 "2025-10-20T17:42:42Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [October 20, 2025, 5:42pm UTC](https://community.fibery.io/t/no-option-to-skip-empty-source-fields-when-updating-existing-target-data-via-csv/9853/1 "2025-10-20T17:42:42Z")
**Issue:** - In the configuration form of the CSV import feature, - in In ‘Manage Duplicates’ - when selecting ‘Update existing entity’ - And the data that is imported contains fields that are not empty and that are empty. - The import overwrites ALL fields regardless of the new values are empty or not, even if the original version of the entity does have a value in that field. - The result is data loss, since import is likely never intended to erase existing field data. Expected: - This should be a clear option: Do not overwrite target field values with source empty values. **Context:** When you import a CSV file into an existing Database, some rows in your file might correspond to existing entities. There are three options on how to deal with such records: 1. Always create an entity per row, regardless of whether it’s a duplicate. 2. Update existing entities when found based on a specific Field. \< This needs extra option 3. Skip duplicates when found based on a specific Field. ---
**Author:** ![dmytro](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dmytro/32/13688_2.png) [@dmytro](https://community.fibery.io/u/dmytro)\ **Post date:** [October 27, 2025, 12:17pm UTC](https://community.fibery.io/t/no-option-to-skip-empty-source-fields-when-updating-existing-target-data-via-csv/9853/2 "2025-10-27T12:17:50Z")
Thanks for flagging this — you’re absolutely right about the current behavior. When you select _Update existing entity_ during CSV import, Fibery **does** overwrite all mapped fields, including replacing existing values with empty cells from the CSV. **Workaround:** Before importing, remove any columns from your CSV that contain empty values you don’t want to overwrite. That way, those fields in Fibery will remain untouched. If we see more people running into this, we’ll definitely reconsider adding an option for this. Let me know if the workaround helps or if you need anything else! ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [October 28, 2025, 10:59am UTC](https://community.fibery.io/t/no-option-to-skip-empty-source-fields-when-updating-existing-target-data-via-csv/9853/3 "2025-10-28T10:59:58Z")
Thanks @dmytro - still i want to keep this flagged as bug, since it leads to unintended data loss, as it did with me. So one quick warning at that setting would at least be needed, and then later the added option to filter, which needs actually be the default option since likely nobody wants to overwrite existing data with empty values. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [October 28, 2025, 11:57am UTC](https://community.fibery.io/t/no-option-to-skip-empty-source-fields-when-updating-existing-target-data-via-csv/9853/4 "2025-10-28T11:57:06Z")
> [@Yuri\_BC](#): > > nobody wants to overwrite existing data with empty values. never say ‘never’ 😉 (or never say ‘nobody’ in this case) Our experience is that there’s always someone that wants to do something you didn’t think anyone would! ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [October 28, 2025, 12:00pm UTC](https://community.fibery.io/t/no-option-to-skip-empty-source-fields-when-updating-existing-target-data-via-csv/9853/5 "2025-10-28T12:00:22Z")
your quote me be left out the ‘likely’ in front of that sentence. But I’m not talking about edge cases, the idea is to prevent data loss caused by behavior that technically can be easily prevented, and not to say ‘tough titties’ to the few percentage of people that learn it the hard way. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [October 28, 2025, 12:05pm UTC](https://community.fibery.io/t/no-option-to-skip-empty-source-fields-when-updating-existing-target-data-via-csv/9853/6 "2025-10-28T12:05:10Z")
> [@Yuri\_BC](#): > > your quote me be left out the ‘likely’ in front of that sentence. But I’m not talking about edge cases, the idea is to prevent data loss caused by behavior that technically can be easily prevented, and not to say ‘tough titties’ to the few percentage of people that learn it the hard way. Yeah, I was just making a joke about the challenges we face with pleasing everyone 🙂 ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [October 28, 2025, 12:12pm UTC](https://community.fibery.io/t/no-option-to-skip-empty-source-fields-when-updating-existing-target-data-via-csv/9853/7 "2025-10-28T12:12:31Z")
very good 😆 now i get it. My inner child indeed wants to break its toys sometimes. Keep them coming, lightens up the community