Supported data
Your GoHighLevel data.
Know what’s included.
The hosted DataCharted Sync product loads 12 datasets into BigQuery. Here’s what each stream contains and how it is refreshed.
Dataset catalogue
These are structured extraction tables. KPI definitions, reporting models, and finished dashboards are built separately on top of them.
| Dataset | BigQuery table | Sync behavior |
|---|---|---|
| Contacts | Contacts | Incremental new contacts by creation date, or full refresh. Existing contact edits require a full refresh. |
| Inbound call records | ConversationMessages | Incremental inbound calls, or full refresh. A 10-minute settling window applies. No general SMS, email, or outbound call export in the hosted UI. |
| Form submissions | Form_Submissions | Incremental new submissions, or full refresh. Initial retrieval begins January 1, 2019, subject to API availability. |
| Survey submissions | Survey_Submissions | Incremental new submissions, or full refresh. Initial retrieval begins January 1, 2019, subject to API availability. |
| Opportunities | Opportunities | Full refresh of the current opportunity snapshot, including mutable stage, status, and value fields. |
| Phone numbers | Phone_Numbers | Full refresh of location phone-number inventory. |
| Forms | Forms | Full refresh of form definitions. |
| Surveys | Surveys | Full refresh of survey definitions. |
| Calendars | Calendars | Full refresh of calendar definitions. |
| Calendar events | Calendar_Events | Full refresh of events returned per calendar, from January 1, 2015 through three years ahead of the run date. |
| Pipelines | Pipelines | Full refresh of pipeline definitions, with stage data stored as JSON. |
| Custom fields | Custom_Fields | Full refresh of location-level custom-field definitions. |
Incremental and full refresh
Incremental runs append new records beyond a creation-date watermark. They do not provide change-data capture for every edit or deletion in GoHighLevel. Contacts, inbound calls, and form and survey submissions allow a choice between incremental and full refresh.
Full refresh reloads the supported scope as a current snapshot. The other eight datasets always use this mode. A snapshot is not a history of every change: for example, an opportunity’s earlier pipeline stages are not automatically preserved as stage-transition events.
Location selection is separate from a Locations table. The app discovers sub-accounts so you can select where to sync from. The hosted product does not currently export an agency-level Locations table into BigQuery.
Build on a known foundation
Table names and field types come from each extractor’s declared schema. DataCharted verifies the destination during setup; missing stream tables are provisioned when the first sync runs. Nested source fields may require SQL transformations before use in a dashboard.
Data availability depends on your GoHighLevel authorization, the records returned by its APIs, and the selected stream’s retrieval window. Review row counts and spot-check records after the first sync. For a historical migration, agree the required scope with us first.