Migrate from Brivity to Twenty CRM

Brivity contact records map directly to Twenty CRM People. The People object holds name, email, phone, job title, and a companyId relation. Brivity contacts without a primary company get created in Twenty with the companyId field left empty for manual assignment or linking.

Brivity company records map directly to Twenty CRM Companies. The Companies object in Twenty stores name, domain, industry, employee count, and annual revenue fields. Parent-company hierarchies present in Brivity translate into Twenty's hierarchical company model when applicable, preserving organizational structures across the migration.

Brivity deal and transaction records map to Twenty CRM Opportunities. The Opportunities object captures deal name, pipeline stage, monetary amount, expected close date, and relational links to People and Company records. Pipeline stage values from Brivity translate directly to Twenty's stage pick-list options on each Opportunity record.

Brivity tasks and follow-up items map to Twenty Tasks. Tasks in Twenty support due dates, assignees, and completion status fields. Each task can be linked to a People, Companies, or Opportunities record through relations, preserving the contextual connection between follow-up activities and the relevant CRM records.

Brivity notes and call logs map to Twenty Notes. Notes in Twenty can be attached to People, Companies, Opportunities, or any custom object. The original creation timestamps and full note body text are preserved exactly as they existed in Brivity, maintaining the historical context of every client interaction.

Brivity lead source properties indicating how each contact was generated have no direct standard field equivalent in Twenty's People object. We create a custom field (lead_source__c) on the People object in Twenty's Data Model settings and migrate the original lead source values so your attribution data remains intact and reportable after migration.

Brivity referral type properties tracking whether contacts originated from past client referrals, sphere of influence sources, or other categories migrate as a custom pick-list field (referral_type__c) on the People object. This preserves the referral attribution logic your team relies on for analyzing lead sources in Twenty CRM.

Brivity transaction and listing records do not have a native equivalent in Twenty's standard objects. We create a custom object (Transaction__c) in Twenty matching the fields Brivity stores (property address, listing price, status, agent, close date) and migrate all historical transaction records as records of that custom object.

Brivity pipeline stage names (e.g., 'New Lead', 'Showing Scheduled', 'Under Contract', 'Closed') map to Twenty Opportunity stage pick-list values. Each Brivia pipeline stage gets a corresponding Twenty stage entry so the deal progression logic reads correctly in Twenty's kanban view.

Brivity owner/agent assignments resolve by email match against Twenty workspace members. Unmatched owners are flagged before migration — your team either invites them to Twenty first or assigns their records to a fallback member. No record lands without an owner in Twenty.

Brivity activity history (logged calls, sent texts, email records) migrates as Twenty Tasks with type labels preserved. Each activity record links to the parent People or Opportunity record. Original activity timestamps are stored as custom datetime fields for reporting continuity.

Brivity Auto Plans and marketing sequences are workflow logic tied to contact lifecycle triggers. Twenty has a workflow builder, but the automation definitions do not transfer. FlitStack exports the full Auto Plan configuration as a JSON reference document your admin can use to rebuild the logic in Twenty's workflow settings.