Migrate from BoldTrail to Salesforce Sales Cloud

BoldTrail Contact maps directly to Salesforce Contact, preserving the original FirstName, LastName, Email, Phone, and Title fields. Salesforce requires an AccountId for most contact records; contacts without a primary company association are linked to a default 'Unassigned Account' record created for this purpose, or flagged for manual assignment before migration runs. Custom contact properties are migrated as custom __c fields.

BoldTrail contacts whose most recent status is 'Lead' or 'Prospect' are routed to Salesforce Lead, preserving LeadSource, original create date, and any custom fields. Contacts marked as active clients or those associated with closed transactions flow to Salesforce Contact, maintaining their AccountId linkage and original timestamps. The split decision uses the latest status value recorded in BoldTrail before the migration run.

BoldTrail Company maps one-to-one to Salesforce Account, transferring the company name, website, phone, billing address, industry, type, and any custom fields. Parent/child hierarchies are preserved by setting the Salesforce ParentId to the migrated parent Account. Contacts that belong to multiple companies are linked to one primary Account via AccountId and recorded as secondary Account Contact Relations, ensuring each contact relationship is represented without duplication.

BoldTrail Deal maps to Salesforce Opportunity with deal name as Opportunity Name, deal amount as Amount, and close date as CloseDate. BoldTrail deal owner is resolved by email to a Salesforce User and set as OwnerId. Deals without a matchable owner are assigned to a fallback owner flagged post-migration.

BoldTrail pipeline becomes a Salesforce Sales Process keyed by Record Type. Each BoldTrail pipeline requires a corresponding Salesforce record type so Opportunity Stage pick-list values are scoped correctly per deal type. We deliver a record-type setup plan before the migration run.

Each BoldTrail pipeline stage is mapped directly to a corresponding Salesforce Opportunity Stage name, scoped to the appropriate record type. The mapping also transfers stage probability percentages and forecast category settings from the source stage model, ensuring that sales forecasting reports reflect the original pipeline logic. Timestamps indicating when a deal entered each stage are saved as custom datetime fields on the Opportunity, preserving the historical progression timeline for reporting.

BoldTrail listing and property data has no direct Salesforce equivalent. We map property records to a custom Property__c object with fields for address, MLS number, status, price, and listing agent. The Salesforce admin creates the custom object before migration; we deliver the field spec and data load sequence.

BoldTrail email activities map to Salesforce Task records with Type='Email'. Calls map to Task with Type='Call'. Meetings map to Salesforce Event with original start and end times preserved. Notes migrate as Salesforce Notes (modern ContentNote object). Original timestamps and owner assignments are preserved on all activity records.

BoldTrail file attachments on contacts, companies, and deals are downloaded and re-uploaded to Salesforce Files. File size limits of 25MB per file apply; files exceeding this limit are flagged for manual handling. Inline images embedded in BoldTrail notes are extracted and re-hosted as Salesforce CRM Content versions.

BoldTrail custom fields on deals (beyond standard name, amount, stage, close date) require Salesforce custom fields on the Opportunity object with the __c suffix. Each custom field's data type is mapped: text to Text, pick-list to Picklist (with value mapping), date to Date, number to Number. The Salesforce admin pre-creates these fields using the field spec FlitStack delivers.

BoldTrail custom properties on contacts and companies migrate to Salesforce custom fields on Contact or Account. BoldTrail's flexible property model (key-value pairs) is normalized into typed Salesforce fields. Properties with no Salesforce equivalent are preserved as text fields for reference.

BoldTrail users and team members are matched by email to Salesforce Users. The match creates an OwnerId linkage so deal and contact records route to the correct Salesforce user. Unmatched BoldTrail users are flagged before migration — your admin either creates Salesforce User accounts first or assigns their records to a fallback owner.

BoldTrail BackOffice transaction data (commissions, agent splits, closing details) does not map to any standard Salesforce object. We map these to a custom Transaction__c object linked to the Opportunity. The Salesforce admin creates the custom object using the transaction field spec before migration.