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

# Historical Data Backfill

> Learn how to request historical data backfill for inactive or completed projects in Kroo.

## Overview

By default, Kroo synchronizes data only for **active projects** to optimize performance and reduce unnecessary data processing. However, you may need historical data from completed or inactive projects for reporting, analysis, or compliance purposes.

## What is Historical Backfill?

Historical backfill is the process of retroactively importing data from:

* **Completed projects** that were finished before Kroo integration
* **Inactive projects** that are no longer actively managed
* **Archived data** from specific time periods
* **Legacy systems** being migrated to new platforms

<Info>
  **Important:** Historical backfill is a one-time process that requires coordination with the Kroo implementation team to ensure data integrity and optimal performance.
</Info>

## When You Might Need Historical Data

<CardGroup cols={2}>
  <Card title="Compliance Reporting" icon="file-shield">
    Generate reports spanning multiple years or including completed projects
  </Card>

  <Card title="Trend Analysis" icon="chart-line">
    Analyze performance patterns across historical and current projects
  </Card>

  <Card title="Benchmarking" icon="chart-column">
    Compare current project metrics against historical baselines
  </Card>

  <Card title="Data Migration" icon="database">
    Consolidate data when switching from legacy systems
  </Card>
</CardGroup>

## How to Request Historical Backfill

<Steps>
  <Step title="Identify Your Needs">
    Document which projects, date ranges, and data types you need backfilled
  </Step>

  <Step title="Contact Implementation Team">
    Reach out to your implementation contact with your requirements
  </Step>

  <Step title="Review Scope & Timeline">
    Work with the team to define the backfill scope, timeline, and any potential impacts
  </Step>

  <Step title="Schedule & Execute">
    The implementation team will schedule and execute the backfill process during optimal hours
  </Step>

  <Step title="Validate Results">
    Review the backfilled data to ensure completeness and accuracy
  </Step>
</Steps>

## What to Include in Your Request

When contacting the implementation team, provide:

* **Project IDs or names** requiring historical data
* **Date range** for the backfill (start and end dates)
* **Specific data types** needed (RFIs, change orders, financials, etc.)
* **Business justification** for the historical data
* **Timeline requirements** for when you need the data available

## Important Considerations

<CardGroup cols={1}>
  <Card title="Performance Impact" icon="gauge-high">
    Historical backfills may temporarily affect sync performance for current data. The team will schedule these during low-usage periods.
  </Card>

  <Card title="Data Volume" icon="hard-drive">
    Large historical datasets may require additional storage planning and cost considerations.
  </Card>

  <Card title="Data Quality" icon="shield-check">
    Historical data quality depends on the source system's data integrity during the requested time period.
  </Card>
</CardGroup>

## Need Assistance?

<Card title="Contact Implementation Team" icon="users">
  Ready to request historical data? Reach out to your implementation contact or email [implementations@getkroo.com](mailto:implementations@getkroo.com) with your requirements.
</Card>

<Info>
  **Response Time:** Historical backfill requests are typically processed within 3-5 business days, depending on the scope and complexity of the data requirements.
</Info>