Migrate from BoldTrail BackOffice to Pipedrive

BoldTrail contacts map 1:1 to Pipedrive Persons. Name, email, phone, address, and job title fields transfer directly via standard field mapping. Owner resolution happens by email match against existing Pipedrive users. Contacts without a valid email address are imported with a generated placeholder email and flagged in the migration report for manual review and cleanup after cutover.

BoldTrail companies map to Pipedrive Organizations. Company name, domain, address, and industry field transfer directly. A BoldTrail contact's primary company links to the Organization via Pipedrive's org_id field on the Person record. Multi-location companies split into multiple Organizations with a parent-org reference custom field.

BoldTrail transactions are the core migration object — they have no direct Pipedrive equivalent and become Pipedrive Deals. The deal name defaults to 'Property Address — Close Date'. Transaction value maps to deal value. Transaction stage (Pending, Under Contract, Closed) maps to a Pipeline Stage value in Pipedrive. A Transaction ID custom field preserves the BoldTrail source reference for reconciliation.

BoldTrail transaction statuses map to Pipedrive stage names per pipeline. Common mappings: 'Pending' → 'First Contact', 'Under Contract' → 'Qualification', 'Inspection' → 'Proposal', 'Closed Won' → 'Won'. Mapping is configurable before migration based on your BoldTrail stage configuration. Probability defaults are applied per Pipedrive stage settings.

BoldTrail commission split percentages and agent split assignments have no native Pipedrive field. We create a Commission_Split__c custom field on both Person (agent) and Deal (transaction). Commission plan names are preserved as a text reference field. Brokerages use this data to reconcile payouts outside Pipedrive or via a commission add-on.

BoldTrail agents who are also CRM users map to Pipedrive Persons with a link to the Pipedrive User record. Agent-specific fields (license number, commission plan, onboarding checklist status) become custom Person fields. Non-CRM agents (transaction coordinators, admins) are exported as a separate agent roster CSV for manual Pipedrive user setup.

BoldTrail call logs, emails, and meeting records map to Pipedrive Activities with type differentiation (call, email, meeting). Original timestamps, duration, and owner are preserved. Activities link to the corresponding Person or Deal record via the activity's subject line matching or BoldTrail's record ID in a custom reference field.

BoldTrail transaction notes and person notes map to Pipedrive Notes attached to the relevant Person or Deal. Rich-text formatting is preserved as HTML where BoldTrail supports it. Notes with @mention to agents include the BoldTrail user ID as a reference for owner mapping.

BoldTrail transaction documents and attachments are downloaded and re-uploaded as Pipedrive Files attached to the corresponding Deal. File size limits apply (Pipedrive's per-file limit is 150MB). Large documents or PDF bundles may be zipped before upload. Documents are reattached by matching the BoldTrail transaction ID to the migrated Deal.

BoldTrail accounting ledger entries, agent billing records, and QuickBooks sync data have no Pipedrive equivalent. FlitStack exports these as a structured CSV and JSON reference file for your accounting team to reconcile in your target accounting tool. This data is outside the CRM migration scope.

BoldTrail custom transaction properties (e.g., 'Property Type', 'MLS Number', 'HOA Fee', 'Close Date') are identified during the pre-migration audit. Each custom property is created as a matching Pipedrive custom deal field with the appropriate type (text, numeric, date, currency, or picklist). Picklist value mappings are applied per field.

BoldTrail workflow rules (transaction stage change triggers, commission recalculation rules, document generation triggers) do not have a Pipedrive equivalent and are not migrated. FlitStack exports a JSON representation of BoldTrail workflow definitions with trigger conditions and actions so your Pipedrive admin can rebuild them using Pipedrive Automations and Smart Docs.