Migrate your BoldTrail data

BoldTrail enforces record ownership at the API level — you can only export contacts you personally own or imported. Contacts originating from team squeeze pages, office ads, or other agents are owned by those entities and are not accessible via export. We query ownership flags during scoping to identify which records are migratable and which require manual handoff from the owning team member.

Listings are fully accessible via the HomeSearch API and MLS API. IDX property data flows through BoldTrail and we can map listing records with their associated photos, status changes, and agent assignments. Listing timelines (milestones, notes, seller reports) are stored as metadata on the Listing object.

BoldTrail Lead Engine feeds leads through auto-nurturing sequences. We map the lead source, lifecycle stage, and any custom lead scoring fields. The auto-nurture sequence associations require rebuilding on the destination platform since Smart Campaigns do not export as portable automation logic.

Smart Campaigns are BoldTrail's proprietary automation engine and do not have a documented export or migration path. We export campaign membership, trigger conditions, and step definitions as a reference schema, then rebuild equivalent workflows (email sequences, SMS triggers, follow-up rules) on the destination CRM using the same trigger logic.

BoldTrail BackOffice manages commission records, transaction timelines, and document bundles. The Deals API provides access to transaction objects including commission splits, agent assignments, and status. We map these 1:1 into the destination's deal or transaction object, preserving the financial split logic.

Documents attached to transactions (contracts, disclosures, signatures via BrokerMint integration) are accessible via the Platform API. We download document binaries and re-associate them with the corresponding migrated transaction record on the destination platform.

Agent records include contact details, team assignments, and role-based permissions. BoldTrail pricing tiers are largely seat-driven, so migration scoping must reconcile the source account's agent count against the destination's plan. We map agent ownership of contacts to preserve accountability assignments post-migration.

BoldTrail teams group agents for shared lead routing, office-level squeeze pages, and aggregated reporting. We map team memberships and the associated team-owned lead sources so that routing rules can be reconstructed on the destination platform.

Custom fields on Contacts, Leads, and Transactions vary by account configuration. We extract the full custom property schema during the discovery scan and map each field to its closest equivalent on the destination platform, flagging any required-field gaps that need value assignment before import.

Subscribers are contacts who have opted in to marketing communications and are used for list-based broadcasts. Since BoldTrail lacks native newsletter broadcasting, these lists are often managed externally. We export subscriber status and list memberships, but the destination platform's list architecture may require re-segmentation.

BoldTrail tracks activity events including email opens, SMS sent, website visits, and listing views. The Events API provides chronological activity data per contact. We import the full activity timeline to preserve the historical context of each client relationship on the destination CRM.

Brokerage-level records including office name, branding settings, and MLS ID associations are stored at the org level. We map brokerage metadata and flag which settings (e.g., IDX branding compliance) need manual reconfiguration in the destination platform rather than automated import.