Data Sync and Backfills
Volv Analytics depends on data arriving from your connected systems over time. This page explains what syncs and backfills are, what outcomes you should expect to see, and when to contact the Volv team if something looks incomplete.
What this page is about
- Syncs bring newer changes from connected systems into Volv.
- Backfills bring in older historical data so reporting is more complete.
- The customer-facing experience is primarily about connection state and data showing up in reports — not a full sync-management console.
How data sync works
After an integration is connected, Volv ingests data from that source in the background. Depending on the integration, this can include records such as:
- CRM contacts, people, and opportunity data
- Meeting or scheduling activity
- Marketing, payment, or form-submission data
You should think of sync health in terms of outcomes:
- the integration is connected
- new activity starts appearing in Volv
- reports and dashboards become more complete over time
What you can verify in the product
The visible product surface is focused on whether an integration is connected, not on exposing every sync control.
In Settings > Integrations and related onboarding connection screens, you can confirm whether a source is connected and reconnect it if needed.
Use that connection state together with your reporting outcomes to validate that data is flowing:
- a source shows as connected
- recently created or updated records begin appearing in Volv
- expected metrics and dashboards stop showing obvious gaps
What this page does not imply
This guide does not assume that every workspace has customer-visible controls for:
- changing sync intervals
- viewing a detailed sync history timeline
- triggering source-specific sync jobs
- editing platform-specific sync settings
If you need one of those actions, treat it as a support or operations request unless your Volv team has explicitly enabled and documented it for your workspace.
Historical data backfills
A backfill imports older data so your reporting is not limited to only what arrived after initial connection.
Backfills are most relevant when:
- you are newly onboarded and want prior history included
- a new integration was connected after activity already existed in that system
- historical data appears incomplete for a known period
- Volv support asks to rerun or extend historical coverage during troubleshooting
What to expect from a backfill
Backfills are usually handled during onboarding or coordinated with the Volv team. After a successful backfill, you should expect to see:
- older records populate in reports
- historical trends become more complete
- fewer gaps in date ranges that were previously empty or undercounted
Backfills may take time depending on source volume, API limits, and how much history needs to be imported.
When to contact the Volv team
Contact support or your Volv point of contact if:
- an integration shows as disconnected and reconnecting does not fix it
- recent activity is missing after a reasonable processing window
- historical reporting still has gaps you expected a backfill to cover
- you need an older date range imported or reprocessed
When you reach out, include:
- the integration involved
- the date range you believe is missing
- example records or people you expected to see
- screenshots of the connected state and the affected report, if available
Troubleshooting mindset
For most customers, the practical questions are:
- Is the integration connected?
- Is new data appearing in Volv?
- Do historical reports still show gaps that need investigation?
If the answer to any of those is no, use the Troubleshooting guide first, then escalate to the Volv team for sync or backfill investigation.