Migrate from Brivity to Nutshell

Brivity People records map 1:1 to Nutshell People. Nutshell People include first name, last name, email, phone, address, and a notes section. Owner is resolved by email match to Nutshell users. Records without a matched owner are flagged pre-migration for fallback assignment.

Brivity Company records map directly to Nutshell Company. The Company name, domain, industry, employee count, and revenue fields migrate as direct mappings. Nutshell's Companies link to People via a one-to-many relationship — multiple associated People records are linked after the Company record is created.

Brivity allows a Person to be associated with multiple Companies (N:N). Nutshell links a Person to a single primary Company and supports secondary Company links via a linked-company attribute. We map the primary (most recently modified) Company as the primary link and surface additional associations as a custom field on the Person record for manual reconciliation.

Brivity Opportunities map to Nutshell Deals — name, value, stage, and expected close date are the core fields. Brivity's opportunity status (Active, Won, Lost, Pending) maps to Nutshell Deal stage values. The migration plan includes a value map between Brivity status labels and Nutshell stage names defined by your team before migration runs.

Brivity Tasks migrate as Nutshell Activities with Type='Task'. Original task subject, due date, completion status, and owner are preserved. Completed flag maps to Nutshell's completed=true on the Activity record. We also set the original task type (Call, Email, General) as a custom field for reporting parity.

Brivity call logs, email logs, and meeting records migrate as Nutshell Activities with Type='Call', 'Email', or 'Meeting' respectively. Original timestamps, duration, and owner are preserved. Nutshell Activities are logged at the Person or Deal level — we link each activity to the primary Person record and optionally to the related Deal if an opportunity association exists in Brivity.

Brivity custom fields on People records create equivalent custom fields in Nutshell People. Supported field types (text, number, date, choice) map directly. Checkbox fields from Brivity become Nutshell custom choice fields with Yes/No options. We pre-create all target custom fields before the migration and validate field type compatibility before committing records.

Brivity custom fields on Company records create equivalent custom fields in Nutshell Company. Number and text fields map directly. Date fields use ISO 8601 format in both platforms. Choice fields require a value-by-value map of Brivity pick-list options to Nutshell choice options — we surface any mismatches before the migration runs.

Nutshell does not support custom fields on Deals. Brivity Opportunity custom fields are mapped to a custom field on the related Person record (e.g., Opportunity_Custom_DealType__c) with the opportunity name and value embedded as a text string for reference. This is surfaced in the migration plan so your team can decide whether to recreate these as separate deal notes or accept the Person-level reference.

Brivity owner assignments migrate by resolving the owner email against Nutshell user accounts. Matched owners assign directly. Unmatched owners are flagged in a pre-migration report — your team either creates the Nutshell user first or designates a fallback owner before the full migration runs. This prevents records landing with a null owner in Nutshell.

Brivity's IDX websites, listing feeds, and showing-request data have no direct Nutshell equivalent. We export all listing-related records as a structured CSV for reference and flag the absence of an IDX tool in Nutshell's feature set so your team can plan separately for a listing integration (e.g., list hub, ShowingTime, or similar).

Brivity's transaction management module (contracts, transaction IDs, commission splits, closing dates) has no Nutshell equivalent — Nutshell Deals do not support transaction-level metadata natively. We export transaction records as a structured CSV and note that commission tracking may need to be rebuilt in a spreadsheet or a dedicated commission tool post-migration.