Migrate from Brokerkit to Nutshell

Nutshell's People object is a unified contact record that merges what other CRMs call 'contacts' and 'leads.' Brokerkit agent and contact records map directly to People. The Nutshell People record carries a 'Lead' flag for records in a pre-conversion state — we set this flag based on Brokerkit record type.

Brokerkit's company records (brokerage name, office name, franchise) map to Nutshell's Company object. If the Brokerkit company is the primary employer of an agent, we link it via Nutshell's 'Works for Company' relationship on the associated People record. We also map the address (street, city, state, postal code, country) to the Nutshell Company address fields. For franchises, we create separate Company records and link them to the parent brokerage.

Brokerkit's deal records representing agent-recruiting transactions map to Nutshell Deals. Nutshell Deals have customizable stage names and a dollar-value amount field — Brokerkit deal stage names are preserved through a value-mapping table during migration, and stage-entered timestamps are stored as custom datetime fields.

Brokerkit activities (calls via the built-in dialer, emails, and meetings) map to Nutshell's Activity records (Business plan and above) or Tasks (all plans). Original timestamps, owner email resolution, and the associated People or Deal link are preserved. If the activity references a dialer call, the duration and outcome fields map to Nutshell's call logging fields.

Brokerkit task and reminder records map directly to Nutshell Tasks. Status (open, completed), due date, and assigned owner (resolved by email) are preserved. Tasks linked to a specific Deal in Brokerkit retain that association via the DealId link in Nutshell.

Brokerkit notes attached to People, Companies, or Deals migrate as Nutshell Notes. Rich-text formatting in Brokerkit notes is preserved as plain-text in Nutshell Notes. If a note references an attachment, the file is downloaded and re-uploaded to Nutshell Files, and the Note record carries a link to the file.

Brokerkit custom field for agent license numbers maps to a Nutshell custom text field (License Number) on the People object. This field is created in Nutshell before migration runs. If the license applies to a specific deal (e.g., a recruiting deal requiring proof of licensure), the value is attached to the People record associated with that deal.

Brokerkit's recruiting_source field (values such as Indeed, LinkedIn, Referral, BrokerBoost) migrates as a Nutshell custom pick-list field on People. Value-by-value mapping preserves the exact source labels. If the pick-list values differ between Brokerkit and Nutshell, we flag mismatches before migration commits.

MLS identifier fields from Brokerkit migrate as custom text fields on the People record in Nutshell. The field is created as a custom text field named MLS_ID__c. If an agent has multiple MLS IDs, we store them as a comma‑separated list. Brokerkit typically stores this on the agent's brokerage‑association record — we attach the value to the Person record, and we preserve the Brokerkit record ID as Source_System_ID__c for traceability.

Brokerkit's dialer call logs (duration, outcome, recording link) map to custom fields on the Activity record in Nutshell. Nutshell's Activities module (Business plan) supports custom fields for detailed call logging. For lower plans, call metadata is stored as custom fields on the related Task record.

Brokerkit's owner_id on records maps to Nutshell's owner_id (the assigned User). We resolve Brokerkit owner email addresses against Nutshell user accounts by email match. Unmatched owners are flagged before migration — the team either creates a Nutshell user or assigns the record to a fallback owner before the full run commits.

Brokerkit tags (e.g., 'Top Producer', 'New Hire', 'Renewal Due') migrate as a custom multi-select text field (Tags) on the People object in Nutshell. Since Nutshell's native tag model is limited, we store all tags as a comma-separated string in a custom field for searchability and reporting.