Migrate from BoldTrail to Microsoft Dynamics 365 Sales

BoldTrail contacts map directly to Dynamics 365 Contacts for active clients and leads already in a deal pipeline. Unassigned or early-stage contacts can land as Dynamics Leads depending on your sales process definition — FlitStack applies a configurable routing rule at migration time.

BoldTrail Company maps 1:1 to Dynamics 365 Account. BoldTrail parent‑child company hierarchies map to Dynamics Parent Account lookups. Multi‑company associations on a BoldTrail contact collapse to a primary AccountId plus Account Contact Relationships in Dynamics. All standard company fields — name, address, phone, website, industry, employee count, and annual revenue — are transferred to the corresponding Account fields, and any custom company properties are stored in custom fields on the Account entity.

BoldTrail Deal maps to Dynamics 365 Opportunity. Deal stage names map to Opportunity StageName values via value mapping; stage probabilities and forecast categories are re‑applied from Dynamics defaults unless custom stage configuration is provided before migration. All standard deal fields — name, amount, close date, pipeline, and owner — transfer to the corresponding Opportunity fields, and any BoldTrail custom deal attributes are stored in custom fields on the Opportunity entity, preserving historical context.

BoldTrail Property has no native equivalent in Dynamics 365 Sales. A custom Dataverse Property table is created in your Dynamics environment with fields for address, list price, bedrooms, bathrooms, square footage, property type, status, listing agent lookup, and listing date — then linked to Opportunity records via a custom lookup field.

BoldTrail Transaction records — contract date, closing date, sale price, commission split, agent — require a custom Dataverse Transaction table or extension fields on Opportunity. The Transaction table links to the Property table and Opportunity, preserving the BoldTrail relationship graph.

BoldTrail call log entries map to Dynamics 365 PhoneCall activities with original start time, duration, direction (inbound/outbound), outcome, and owner preserved. The PhoneCall activity is linked to the parent Contact or Lead record, and any call notes or disposition text are stored in the Description field of the PhoneCall entity. Additionally, the PhoneCall activity includes an ActivityParty record for the caller and callee, ensuring full call‑related participant tracking within Dynamics.

BoldTrail email engagement history maps to Dynamics 365 Email activities. Subject, body (plain text), timestamp, sender, and recipient are preserved. Rich HTML email bodies are stripped to text format to match Dynamics activity storage conventions, and file attachments are downloaded from BoldTrail and re‑uploaded to Dynamics 365's document storage, linked to the Email activity. The Email activity also includes ActivityParty records for the sender and each recipient, preserving communication chain.

BoldTrail showing and meeting records map to Dynamics 365 Appointment activities with original start/end times, subject, location, and attendees preserved. Property‑showing appointments are linked to both the Contact and the Property record in Dataverse, and the Appointment entity captures the appointment type, description, and notes from BoldTrail. Reminder settings are applied per Dynamics preferences, and each appointment is associated with the related Opportunity when the meeting concerns a specific deal.

BoldTrail notes and document attachments map to Dynamics 365 Annotations. Text notes become Annotation records with isdocument=false, preserving the created‑on timestamp and author. File attachments are downloaded from BoldTrail and re‑uploaded to Dynamics 365's document storage, where they are linked to the parent record (Contact, Account, Opportunity, or Property table) via the objectid and objecttypecode fields. Each annotation also records the file name and MIME type, ensuring an audit trail.

BoldTrail agents and users are resolved by email match against Dynamics 365 SystemUser records. Unmatched BoldTrail agents are flagged before migration — your team either provisions a corresponding Dynamics user first or assigns those records to a fallback owner during migration.

BoldTrail contact tags and segment memberships map to a multi-select custom field on Contact (tags as semicolon-delimited text) and to Marketing List membership records in Dynamics for segmentation continuity. FlitStack surfaces the full tag list for your admin to configure the target field.