> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.8.8-monthly-release-notes.md).

# Backup & Archive (v4.8.8) ‐ Monthly Release Notes

{% hint style="info" %}

#### Release Details - Backup & Archive - v4.8.8 - October 26, 2026

This article is intended for Salesforce administrators, compliance officers, and IT teams responsible for managing Salesforce backups and data governance.

**Release Type**

* Monthly
* Applies to Flosum-hosted and self-hosted

**Prerequisites**

* A registered and configured Flosum Cloud Apps tenant
* Appropriate Flosum user permissions (SystemAdministrator or equivalent)
  {% endhint %}

## ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FPL2eaOdTi7VscAjFymsv%2FSummary2-Small-Icon.svg?alt=media\&token=a14ffcd6-66df-43ec-aafc-61364d19c7cd) Summary

This article documents the monthly release for **Backup & Archive (v4.8.8)**. This release adds the option to export an object's data directly from a specific backup. You can save the export to internal storage for download or send it to your configured external storage. Export requests can also be created through the API.

### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FgG2A2IRhOXknRFbAGToW%2FNew-Feature-Icon2-Small.svg?alt=media\&token=76ce09b1-243a-482d-97e4-ccc4cbc94d67) Export Data from a Specific Backup

#### What Changed

**Backup & Archive** now lets you export data for a Salesforce object from a specific backup. This is an additional way to export data, and the existing export options remain available.

You can now:

* Export an object's data directly from a specific backup.
* Save the export to internal storage and download it later.
* Send the export to your configured external storage.
* Create export requests through the API.
* Receive status and error information when an export request is invalid or the export fails.

#### Why It Was Done

This enhancement gives you more flexibility in accessing backed-up data, and it lets you export only the data you need to the destination you prefer. It also lets integrations and automated workflows start exports through the API.

#### What You Will Notice

An object's page inside a backup now has an **Export** button. It creates an export request for that object from that backup, and you choose where the export goes:

* An **Internal export** starts the export request immediately. The export file is stored internally and is available for download later.
* An **External export** opens the export request with the backup and object already selected. You select the external storage for the export, and then click **Run Export** to start it.

![](https://content.gitbook.com/content/KdKbUdYCYQswKDxgzTfY/blobs/PnlxHaYf2UKTAkXrjCPe/BA-V4.8.8-01-Glow.png)

![](https://content.gitbook.com/content/KdKbUdYCYQswKDxgzTfY/blobs/pe7aturLVdhKpcFGEbBj/BA-V4.8.8-02-Glow.png)

{% hint style="info" %}

#### Important

The export includes data only for the selected object from the selected backup, so what you can export depends on the contents of that backup.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flosum.com/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.8.8-monthly-release-notes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
