Migrate from Brivity to Pipedrive

Brivity contacts map 1:1 to Pipedrive Persons. The Person object in Pipedrive stores name, email, phone, and address as standard fields. Brivity agent-specific fields (license number, transaction role) migrate as custom fields on the Person record. Owner resolution uses email match against Pipedrive users — unmatched owners are flagged before migration.

Brivity companies map to Pipedrive Organizations. Pipedrive Organizations store company name, domain, address, and industry as standard fields. Parent-child company hierarchies in Brivity map to Pipedrive's Parent Organization field. Multi-company contacts need a primary-company rule applied before Person records are created.

Brivity deals map to Pipedrive Deals with the pipeline and stage values mapped value-by-value. The deal name, value (amount), expected close date, and owner transfer directly. Pipedrive Deals inherit all deal custom fields for Leads automatically when a lead is converted, which affects how Brivity listing fields migrate if used on leads.

Brivity pipelines map 1:1 to Pipedrive Pipelines. Each Brivity pipeline stage becomes a Pipedrive stage in the corresponding pipeline. Stage order, probability, and forecast category are preserved. Stage names may need manual renaming in Pipedrive if Brivity uses real estate–specific stage labels (e.g., 'Under Contract', 'Inspection Scheduled').

Brivity Listings have no native Pipedrive equivalent — Listings object fields migrate as custom fields on the Deal object, tagged with a 'Listing Source' prefix for identification. Property address fields map to concatenated text fields or address custom fields on the Deal. Listing status fields require value mapping if Brivity uses status labels not present in Pipedrive.

Brivity Transaction records (commission, closing date, referral partner) have no Pipedrive equivalent — they migrate as a custom field group on the Deal object. Transaction role fields (listing agent, buyer agent, dual agent) become picklist custom fields. Referral partner details become text custom fields on the Deal.

Brivity auto plans and action sequences are not portable to Pipedrive because they use Brivity's event-trigger model. FlitStack exports the plan definitions as a structured JSON document and a step-by-step narrative so your Pipedrive admin can rebuild equivalent Automations and Sequences. The export is delivered before migration day.

Brivity call logs, email records, and meeting records map to Pipedrive Activities. Each activity type gets a corresponding Pipedrive Activity type field (call, email, meeting). Original timestamps, activity owners, and linked Person or Deal associations are preserved. Activities without a linked record are imported as standalone activities.

Brivity notes map to Pipedrive Notes linked to Person, Organization, or Deal records. Rich-text formatting is preserved where Brivity supports it. If Brivity notes contain embedded images, those are extracted, downloaded, and re-uploaded as Pipedrive file attachments with the note re-linked.

Brivity file attachments on contacts, companies, or deals are exported and re-uploaded to Pipedrive Files, then linked to the corresponding record. Pipedrive file size limits (25 MB per file by default) apply — oversized files are flagged for manual review. Inline images in notes are handled as part of the note migration step.

Brivity tags on contacts, companies, and deals map to Pipedrive Labels. Label names transfer as-is. Pipedrive Labels are entity-scoped (Person, Organization, Deal) — multi-entity tags are split by entity type and applied as separate label sets on each record. If a Brivity contact carries both a 'Residential' and 'Commercial' tag across different objects, Pipedrive receives each tag applied to the corresponding entity independently.

Every Brivity custom field on any object becomes a Pipedrive custom field on the equivalent object. Pipedrive custom field keys are generated as 40-character hashes in the API — we map by display name during import and verify type compatibility (text, number, date, picklist, etc.). Picklist custom fields require value-by-value mapping if Brivity uses labels not in Pipedrive's default set.