# Merging entities of the same type **URL:** \ **Category:** Ideas & Features\ **Created:** [September 2, 2021, 7:37am UTC](https://community.fibery.io/t/merging-entities-of-the-same-type/1970 "2021-09-02T07:37:24Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [September 6, 2021, 5:26pm UTC](https://community.fibery.io/t/merging-entities-of-the-same-type/1970/3 "2021-09-06T17:26:14Z")
I don’t know if this is similar enough, but my needs related to this are around imported/synced data: > [@Merging synced data to existing types and avoiding "type proliferation"?](https://community.fibery.io/t/merging-synced-data-to-existing-types-and-avoiding-type-proliferation/1946): > > Not sure if this belongs in #ideas-features or not, but probably, given how it turned out after I wrote it. grinning_face_with_smiling_eyes So, it’s clear that one of Fibery’s greatest strengths is in its ability to replace multiple systems, bring data from various places into one location and interconnect it, etc. But the more I do that (now with Discourse and Airtable connected, and plans to add more), the more “type proliferation” I have. And the thing that is most challenging with this is… That thread refers specifically to integrations, but imported data from e.g. CSV would likely often suffer from similar issues. --- _[View the full topic](https://community.fibery.io/t/merging-entities-of-the-same-type/1970)._