Migrate from Brivity to HighLevel

Brivity stores all people — leads, prospects, and past clients — in a single contacts object with no native lead/contact split. HighLevel uses a unified contacts object as well. We migrate every Brivity contact record directly, preserving the original create date as a custom datetime field and the Brivity record ID as a custom text field for delta-run traceability. Tags, source attribution, and custom field values transfer as-is or map to new HighLevel custom fields.

Brivity company records map directly to HighLevel company records. Company names, domains, addresses, industry classifications, and employee counts transfer directly. Brivity's company record may include custom real estate fields such as brokerage name, license number, or market area — these migrate as custom fields on the HighLevel company record. Contacts are linked to companies in both systems using a lookup relationship.

Brivity deal opportunities map to HighLevel opportunities with direct field transfers for name, amount, stage, close date, and owner. The pipeline and stage names are mapped value-by-value to HighLevel's pipeline stage values. Brivity deal probability is stored per-stage and re-applied on the HighLevel side. If Brivity deal records include real estate-specific custom fields (property type, MLS number, showing status), these migrate as custom fields on the HighLevel opportunity.

Brivity pipelines contain customizable stage names, stage weights, and probability values. HighLevel uses a single pipeline object with stages that can each carry a probability value and trigger workflow events. If Brivity has multiple pipelines (available on higher plans), each maps to a separate HighLevel pipeline. Stage names are mapped value-by-value during migration setup, and probability is preserved per stage. Pipeline-level filters in Brivity that segment by agent, team, or region require custom field creation in HighLevel for equivalent segmentation.

Brivity activity records — calls, appointments, follow-up tasks, and texts — map directly to HighLevel task records. Each task preserves its original creation timestamp, assigned owner, due date, status, and body content. HighLevel tasks can trigger workflows, which is useful for rebuilding Brivity's follow-up sequences in HighLevel's automation engine post-migration.

Notes attached to Brivity contacts, companies, or opportunities migrate as HighLevel notes, preserving the original author, creation date, and body content. HighLevel notes display inline within the contact or company record. Plain-text and formatted notes transfer directly; any rich-text formatting is preserved in the note body.

Brivity real estate properties are stored as custom fields on contact and opportunity records — MLS number, property address, listing status, showing count, and CMA value are common examples. These have no native HighLevel equivalent. We create matching custom fields on the appropriate HighLevel object and migrate the values directly. If the team tracks multiple properties per contact, we assess whether a HighLevel custom object is warranted for the property data.

Brivity's transaction management tracks deal milestones, contract status, and document references tied to a real estate closing. HighLevel has no native transaction object. We assess transaction record volume and field count: low-volume transactions migrate as custom fields on the related opportunity; high-volume or complex transaction setups are migrated as a dedicated HighLevel custom object with a lookup to the opportunity record.

Brivity includes a reputation management feature for tracking and responding to client reviews. HighLevel has its own native reputation management module. Review data and review-response history cannot be exported from Brivity in a transferable format — these records are skipped. We document this gap and recommend activating HighLevel's reputation management module from day one of the new account.

Brivity IDX websites pull live MLS listing data directly into the platform and render property search pages, listing alerts, and showing request forms. HighLevel has no native IDX integration. The website domain routing cannot be transferred. We export listing records and lead routing data as a CSV for manual rebuild in HighLevel's funnel builder or a dedicated IDX provider. The domain and DNS configuration requires manual update outside the migration scope.

Any Brivity custom field that does not map to a standard HighLevel field — such as custom dropdown values, multi-select lists, or text fields with business-specific semantics — is recreated as a matching HighLevel custom field on the appropriate object. We preserve field type, pick-list values, and default values during the migration. Custom field definitions are reviewed before migration begins to avoid type mismatches (e.g., a Brivity date field that HighLevel might interpret as text without explicit type mapping).

Brivity users and owners are matched to HighLevel users by email address resolution. Before migration, we pull the full Brivity user list, match each to a HighLevel user by email, and flag any Brivity owner without a HighLevel counterpart for reassignment. Records assigned to unmatched owners are staged with a fallback owner designation pending team assignment in HighLevel. This ensures every migrated record lands with a valid owner.