Migrate from BoldTrail BackOffice to HighLevel

BoldTrail contact records map directly to HighLevel contacts via 1:1 field mapping for name, email, phone, and address data. The contact-source tracking field in BoldTrail (capturing referral sources, website leads, etc.) migrates as a custom text field in HighLevel to preserve your historical lead source data and enable continued segmentation based on original acquisition channel.

BoldTrail agents become HighLevel user records with custom fields capturing license numbers, brokerage role, and onboarding status. Commission split rates migrate as custom number fields on the user record. BoldTrail's agent-to-contact relationship associations preserve in HighLevel through contact ownership assignments or tagging rules, maintaining the connection between agents and their assigned clients.

Each BoldTrail transaction maps to a HighLevel opportunity. Transaction status values (active, pending, closed) translate to corresponding pipeline stage values in HighLevel. The transaction address and property details migrate as custom fields on the opportunity since HighLevel's default opportunity schema is sales-focused and lacks real estate-specific property fields.

BoldTrail transaction phases (listing, contract, closing, closed) map to HighLevel pipeline stages. Each stage value requires explicit one-to-one mapping. Probability percentages associated with BoldTrail's stage model translate to HighLevel's stage probability settings if your team has configured those for forecasting purposes.

BoldTrail commission plans including split percentages, tiered rates, and flat fees have no direct HighLevel equivalent. We create a Commission_Plan custom object in HighLevel with fields for plan name, agent ID, split rate, and tier thresholds. Each agent's active plan links to their user record via a lookup field relationship.

BoldTrail transaction documents including contracts, disclosures, and addenda attach to the corresponding HighLevel opportunity record. Files are re-uploaded to HighLevel's attachment storage with original file names and upload timestamps preserved for audit continuity and record-keeping compliance.

BoldTrail's brokerage-level data including company name, address, and branding information becomes HighLevel company records. Multi-office brokerages create separate company records for each office location. HighLevel's company-contact associations mirror BoldTrail's primary contact linkage model to preserve organizational hierarchy.

BoldTrail onboarding checklists and transaction checklists cannot migrate directly as they represent automation constructs rather than data. We export checklist definitions as a structured reference document. Your HighLevel admin rebuilds them as workflow sequences using task actions and deadline triggers. We provide the exported structure including step names, order, required flags, and deadline rules to accelerate the rebuild.

BoldTrail's QuickBooks Online integration settings, chart of accounts mapping, and sync preferences do not transfer to HighLevel. We export your QuickBooks integration settings and account mappings as documentation for your team. After migration, your team configures an alternative accounting workflow using QuickBooks connector integrations via Zapier or Make, or a dedicated accounting integration app from the HighLevel marketplace.

BoldTrail custom transaction fields including MSA type, HOA fees, closing costs, and financing type migrate as custom fields on the HighLevel opportunity object. Field type mapping applies consistently: date fields convert to date pickers, currency amounts to number fields, and text to text. Required-field enforcement settings carry over based on BoldTrail's original field requirements.

BoldTrail agent custom properties such as DRE license numbers, MLS ID, and market area migrate as custom fields on the HighLevel user record. Some agent-level fields may alternatively map to contact custom fields if agents also exist as contacts within your specific setup and workflow requirements.