# Feature request: automated workspace exports

**URL:** <https://community.fibery.io/t/feature-request-automated-workspace-exports/10717>\
**Category:** Ideas & Features\
**Created:** [April 8, 2026, 10:19am UTC](https://community.fibery.io/t/feature-request-automated-workspace-exports/10717 "2026-04-08T10:19:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![uzzer](https://avatars.discourse-cdn.com/v4/letter/u/34f0e0/32.png) [@uzzer](https://community.fibery.io/u/uzzer)\
**Post date:** [April 8, 2026, 10:19am UTC](https://community.fibery.io/t/feature-request-automated-workspace-exports/10717/1 "2026-04-08T10:19:08Z")

</div>

Manual workspace exports (for backup purposes) take quite a lot of time. It would be neat to have automated exports. You set export location, schedule and rules once, and that’s it. You can see how that has been implemented in Capacities ( [Export - Capacities Documentation](https://docs.capacities.io/reference/export) ).

---

<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:** [April 8, 2026, 10:49am UTC](https://community.fibery.io/t/feature-request-automated-workspace-exports/10717/2 "2026-04-08T10:49:40Z")

</div>

Do you mean workspace export?  
You should know that a workspace export is not usable as a source for restoring a workspace, so shouldn’t really be treated as a ‘backup’ solution.

---

<div class="post-metadata">

**Author:** ![uzzer](https://avatars.discourse-cdn.com/v4/letter/u/34f0e0/32.png) [@uzzer](https://community.fibery.io/u/uzzer)\
**Post date:** [April 8, 2026, 11:10am UTC](https://community.fibery.io/t/feature-request-automated-workspace-exports/10717/3 "2026-04-08T11:10:47Z")

</div>

Workspace exports, that is correct. Exported workspaces are still a backup in terms of having the data somewhere. It is still viewable, albeit not applicable to Fibery.

For instance, if I am making a database of my contacts, if something happens to Fibery, I will lose all that data. If I have it exported, I’d still be able to view it, even though I’d have lost the convenience of operating with it in Fibery. Otherwise I’d totally lose all of it.

---

<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:** [April 8, 2026, 11:38am UTC](https://community.fibery.io/t/feature-request-automated-workspace-exports/10717/4 "2026-04-08T11:38:31Z")

</div>

> [@uzzer](#):
>
> For instance, if I am making a database of my contacts, if something happens to Fibery, I will lose all that data. If I have it exported, I’d still be able to view it, even though I’d have lost the convenience of operating with it in Fibery. Otherwise I’d totally lose all of it.

Gotcha. I just wanted to make sure the expectations were set right 🙂

Note that there are a couple of related topics in the community:

> [@Export Workspace per API](https://community.fibery.io/t/export-workspace-per-api/7937):
>
> Hi I would like to do regular backups without manual intervention. Is the export availabe per API call? Thanks Martin

> [@Backup entire workspace?](https://community.fibery.io/t/backup-entire-workspace/595):
>
> It would be great to have a way to back up or create a checkpoint not just of a single app, but all apps and all their data in my account. I am paranoid that someone might delete a type/field/app by mistake, resulting in unrecoverable data loss.

> [@"Time Machine" (Version History) for Databases](https://community.fibery.io/t/time-machine-version-history-for-databases/10554):
>
> Hi Fibery team! Here is a “food for thought” suggestion regarding data safety and UX. In Google Sheets, we have Version History, which allows us to instantly see and restore the state of the entire document at any specific point in time. Sometimes, a user (or an automation/script error) can accidentally mess up hundreds of records, change a complex formula, or delete relations across the whole database. Currently, we have to check the Activity Log for each entity or ask support for a manual ba…

I guess you might want to comment/vote on those…
