Migrate from Brokerkit to Pipedrive

Brokerkit's agent profile maps directly to Pipedrive's Person object. Name, email, phone, address, and job title fields translate field-by-field with no transformation logic required. Brokerkit agent status (Active, Inactive, Prospect) is preserved as a custom pick-list on the Person record in Pipedrive, ensuring that agent lifecycle information remains queryable after migration.

Brokerkit's brokerage entity maps to Pipedrive's Organization object. Brokerage name, website, industry, and address fields map directly using the same data types. Multi-office brokerages with parent-child relationships translate via Organization's parent_id field in Pipedrive, preserving the hierarchical structure. The parent Organization must be migrated first to resolve circular reference issues during the data load.

Brokerkit's agent-to-brokerage many-to-one relationship maps to Pipedrive's Person.organization_id lookup. Each Brokerkit agent has one primary brokerage assignment that becomes the organization_id on the Person record. Secondary brokerage associations that exist in Brokerkit are preserved as custom fields on the Person record, allowing teams to maintain a complete brokerage association history without data loss.

Brokerkit's real estate transaction records map to Pipedrive's Deal object. Transaction status, close date, commission amount, and agent assignment all translate to standard Pipedrive Deal fields. Brokerkit's transaction ID is stored as Source_System_ID__c on the Pipedrive Deal for traceability back to the original Brokerkit record, enabling audit trails and cross-system reporting after migration completes.

Brokerkit's recruitment pipeline stages (Applied, Interviewing, Offered, Hired, Active, Retained) map to Pipedrive Pipeline stages. Each Brokerkit recruitment pipeline becomes one Pipedrive Pipeline with ordered stages representing the agent journey. Stage probability values are assigned per stage name during migration configuration, and stage-entered timestamps are preserved as custom datetime fields on the Deal for historical reporting.

Brokerkit's transaction pipeline stages (Pre-Market, Listed, Under Contract, Pending, Closed Won, Closed Lost) map to a separate Pipedrive Pipeline. Each stage's success probability is set during Pipedrive pipeline configuration. Stage-entered timestamps are preserved as custom datetime fields on the Deal.

Brokerkit's recruiting activity log (calls, emails, notes, tasks) maps to Pipedrive Activities. Each activity type maps to Pipedrive's activity_type field (call, email, meeting, task). Original timestamps, owners, and linked agent or deal references are preserved in the Pipedrive activity record, maintaining the full activity history for each agent and transaction throughout the migration.

Brokerkit's notes on agents, transactions, and brokerages migrate to Pipedrive Notes. Notes are attached to the corresponding Person, Organization, or Deal record based on the entity they reference in Brokerkit. Rich-text formatting from Brokerkit is preserved as plain text in Pipedrive's Note object, ensuring that note content remains readable even if advanced formatting is simplified during the migration.

Brokerkit custom fields on agent profiles that have no direct Pipedrive equivalent (e.g., license number, MLS ID, referral source) are created as Pipedrive custom fields on the Person object using the matching field type (text, numerical, single option, etc.). Pipeline-specific fields are scoped to the relevant Pipedrive pipeline.

Brokerkit custom fields on transaction records (e.g., property address, listing type, commission split) migrate as Pipedrive custom fields on the Deal object. Date and monetary field types from Brokerkit map directly to Pipedrive's date and monetary custom field types, maintaining the original data precision. Pipeline-specific custom fields are scoped to the relevant Pipedrive pipeline during configuration.

Brokerkit tags on agents and transactions map to Pipedrive Labels. Labels exist independently per entity type in Pipedrive (Person Labels, Organization Labels, Deal Labels), so agent tags land in the Person Labels section while transaction tags appear in Deal Labels. Labels are created automatically during migration with the same color-coding applied where Pipedrive's label color field supports it.

Brokerkit users are matched to Pipedrive users by email address to preserve ownership assignments during migration. Unmatched Brokerkit owners are flagged before migration begins — these users are either invited to create Pipedrive accounts or assigned to a fallback Pipedrive user. No record lands in Pipedrive without a valid OwnerId, ensuring that all migrated data maintains proper access controls and accountability.