Contacts
Selected identity, contact, owner, source, tags, dates, and available custom fields.
Import and selected reviewed existing-record updates.
Source access and supported writable fields must be accepted.
Data catalog and availability
GoHighLevel data, with its meaning intact.
See what the early-access import and report designs use, which directions are supported, and where source acceptance is still required.
Record families and practical boundaries
Opportunities
Deal ID, contact relationship, pipeline, stage, status, amount, currency, ownership, and dates.
Import and selected reviewed existing-record updates.
Current stage is not stage history. Probabilities and history need validated sources.
Businesses
Business identities and explicit contact relationships.
Reporting/import source.
Do not infer associations from company-name similarity.
Tasks and notes
Contact-linked tasks, deadlines, current completion flags, and dated notes.
Reporting/import source.
Current completed status is not a historical completion timestamp.
Calendars and appointments
Calendar identity, event occurrences, dates, owner, and attendance status.
Reporting/import source with calendar/date scope.
Attendance meanings, recurring identity, and time windows require validation.
Invoices and payments
Invoice headers, embedded lines, balances, due dates, and transaction status/currency.
Reporting sources; financial actions are excluded.
Won sales, cash collection, and recognized revenue are different measures.
Orders and subscriptions
Order headers/lines, product references, subscription terms, and current status.
Reporting sources with live data acceptance pending.
Recurring change metrics need real lifecycle history; missing intervals are not guessed.
Conversations and messages
Conversation identities and message metadata by channel, date, direction, and known actor.
Metadata-based reporting previews.
Email bodies, recordings, transcripts, and complete response history are not established by the sample.
Forms and surveys
Submission identities, dates, and supported contact/response relationships.
Reporting preview; source/schema acceptance pending.
Repeated responses are not new contacts. Submission counts alone do not measure visitor conversion.
Custom records
A selected object schema and accepted customer-association mapping.
Synthetic Jobs example; live schema/source acceptance required.
No universal custom-object support or automatic writeback is promised.
History and snapshots
Observed stage transitions, compatible forecast snapshots, and effective-dated recurring events.
Used only when the exact history is available.
Current records cannot reconstruct unobserved events. Workflow execution reporting is unavailable.
Early access · These public previews use invented records. Join early access to discuss connecting your own GoHighLevel account.
Read and write support are separate.
A field being available in a report does not make it writable. Outgoing updates are designed for eligible fields on matching existing Contacts and Opportunities, with a fresh preview and explicit confirmation.
The public sample engines use invented relational fixtures. An object appearing in a preview is evidence of the sample calculation, not a claim that live account delivery or every field is enabled.
Count primary transfers, not spreadsheet formatting.
Each execution counts its successfully transferred primary records. Fields, supporting lookups, and embedded invoice/order lines are bundled. A new execution transferring the same records creates usage again.
Read the exact usage rates or learn why sales, payments, and invoice totals differ.