Migrate from Brokerkit to Salesforce Sales Cloud

Brokerkit agents map 1:1 to Salesforce Contacts. Salesforce requires an AccountId lookup — agents without a primary brokerage company are attached to a default 'Unassigned Brokerage' Account record. Agent status (active, inactive, suspended) migrates as a custom pick-list field. This custom field is named Agent_Status__c and is added to the Contact object during schema preparation.

Brokerkit recruits in the recruiting pipeline route to Salesforce Leads. Brokerkit recruiting stage values map to Salesforce Lead Status via value-by-value mapping. Once a recruit converts to an agent, the Lead converts to a Contact with the original recruit history preserved as custom fields.

Brokerkit company records map to Salesforce Accounts. Brokerkit parent-child company relationships map to Salesforce ParentId. Multi-agent associations (Brokerkit N:N) collapse to one primary AccountId per Contact with additional relationships surfaced as Account Contact Relations. We also create Account Contact Relation entries for each secondary brokerage link, ensuring all historical associations are preserved and queryable in Salesforce reports.

Brokerkit deals and transactions map to Salesforce Opportunities. Each recruiting pipeline stage becomes a Salesforce Opportunity Stage value within the appropriate Sales Process and record type. Deal amount, close date, and owner map directly; pipeline-specific fields migrate as custom Opportunity fields.

Brokerkit recruiting pipelines become Salesforce record types. Each record type gets its own Sales Process so stage pick-list values are scoped correctly per recruiting track. We deliver a record-type and page-layout setup plan before data lands so your admin pre-creates the schema.

Brokerkit stage names map to Salesforce stage names value-by-value per record type. Stage probability and forecast category re-applied based on Salesforce defaults or your specified rules. Stage-entered timestamps preserved as custom datetime fields for reporting continuity. We also validate that each stage transition aligns with the defined Sales Process to avoid validation errors during opportunity updates.

Brokerkit agent licensing fields (license number, state, expiration) have no Salesforce standard equivalent. We create custom fields (License_Number__c, License_State__c, License_Expiration__c) on Contact and migrate values preserving the original data. Your admin assigns field-level security per profile. These custom fields are configured as required where applicable and can be included in validation rules to enforce compliance with state licensing regulations.

Brokerkit recruiting source values (referral, job board, event, etc.) map to Salesforce Lead Source pick-list. Unmapped values are flagged for admin review and either collapsed into an 'Other' value or added to the Salesforce pick-list before migration. We recommend documenting the final mapping in a shared reference sheet to streamline future lead source reporting and campaign attribution.

Brokerkit logged calls and emails map to Salesforce Tasks with Type='Call' or Type='Email'. Meetings map to Events with original start/end times preserved. Notes map to Salesforce Notes. Original timestamps, owners, and parent-record links (Contact, Lead, Opportunity) are preserved. Task and Event records also inherit the Salesforce record type associated with the parent object to maintain appropriate page layouts and automation triggers.

Brokerkit custom properties on agents and recruits become Salesforce custom fields on Contact or Lead. We create the custom fields in Salesforce Object Manager before migration, set appropriate field types (text, picklist, number, date), and map values directly. Properties with no Salesforce equivalent are flagged as no_equivalent and preserved as reference fields.

Brokerkit file attachments on agent or recruit profiles are downloaded and re-uploaded to Salesforce Files, linked to the corresponding Contact or Lead record. File size limits apply — Salesforce Files cap at 25MB per file; files exceeding this threshold are flagged for manual handling.

Brokerkit integrations with third-party tools (IDX, MLS, email providers) have no Salesforce equivalent. We document each active integration for your admin to reconfigure in Salesforce using AppExchange apps or native integrations. No integration settings or credentials transfer. We also provide a checklist of required OAuth scopes and endpoint URLs needed for each integration, helping your admin set up connections quickly after migration.