Migrate from Brivity to HubSpot

Brivity contacts map 1:1 to HubSpot contacts. Owner assignment resolves by email match against HubSpot users. Brivity's lead status field migrates as a HubSpot contact property and can optionally gate enrollment in HubSpot workflows. This mapping preserves all contact details, including phone numbers, addresses, and custom fields, ensuring continuity of communication history.

Brivity companies map to HubSpot companies. Brivity's company domain, phone, address, and industry fields map to their HubSpot counterparts. Multi-address records collapse to the primary address; secondary addresses stored as a custom property. All company records retain original create dates and owner assignments, supporting accurate historical reporting after migration.

Brivity has no separate Lead object; leads are contacts with a lead status property. All Brivity leads migrate as HubSpot contacts. Teams wanting HubSpot Leads can route contacts by lifecycle stage using a post-migration workflow. This approach ensures that no lead data is lost during the transition.

Brivity transactions map to HubSpot deals. Deal name uses Brivity's transaction title or address. Deal stage names (Active, Under Contract, Closed) must be configured in HubSpot's deal pipeline to match Brivity's real estate stages before migration. Failure to pre-configure the stages will cause unmapped stage values in HubSpot, requiring post-migration cleanup.

Brivity transaction type (Buyer, Seller, Listing, Rental) has no HubSpot native equivalent. We create a Transaction_Type__c custom pick-list property on the Deal object and map each value directly. Stage order reconfigured to reflect real estate lifecycle. This ensures consistent categorization of deals and enables filtering by transaction type in reports and dashboards.

Brivity's Property object (listing address, MLS number, list price, beds, baths) has no HubSpot equivalent. Listing address maps to a Listing_Address__c custom property on Deal; MLS number maps to MLS_Number__c; property details stored in deal description or additional custom properties.

Brivity tasks, call logs, and notes map to HubSpot engagements with original timestamps and owner links preserved. Task status (completed, deferred, waiting) maps to HubSpot engagement state. Completed tasks appear as logged engagements on the contact record. This ensures that all communication history is searchable and attributable to the correct owner after migration.

Brivity file attachments on contacts, companies, or transactions are re-uploaded to HubSpot Files and associated with the corresponding record. File size limits per HubSpot's storage tier apply. Inline images in notes are downloaded and rehosted. This preserves document context and maintains links to related contacts, companies, or deals.

Brivity owner and agent records resolve by email match against HubSpot users. Unmatched owners are flagged before migration; you either invite them to HubSpot first or assign their records to a designated fallback user. This prevents orphaned records and ensures every activity links to an active HubSpot user for accountability.

Brivity Action Plans (automated follow-up sequences, lead response triggers, task creation rules) have no HubSpot equivalent and do not migrate. FlitStack exports Action Plan definitions as a reference document your HubSpot admin uses to rebuild triggers in HubSpot's workflow builder.

Brivity lead source values (Website, Referral, Zillow, Realtor.com, etc.) map to HubSpot's hs_analytics_source standard property or a custom lead source pick-list depending on your HubSpot tier. Custom lead sources require value-by-value mapping. This ensures accurate source attribution in reports and supports workflow enrollment based on lead origin.

Brivity's internal record IDs are stored as Source_CRM_ID__c custom properties on HubSpot contacts, companies, and deals. This enables delta-run de-duplication and traceability back to the source Brivity record. During subsequent data refreshes, the ID mapping allows FlitStack to identify and update existing records without creating duplicates.