# Import CSV and Update Existing Entities (where matches exist) **URL:** \ **Category:** Get Help\ **Created:** [August 23, 2024, 5:17pm UTC](https://community.fibery.io/t/import-csv-and-update-existing-entities-where-matches-exist/6544 "2024-08-23T17:17:18Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Pamela\_Parker](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/pamela_parker/32/9588_2.png) [@Pamela\_Parker](https://community.fibery.io/u/Pamela_Parker)\ **Post date:** [August 23, 2024, 5:17pm UTC](https://community.fibery.io/t/import-csv-and-update-existing-entities-where-matches-exist/6544/1 "2024-08-23T17:17:18Z")
Hey folks: This seems like a simple use case so maybe this is possible and I just can’t figure it out (or find documentation or discussion). There are some cases where I’m importing a CSV into an existing database and – rather than creating a duplicate of an entity – I’d like for it to update the existing entity with the additional information that’s in the CSV. Right now it seems like it just creates a new entity rather than finding and matching to one that already exists. And I end up manually having to find those and merge them together. Is there something I’m missing? Thanks much! ---
**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\ **Post date:** [August 24, 2024, 9:05pm UTC](https://community.fibery.io/t/import-csv-and-update-existing-entities-where-matches-exist/6544/2 "2024-08-24T21:05:52Z")
Hi, Pamela! It’s not possible indeed But you can try checking deduplication template in our template gallery - in Advanced category This template will help to configure process like this: 1. You import into existing database 2. Automation find duplicates 3. Compares those duplicates 4. Updates one of them with the missing information 5. Deletes the one with less info If smth will be unclear, you can ping us via chat btw, curious to know where the data is coming from - maybe it will make sense to have integration instead\> ---
**Author:** ![Pamela\_Parker](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/pamela_parker/32/9588_2.png) [@Pamela\_Parker](https://community.fibery.io/u/Pamela_Parker)\ **Post date:** [September 10, 2024, 7:16pm UTC](https://community.fibery.io/t/import-csv-and-update-existing-entities-where-matches-exist/6544/3 "2024-09-10T19:16:39Z")
I have looked at the deduplication template already. It looked like it was set up to where the info from the newly-created entity is pasted to the original entity, then the newly-created entity is deleted. It seems like that might create problems where the newly-created entity could overwrite some of the fields in the original entity, if, for example, certain fields in the newly-created entity were blank. Is that correct? I would prefer some way to automatically identify and merge duplicates instead, if the update upon import function isn’t included. Maybe an automation that would find duplicates and merge them, instead of copying one over the other and deleting? Or only copying over when the new entity has data in a field and the original entity doesn’t? ---
**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:** [September 10, 2024, 7:49pm UTC](https://community.fibery.io/t/import-csv-and-update-existing-entities-where-matches-exist/6544/4 "2024-09-10T19:49:20Z")
> [@Pamela\_Parker](#): > > It seems like that might create problems where the newly-created entity could overwrite some of the fields in the original entity, if, for example, certain fields in the newly-created entity were blank. Is that correct? > > I would prefer some way to automatically identify and merge duplicates instead, if the update upon import function isn’t included. You can set it up to always overwrite with the new data, or only overwrite if the new data is not empty, or only overwrite if the old data is empty, or whatever combination you would like. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 14, 2025, 1:08pm UTC](https://community.fibery.io/t/import-csv-and-update-existing-entities-where-matches-exist/6544/5 "2025-08-14T13:08:28Z")
Done > [@August 14, 2025 / honey\_pot Update existing entities via CSV, even more small UI improvements](https://community.fibery.io/t/august-14-2025-update-existing-entities-via-csv-even-more-small-ui-improvements/9411): > > honey_pot Update existing entities via CSV Sometimes import doesn’t happen just once, it happens from time to time. In this case, you don’t want just to add new records but also update the existing ones. Introducing three ways to deal with duplicates: Always create new records (previously, the only option); Update existing records based on name, ID, or some other Field; Skip duplicates based on some Field. No need to slice and dice your CSV file before uploading and configure wor… ---
**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:** [August 14, 2025, 9:06pm UTC](https://community.fibery.io/t/import-csv-and-update-existing-entities-where-matches-exist/6544/6 "2025-08-14T21:06:15Z")