# \[DONE\] Exported backup / Export all data

**URL:** <https://community.fibery.io/t/done-exported-backup-export-all-data/600>\
**Category:** Ideas & Features\
**Tags:** export\
**Created:** [March 6, 2020, 12:01pm UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600 "2020-03-06T12:01:53Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![Haslien](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/haslien/32/493_2.png) [@Haslien](https://community.fibery.io/u/Haslien)\
**Post date:** [March 6, 2020, 12:01pm UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/1 "2020-03-06T12:01:53Z")

</div>

Similar to [Backup entire workspace?](https://community.fibery.io/t/backup-entire-workspace/595), but not the same thing.

**Request**  
**I would want to have some way to backup data myself** —at least export data of certain ‘Views’, like ‘Board view’, so it doesn’t need all the interconnected data/relations that it links to.  
I my particular case I would only need the data it is currently displaying.  
Good to see that charts view has export in various formats so far.

**Why**  
I’ve come to understand it is a relatively new service/platform, and I ( **really** ) want to move from our current system to this as it is 100% what I needed. However, I _must_ be prepared for disaster with some of this data at least return.

Will be trying to set up my use cases in the meantime and try run this system in parallel.  
So far I have managed to replicate one aspect (what you define as an App), and it is much more intuitive than our current.

Currently using free plan to get to know the system, looking forward to upgrading when ready.

---

<div class="post-metadata">

**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:** [April 11, 2020, 11:04am UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/2 "2020-04-11T11:04:12Z")

</div>

@Haslien You can export data from Table View, just find Export Table action in top right corner. It will export visible data in a table as CSV. Is it enough?

![Screen Shot 2020-04-11 at 14.03.29](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e76581d340abed3b4adf2f3879dd76e2c6da8ba3.png)

---

<div class="post-metadata">

**Author:** ![Haslien](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/haslien/32/493_2.png) [@Haslien](https://community.fibery.io/u/Haslien)\
**Post date:** [April 28, 2020, 7:58am UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/3 "2020-04-28T07:58:45Z")

</div>

Yes! This works nicely 🙂Thank you

---

<div class="post-metadata">

**Author:** ![redrockcity](https://avatars.discourse-cdn.com/v4/letter/r/e480ec/32.png) [@redrockcity](https://community.fibery.io/u/redrockcity)\
**Post date:** [July 8, 2020, 1:26am UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/4 "2020-07-08T01:26:52Z")

</div>

We are having the same issue.

We easily built a custom workflow in Fibery in one day that we’ve not been able to implement on any of your competitors platforms. The product is _fantastic_! However, we’re concerned about the ability to export our data in the event we ever change platforms or, _[knock-on-wood]_, the platform goes away.

We’re aware of the Export Table feature but it only exports the currently configured table view which does not show rich text fields. Our types include many rich text fields and we can’t lose that data. It would be minimally acceptable if the Export Table feature could export rich text fields. Ideally, you would provide some kind of app / account wide full data export in compressed format. Is this a future feature on your roadmap?

Thanks!

---

<div class="post-metadata">

**Author:** ![Jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@Jean](https://community.fibery.io/u/Jean)\
**Post date:** [July 8, 2020, 2:30am UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/5 "2020-07-08T02:30:10Z")

</div>

Agree. Even though maybe most users won’t use the export function is better to have ways to export most of the important data just for their comfort, which includes rich fields and doc views.

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [July 8, 2020, 4:24am UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/6 "2020-07-08T04:24:57Z")

</div>

Agree, this makes a lot of sense to me, too. Glad to hear @redrockcity of your enthusiasm, the more satisfied users in Fibery, the better for the rest of us who have been here a while and eager for the product to grow.

Cheers!

---

<div class="post-metadata">

**Author:** ![RobinLS](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/robinls/32/884_2.png) [@RobinLS](https://community.fibery.io/u/RobinLS)\
**Post date:** [September 1, 2020, 7:29pm UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/7 "2020-09-01T19:29:19Z")

</div>

It’s very easy to delete data in Fibery. As this becomes a company-wide tool (or rather, as the company grows) this will become more of a liability. Somebody will do it. I’ve already done it twice myself. So at best I end up with a CSV file? How do I get that data back into Fibery?  
For me to be comfortable really using this tool there must be a simple way to backup data and roll back to how it was a few minutes ago (before I deleted a fair chunk of my mission-critical data).

---

<div class="post-metadata">

**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 1, 2020, 10:51pm UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/8 "2020-09-01T22:51:09Z")

</div>

Can i add my vote to this, but specifically I’d love granular export/backup capability (entity-level) if possible 🙏

---

<div class="post-metadata">

**Author:** ![Haslien](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/haslien/32/493_2.png) [@Haslien](https://community.fibery.io/u/Haslien)\
**Post date:** [September 3, 2020, 8:13am UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/9 "2020-09-03T08:13:21Z")

</div>

In the table, you also won’t be able to get the first-level content in each of the entities, like description, images in description, or fields of the type that is not shown in the table overview. It’s basically as I initially requested it, and that worked well.

My needs have however grown as my workspace grew. Exporting everything I get can be a be complicated due to references and circular dependency, but a first-level I would hope be do-able.

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [October 23, 2020, 3:50pm UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/10 "2020-10-23T15:50:26Z")

</div>

Please add me now to the users needing this functionality. Sure enough, as @Haslien and @Chr1sG are pointing out, you miss big chunks of data with the Table Export, as a key point here I just now realized is **it only exports the data you are showing from the Entity in a given Table View**. So if you just have the Name, which is the default, only that info will export.

 ![Image 2020-10-23 at 11.52.12 AM.png](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a34b234b0c7e95415d1337356beb8a0caaeee2f6.png)

So to follow on what @Haslien is saying, you can’t actually get exported any of the important stuff that won’t show in Table View, like Rich Text - so the key info of Entity Description, because that won’t be included.

I was using this as a workaround for trying to do this:

> [@\[DONE\] Convert Entity to another Type](https://community.fibery.io/t/move-entity-to-another-type/528/7):
>
> It also occurs to me that this could be handled if you guys were able to implement the excellent “Import Data” dialogue. I just used this now for the first time as I was building my Fibery Instance “clean” up till now. And I notice that it has all the re-mapping functionality already there. So I’m hoping you guys could potentially utilize that more “in-app” in Fibery and with the existing Batch Select feature, there will be an option to simply move Entities to other Types. I could …

But I couldn’t figure out why when I exported per @mdubakov suggestion, I was missing a lot of data.

Hope we can get these key capabilities pretty soon in Fibery!

---

<div class="post-metadata">

**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:** [October 30, 2020, 8:39am UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/11 "2020-10-30T08:39:45Z")

</div>

This is a part of our Fear Management initiative, most likely it will be done in the next 3-6 months.

---

<div class="post-metadata">

**Author:** ![Anton\_Kats](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/anton_kats/32/4060_2.png) [@Anton\_Kats](https://community.fibery.io/u/Anton_Kats)\
**Post date:** [September 8, 2021, 12:32pm UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/12 "2021-09-08T12:32:13Z")

</div>

Is there an update on this feature?

---

<div class="post-metadata">

**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:** [September 8, 2021, 12:33pm UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/13 "2021-09-08T12:33:49Z")

</div>

Hi!  
We released a Markdown export, so we’re slowly working in this direction 🙂

---

<div class="post-metadata">

**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:** [December 9, 2021, 8:50am UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/14 "2021-12-09T08:50:32Z")

</div>

Implementation started. It will be possible to export all data into Markdown + CSV.

---

<div class="post-metadata">

**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:** [January 5, 2022, 5:41pm UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/15 "2022-01-05T17:41:03Z")

</div>

That Feature is ready  
Please, check more details [here](https://community.fibery.io/t/changelog-jan-5-2022-export-all-the-data-limit-max-amount-of-entities-in-board-calendar-list-views-and-more/2350) 💖

---

<div class="post-metadata">

**Author:** ![Lug-gl](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lug-gl/32/5293_2.png) [@Lug-gl](https://community.fibery.io/u/Lug-gl)\
**Post date:** [June 27, 2023, 8:17am UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/16 "2023-06-27T08:17:45Z")

</div>

I would like to reopen the topic. It’s great that we can trigger and download a complete export of a workspace, but there are several manual steps involved in performing regular backups. For proper disaster management, we need to store a backup externally at least once a week. Therefore, it would be beneficial to have an automation option. Here are my desired features:

1. Specify a scheduler for when and which spaces a backup should be created. ⏰
2. Provide a URL field where the download link can be sent via POST after a successful backup creation (with a token or other authentication). 📥🔗

Some simpler ideas would also be helpful:

1. Specify a target email address. 📧
2. Perform a GraphQL query for already created backups/URLs. 🔎🗄

Best regards, Lukas ⚡

---

<div class="post-metadata">

**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:** [July 19, 2023, 10:38am UTC](https://community.fibery.io/t/done-exported-backup-export-all-data/600/17 "2023-07-19T10:38:49Z")

</div>


