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
Important: Historical backfill is a one-time process that requires coordination with the Kroo implementation team to ensure data integrity and optimal performance.
When You Might Need Historical Data
Compliance Reporting
Generate reports spanning multiple years or including completed projects
Trend Analysis
Analyze performance patterns across historical and current projects
Benchmarking
Compare current project metrics against historical baselines
Data Migration
Consolidate data when switching from legacy systems
How to Request Historical Backfill
1
Identify Your Needs
Document which projects, date ranges, and data types you need backfilled
2
Contact Implementation Team
Reach out to your implementation contact with your requirements
3
Review Scope & Timeline
Work with the team to define the backfill scope, timeline, and any potential impacts
4
Schedule & Execute
The implementation team will schedule and execute the backfill process during optimal hours
5
Validate Results
Review the backfilled data to ensure completeness and accuracy
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
Performance Impact
Historical backfills may temporarily affect sync performance for current data. The team will schedule these during low-usage periods.
Data Volume
Large historical datasets may require additional storage planning and cost considerations.
Data Quality
Historical data quality depends on the source system’s data integrity during the requested time period.
Need Assistance?
Contact Implementation Team
Ready to request historical data? Reach out to your implementation contact or email [email protected] with your requirements.
Response Time: Historical backfill requests are typically processed within 3-5 business days, depending on the scope and complexity of the data requirements.