Migrate from BoldTrail to HighLevel

BoldTrail contacts map 1:1 to HighLevel contacts. BoldTrail's contact-ownership restriction means only contacts you personally own or imported are exportable via API — team contacts owned by the brokerage must be extracted separately or flagged as inaccessible before migration runs.

BoldTrail's flat tag taxonomy maps directly to HighLevel tags. Tags that encode Smart Campaign attribution or source channels become HighLevel tags, but tag inheritance on child contacts requires workflow recreation since HighLevel workflows are the only mechanism for propagating contact attributes.

BoldTrail companies map to HighLevel companies with direct field mapping for name, website, address, industry, and employee count. Parent-child company hierarchies in BoldTrail map to HighLevel's parent company lookup, which must be resolved before child records load. During migration, ensure that each parent company exists in HighLevel before creating child records, to avoid orphaned entries and maintain reporting accuracy.

BoldTrail Listings have no native equivalent in HighLevel — they translate to Opportunities with the property address stored in a custom field (Listing_Address__c) and the MLS number in another (MLS_Number__c). Each BoldTrail deal linked to a listing creates an Opportunity with the listing address, price, and status carried over as custom fields on the Opportunity.

BoldTrail deals not tied to a listing — referral fees, admin fees, coaching engagements — map directly to HighLevel Opportunities. Pipeline names in BoldTrail translate to HighLevel pipeline names, and deal stages translate to opportunity stage names via value mapping per pipeline.

BoldTrail pipelines and their stages map to HighLevel pipelines and stages on a 1:1 basis. Each BoldTrail pipeline becomes a HighLevel pipeline, and each stage name is mapped by value. Stage probability percentages are preserved as custom fields on the opportunity if they exist in BoldTrail.

BoldTrail AI Lead Scoring has no native equivalent in HighLevel. The score migrates as a custom numeric field (AI_Lead_Score__c) on the HighLevel contact record. The score reflects BoldTrail's 90-day behavioral model — it is preserved as-is for reporting continuity and can feed HighLevel workflow conditions if your admin builds a scoring workflow.

BoldTrail Smart Campaigns encode drip sequences, behavioral triggers, and lead nurturing tied to listing views and property searches. HighLevel Workflows are the automation engine but they cannot import Smart Campaign definitions — the logic must be rebuilt. We export your BoldTrail Smart Campaign configuration as a rebuild reference document for your HighLevel admin.

BoldTrail tracks lead behavior on IDX property searches — pages viewed, searches saved, listings favorited — directly in the contact timeline. HighLevel has no IDX or website behavior tracking native object. This data migrates as a note attachment on the contact record (BoldTrail_IDX_Activity__c) and as tags for property type interest, but the granular behavioral timeline is not reconstructable in HighLevel.

BoldTrail tasks and call/email activities map to HighLevel tasks with original timestamps, owners, and parent contact links preserved. Notes attached to contacts migrate as HighLevel notes. Owner resolution is by email match to HighLevel users — unmatched owners are flagged before migration commits.

BoldTrail custom properties on contacts, companies, and deals create corresponding custom fields in HighLevel. Field type is inferred from BoldTrail's data (text, number, pick-list, date) and recreated with the matching type. Pick-list custom properties in BoldTrail require value-by-value mapping in HighLevel's custom field options.

BoldTrail lead sources (Zillow, Realtor.com, Facebook Lead Ads, referral, etc.) are stored as a contact property. These map to HighLevel contact tags in most cases, preserving the source attribution. For reporting purposes, a custom pick-list field (Lead_Source__c) is also created so source data is queryable in HighLevel pipelines.