# Migrate Entity View to Blocks

**URL:** <https://community.fibery.io/t/migrate-entity-view-to-blocks/2005>\
**Category:** Ideas & Features\
**Tags:** blocks\
**Created:** [September 13, 2021, 8:01am UTC](https://community.fibery.io/t/migrate-entity-view-to-blocks/2005 "2021-09-13T08:01:12Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**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:** [October 11, 2021, 4:15pm UTC](https://community.fibery.io/t/migrate-entity-view-to-blocks/2005/14 "2021-10-11T16:15:44Z")

</div>

> [@a2say](#):
>
> “Standard version history” or “The ability to save a block variant in manual mode. And a convenient comparison of these variants”.

Ahh, I see, you _specifically_ want named versions. Well, this feature doesn’t exist in Fibery yet, but [has been requested](https://community.fibery.io/t/named-versions-in-docs-and-rich-text-field-history/1856). And based on what Michael says below, I suspect that if/when named versions are implemented at all, they will immediately work for Block versions too (if so, great!).

> [@mdubakov](#):
>
> Every _ **large** _ text block is a rich edit text with its own history.

Can you clarify what you mean by “large” text block?

> [@mdubakov](#):
>
> This will be easy to add I hope, we’ll definitely consider it.

Excellent, that’s exciting news! More and more Fibery looks appropriate for a personal knowledge management system too. 😄

---

_[View the full topic](https://community.fibery.io/t/migrate-entity-view-to-blocks/2005)._