Migrate from Brokerkit to HighLevel

Brokerkit agent records map directly to HighLevel Contacts. Agent name, email, phone, address, and all standard contact fields migrate as-is. Brokerage's internal agent ID is preserved as a custom field (Brokerkit_Agent_ID__c) for traceability and delta-run de-duplication. The mapping also retains the created date, last activity date, and any tags. Custom fields created in Brokerkit are added to the Contact record as text, pick-list, or date fields to preserve agent-specific metadata.

Brokerkit brokerage company records map to HighLevel Companies. Company name, address, phone, website, and industry fields migrate directly. Multi-location brokerages where Brokerkit stores each office as a separate company record map to individual HighLevel Company records linked by a common parent if parent-child hierarchy is present.

Each Brokerkit recruiting pipeline becomes a separate HighLevel Opportunity pipeline. Brokerkit stage names (e.g., 'New Lead', 'Interview Scheduled', 'Offer Extended', 'Active Agent') map to HighLevel Opportunity stage values within each pipeline. Stage ordering and probability weights are translated based on Brokerkit's stage configuration.

Brokerkit recruiting-stage pick-list values map to corresponding HighLevel Opportunity stage names. Where HighLevel's default stages don't match Brokerkit's real estate terminology (e.g., 'License Verified', 'E&O Signed'), we create custom stage names during setup. Stage-entry timestamps from Brokerkit are preserved as custom datetime fields on the Opportunity record.

Brokerkit agent-specific properties — license number, MLS ID, real estate license state, team assignment, recruiting source, referral source — migrate as named custom fields on the HighLevel Contact record (e.g., License_Number__c, MLS_ID__c, Recruiting_Source__c). Field types match the source (text, pick-list, date, number) to preserve data fidelity.

Brokerkit follow-up tasks and recruiting activities migrate as HighLevel Tasks attached to the Contact record. Original due dates, task owners, and completion status are preserved. Activity type (call, email, meeting, note) is encoded in the Task's Type or custom field for workflow trigger compatibility.

If Brokerkit stores closed transactions or commission records as deals, these migrate to HighLevel Opportunities with the Closed Won stage. Transaction amount fields map to Opportunity Value, and close date maps to the Opportunity close date field. Deal metadata like commission rate, referral source, and transaction notes transfer as custom fields. The deal ID is kept for reconciliation, and linked contacts (buyer, seller, agent) are attached via Opportunity contact roles.

Brokerage notes on agent records migrate as HighLevel Notes attached to the Contact. Rich-text formatting is preserved where the source format is compatible. File attachments are re-uploaded to HighLevel's file storage and linked to the Contact record. If notes contain images or tables, those elements are extracted and stored as file attachments. Mention of dates, contacts, or tasks in the note body is linked to HighLevel records for consistency.

Brokerkit tags applied to agent or company records migrate as HighLevel Tags. Both platforms support multiple tags per record, so the 1:1 mapping is direct. Tag names are preserved exactly to avoid breaking any HighLevel workflow triggers that reference tag conditions.

If Brokerkit stores agent data as a distinct custom object separate from standard contacts, we create a corresponding HighLevel Custom Object. Custom object relationships (agent-to-brokerage, agent-to-team) are recreated as relationship fields in HighLevel. Custom object field types are mapped individually with type-aware transformation.

Brokerkit follow-up sequences and agent nurturing workflows do not migrate. They must be rebuilt in HighLevel's Workflow engine. We export Brokerkit workflow definitions as a structured document to serve as a rebuild reference for your HighLevel admin or our implementation team.

Brokerkit reports and recruiting dashboards do not migrate. Underlying data (agent pipeline, stage history, activity logs) does migrate — the records driving those reports will be available in HighLevel for report recreation. We provide a data dictionary mapping Brokerkit report fields to their HighLevel equivalents.