> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Export

> Use Data Export to request CSV or JSON exports from the active entity for business intelligence, compliance, migration, or data portability work.

<Warning>
  **Exports can contain sensitive business data**
  Data Export can include customer and vendor records, products, orders, invoices,
  inventory balances, accounting transactions, and operator activity history. Store
  downloads only in approved locations and delete temporary copies when the review,
  migration, or reporting job is complete.
</Warning>

## Open Data Export

1. Open **Settings**.
2. Choose **Entity Settings**.
3. Open the **System** group.
4. Select **Data Export**.

Data Export is scoped to the current entity. Confirm the entity selector before requesting
an export. If no entity is selected, the **Request Export** button is disabled.

## Choose Export Type

The **Export Type** list controls which dataset Arcus exports.

| Export type     | Includes                                |
| --------------- | --------------------------------------- |
| GL Transactions | Journal entries and line items.         |
| Accounts        | Customers and vendors.                  |
| Products        | Product catalog with pricing.           |
| Orders          | Sales orders and quotes.                |
| Invoices        | Invoices with payment status.           |
| Inventory       | Current inventory balances by location. |
| Activity Log    | Operator audit trail.                   |

## Use Date Ranges Carefully

Date range fields appear only for export types that support them:

* GL Transactions
* Orders
* Invoices
* Activity Log

The **From date** and **To date** fields are optional. When you switch to an export type
that does not use dates, Arcus clears the date fields so the request does not imply a
filter the export will ignore.

Use narrower date ranges for routine review. Use broader ranges only when the business
purpose requires a full migration, archival package, or legal/compliance response.

## Pick a Format

* **CSV** is best for spreadsheet review, reconciliation, and simple handoff packages.
* **JSON** is best for structured archival, technical review, and migration tooling.

## Request an Export

1. Choose the export type.
2. Enter a date range when the type supports one and the review needs it.
3. Choose CSV or JSON.
4. Select **Request Export**.
5. Wait for the current export result or check **Export History**.

Arcus shows the export status after the request:

* **Queued**: Arcus accepted the request and is waiting to process it.
* **Running**: Arcus is generating the file.
* **Done**: the file is ready. Download it before the link expires.
* **Error**: the export failed. Review the error message and try again with a narrower request if needed.

When the export finishes, Arcus shows the row count and a download link. Large exports
are also emailed when ready.

## Review Export History

Export History shows recent export jobs for the active entity. Use it to confirm who
requested an export, when it was requested, which format was used, how many rows were
included, and whether the download link is still available.

The history table shows:

* Export type
* Format
* Status
* Row count
* Requested time
* Requester email when available
* Download link for completed jobs
* Expiration date when the download link has one

Use the refresh control when you are waiting for a queued or running export to finish.

## Safe Export Workflow

* Confirm the entity before exporting.
* Confirm the business reason before exporting broad data.
* Prefer the smallest date range that answers the question.
* Choose Activity Log only when the reviewer needs audit history.
* Store files in an approved secure location.
* Avoid emailing raw exports unless your company process allows it.
* Delete local temporary copies after the work is done.
* Review Audit Log activity when investigating who exported data.

## Common Blocks

* **Request Export is disabled**: select an entity and confirm your role allows export work.
* **Date fields disappeared**: the selected export type does not support date range filtering.
* **Rows are fewer than expected**: check export type, date range, entity, and whether the dataset is current-state only.
* **Download link is gone**: the link may have expired. Request a fresh export if the data is still needed.
* **Export failed**: retry with a narrower date range or a smaller dataset, then escalate with the export type, time, status, and error message.
* **Activity Log export is too broad**: use Audit Log filters or compliance reports when you need targeted audit evidence instead of a general activity export.

## Related Articles

<CardGroup cols={2}>
  <Card title="Audit Log and Compliance" href="/support/settings/audit-compliance">
    Review export activity, compliance reports, saved filters, and audit-log downloads.
  </Card>

  <Card title="System Operations Settings" href="/support/settings/system-operations">
    Understand how Data Export fits with printing, modules, tags, and developer access.
  </Card>

  <Card title="Roles and Permissions" href="/support/settings/roles-permissions">
    Review export-related permissions and effective access.
  </Card>

  <Card title="Organization, Entities, and API Access" href="/support/settings/organization-access">
    Confirm entity context and organization-level safety controls before broad exports.
  </Card>
</CardGroup>