Migrate from Brivity to Microsoft Dynamics 365 Sales

Brivity stores all people as Contact records — no separate Lead object exists. During migration, FlitStack AI evaluates each Brivity Contact's status field: Contacts with a closed-won Transaction route to Dynamics 365 Lead; all others also route to Lead for manual qualification in Dynamics. The original Brivity contact status is preserved as a custom field for reporting continuity after go-live.

Brivity Companies represent brokerages and individual brokerages under which agents operate. These map 1:1 to Dynamics 365 Accounts. The Brivity Company ID is stored as a custom field on the Account for delta-run de-duplication and traceability back to the source system.

Brivity Transactions track a real estate deal from offer through close, capturing MLS listing reference, commission split, and closing status. Dynamics 365 Opportunities track deal amount, stage, probability, and close date. FlitStack AI maps the transaction name to Opportunity Name, total commission to Amount, and closing status to a custom pick-list field since Dynamics Opportunity Stage is not 1:1 with Brivity transaction statuses.

Brivity Listings sourced from IDX have no native equivalent in Dynamics 365. FlitStack AI creates a custom BrivityListing table in Dataverse to store MLS number, property address, listing status, and listing agent. The Opportunity record links to the listing via a lookup relationship established during migration.

Brivity activity records (calls logged, emails sent, appointments scheduled, notes attached) map to Dynamics 365 equivalents. FlitStack AI preserves original timestamps, activity type, and the linked Contact or Transaction ID as a lookup on the Task or Note record. Activity owners are resolved by email match to Dynamics 365 users.

Brivity custom properties on Contact, Company, and Transaction map to custom fields in Dynamics 365. Text properties become Text fields, numbers become Decimal or Whole Number fields per value range, and pick-list properties become Option Sets. Each custom field is created in the target Dynamics environment before the full migration run commits data.

Brivity agents assigned to teams with lead-routing roles have no 1:1 in Dynamics 365. FlitStack AI maps each unique Brivity agent email to a Dynamics 365 SystemUser by email match. Brivity teams are represented as Dynamics 365 Teams, and agent roles are approximated using Security Roles — your Dynamics admin assigns the appropriate role profile after migration.

Brivity Auto Plans and lead-routing sequences are automation logic stored in Brivity's engine. Dynamics 365 has no native equivalent for cross-object automation. FlitStack AI does not migrate these. We export a JSON or PDF summary of every Brivity Auto Plan — trigger conditions, action steps, and timing rules — as a reference document your Dynamics admin uses to rebuild equivalent flows in Power Automate.

Brivity files attached to contacts, transactions, or listings are downloaded and re-uploaded to the Dynamics 365 record's Notes section or to the associated SharePoint document library if SharePoint integration is enabled. File size limits of 25 MB per file apply in Dynamics 365.

Every Brivity record carries an internal ID that has no meaning in Dynamics 365. FlitStack AI stores this as a text custom field (Source_ID__c) on every target table so the migration tool can de-duplicate on delta runs, trace records back to Brivity for reconciliation, and support rollback if the migration does not pass validation.