Migrate from BoldTrail to Pipedrive

BoldTrail contacts map to Pipedrive People. Standard fields (name, email, phone, address) move directly. BoldTrail properties like lead_source and drip_status have no Pipedrive equivalent — those become custom fields on the Person record during migration. Owner resolution happens by email match against Pipedrive users.

BoldTrail companies map to Pipedrive Organizations. BoldTrail's brokerages and real estate offices become Organizations in Pipedrive — there is no separate brokerage entity in Pipedrive's data model, so those records collapse into the Organization object with a custom field flagging the original BoldTrail type.

BoldTrail stores the primary company as a property on the contact record. In Pipedrive, each BoldTrail company must exist as an Organization before the contact migrates — we sequence the migration to create Organizations first, then link People to them via org_id. BoldTrail N:N contact-company associations surface as secondary Organization links in Pipedrive.

BoldTrail deals map to Pipedrive Deals. BoldTrail deal_name becomes Deal title, amount maps directly, close_date maps to expected_close_date. The pipeline and stage concepts are preserved — BoldTrail pipelines map to Pipedrive pipelines, stage names map value-by-value to Pipedrive stage values per pipeline. BoldTrail deal properties (listing address, price, type) become custom fields on the Pipedrive Deal.

BoldTrail deal pipelines map 1:1 to Pipedrive Pipelines. If BoldTrail has three pipelines (Listings, Buyers, Leases), FlitStack creates three Pipelines in Pipedrive with matching names. Each pipeline in Pipedrive then needs its own stage configuration — stage names, probabilities, and forecast categories are mapped value-by-value from BoldTrail.

BoldTrail transaction stages (Active Listing, Pending Sale, Closed, etc.) map to Pipedrive stage values per pipeline. We preserve stage-entry timestamps as custom datetime fields on the Pipedrive Deal so reporting continuity is maintained. The value mapping is defined per pipeline since BoldTrail pipelines may use different stage sets.

BoldTrail stores listing address, price, bedrooms, bathrooms, property type, square footage, and listing status as native fields on deals. Pipedrive has no native property fields. FlitStack creates custom fields for each — Listing_Address__c, Listing_Price__c, Property_Type__c, Bedrooms__c, Bathrooms__c, Square_Footage__c, Listing_Status__c — before the migration run so the mapping is valid from the start.

BoldTrail deal records carry an assigned listing agent name and a BoldTrail owner ID. Pipedrive's deal model does not have a native agent assignment field — we carry both values into Pipedrive as custom text fields (Listing_Agent_Name__c and BoldTrail_Owner_ID__c) so the original attribution is preserved for reference after cutover.

BoldTrail calls, emails, meetings, and notes map to Pipedrive Activities. The BoldTrail activity type becomes a Pipedrive activity_type value (call, email, meeting, or note). Original timestamps, owners, and parent-record links (deal_id or person_id) are preserved. Pipedrive's Activity object is a unified container for all engagement history.

BoldTrail file attachments on contacts, companies, and deals are re-uploaded to Pipedrive's Files section. Files are linked to the parent record (deal, person, or organization) using Pipedrive's file attachment API. Inline images in BoldTrail notes are downloaded and rehosted. BoldTrail file IDs are stored in a custom Pipedrive field for traceability.

BoldTrail owner IDs are resolved by email match against Pipedrive user accounts. Each BoldTrail user must have a corresponding Pipedrive user before the migration runs — FlitStack flags unmatched owners and suggests inviting them to Pipedrive first. Unresolved owners default to a designated Pipedrive admin user with a note on the record.