---
title: "Re-archiving Signal Capture Data"
slug: "re-archiving-signal-capture-data"
updated: 2026-03-13T11:43:43Z
published: 2026-03-13T11:43:43Z
canonical: "docs.smarsh.com/re-archiving-signal-capture-data"
---

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

# Re-archiving Signal Capture Data

Re-Archiving is a feature designed to retrieve historical data that was not archived due to specific circumstances. This process ensures that all critical data is accounted for, supporting compliance and investigative needs. Re-Archiving is especially useful in addressing gaps caused by delays in application installation, technical issues, or intentional actions to bypass archiving.

Re-Archiving ensures that:

- No critical data is lost due to archiving gaps.
- Compliance standards are met, even in challenging scenarios.
- Administrators have a streamlined way to recover missed data for defined periods.

Re-archiving in Signal Capture is a user-initiated process where administrators must request support to recover specific data for selected users and date ranges. The selected date range can span a maximum of six months. For example, if the start date is 02 August 2024, the end date must be within the six-month period, such as 01 February 2025.

The features of re-archiving are:

| **Trigger** | Admin request |
| --- | --- |
| **Effort** | Requires admin to contact support |
| **Use Case** | Specific recovery for defined date ranges |
| **Setup** | No prior setup required |
| **Timeline** | Up to 24 hours after request |

#### Limitation

Re-archiving of calls is limited to those made from this version onward.