Migrate from Brivity to Freshsales

Brivity People records split by status at migration time. Active leads and unconverted prospects route to Freshsales Lead. Clients with closed transactions or a defined Account link route to Freshsales Contact. The split rule is configurable — default is anyone with a Deal in Closed Won stage becoming a Contact.

Brivity Company maps directly to Freshsales Account. The primary Company contact in Brivity becomes the primary contact link in Freshsales. Parent-company hierarchies map to Freshsales Parent Account relationships; circular references are flagged before migration. We also map the company's phone, website, and industry fields, and if a parent-company hierarchy exists, the top-level organization is imported first to ensure the Parent Account reference resolves correctly during the import sequence.

Brivity Deal maps 1:1 to Freshsales Deal. The deal name, amount, close date, and stage all transfer. Brivity pipeline names map to Freshsales Sales Flows. Deal owner resolves by email match against Freshsales users; unmatched owners are flagged before migration commits.

Each Brivity pipeline stage maps to a corresponding Freshsales deal stage value. Stage ordering, probability percentages, and forecast categories are re-applied in Freshsales. We preserve the original stage-entered timestamp as a custom datetime field (Stage_Entered_Date__c) for pipeline reporting continuity. If a Brivity pipeline stage has a custom probability or forecast category, those values are configured in Freshsales before records load, ensuring that deal health indicators reflect historical expectations.

Brivity activities map to Freshsales Sales Activities by type: calls become Calls, emails become Emails, meetings become Meetings, and general tasks become Tasks. Original timestamps, duration, owner, and the parent record link (contact or deal) are all preserved. Linked notes migrate as Freshsales Notes.

Brivity stores real-estate-specific deal fields like Property Address, Transaction Side (Buyer/Seller), Listing MLS Number, and Referral Source. Freshsales has no native real estate transaction object, so these migrate as custom text, pick-list, or number fields on the Deal object. Your Freshsales admin pre-creates these fields or we create them as part of the migration plan.

Brivity custom properties on People records — such as Lead Source, Preferred Neighborhood, or Budget Range — transfer to Freshsales as custom fields on Lead and Contact objects. Freshsales Growth supports basic custom fields; advanced field types (multi-select, lookup) require Pro or Enterprise. We map the field type to the closest Freshsales equivalent.

Brivity IDX website data and listing associations are platform-specific and have no equivalent in Freshsales's general CRM model. This data cannot migrate and must be managed separately in Brivity or rebuilt in a dedicated IDX/listing tool. We flag this clearly in the migration plan and do not include it in the record count for pricing.

Brivity file attachments on People, Company, and Deal records are downloaded and re-uploaded to Freshsales Files, linked to the corresponding record. Files larger than 25 MB are chunked or linked externally. Inline images embedded in Brivity notes are extracted, re-hosted, and the link is updated in Freshsales Notes.

Brivity owner and agent assignments resolve by email match against Freshsales Users. If a Brivity owner has no matching Freshsales user, the record is assigned to a fallback owner and flagged in the pre-migration validation report. Freshsales requires an active user for every owner assignment before records insert.