Migrate from BoldTrail to Freshsales

BoldTrail unified Contact objects split by lifecycle stage in Freshsales: Contacts with lifecycle_stage of 'Client' or 'Customer' land as Freshsales Contacts; all others (Lead, Prospect, Showing Request) land as Freshsales Leads. The migration applies your specified lifecycle-to-status mapping rules at record creation time.

BoldTrail Companies map directly to Freshsales Accounts. Company name becomes Account Name, domain becomes Website, industry maps via pick-list value mapping, and employee count maps to the standard NumberOfEmployees field. Parent-child company hierarchies in BoldTrail map to Freshsales Account hierarchy via the Parent Account lookup.

BoldTrail Deals map to Freshsales Opportunities. Deal name becomes Opportunity Name, deal amount maps to Amount, closedate maps to Close Date, and deal stage maps to Freshsales pipeline stage values. The BoldTrail pipeline the deal belongs to maps to a Freshsales Pipeline, which you configure in Freshsales Admin Settings before migration.

Each BoldTrail pipeline becomes a Freshsales Pipeline with configurable stages. We create the pipeline and stage definitions in Freshsales as part of the pre-migration schema setup, then map stage names value-by-value so deal history is preserved correctly in Freshsales reporting.

BoldTrail Smart Campaigns (drip email/text sequences tied to contact lifecycle triggers) cannot be exported as automation definitions and have no direct Freshsales equivalent. We export Smart Campaign names and associated contact IDs as a rebuild reference CSV. Freshsales Sequences must be configured manually in Admin Settings > Sequences using that reference.

BoldTrail email logs, call records, meeting records, and notes map to Freshsales Sales Activities. Each activity type preserves its original timestamp, owner, and linked contact/deal association. Rich-text note bodies migrate as note content attached to the corresponding Contact or Lead record.

BoldTrail listing data (address, MLS number, status, price) maps to a Freshsales custom module called Properties or to custom fields on the Account object. We map listing status values to Freshsales pick-list options. The choice between a custom module and account-level fields depends on whether listings need their own pipeline view.

BoldTrail custom contact properties and custom deal fields migrate to Freshsales custom fields created via Admin Settings > CRM Customization. Field types map accordingly: text fields stay text, pick-lists map value-by-value, and numeric fields preserve precision. Freshsales plan limits apply — Growth allows 100 custom fields per module, Pro allows 300, Enterprise allows 300.

Tags are preserved as string values attached to each record. Tags do not trigger Freshsales workflows automatically — that logic must be rebuilt separately. During migration, each BoldTrail tag is copied as a plain text label to the matching Freshsales record. Because Freshsales does not treat these labels as workflow triggers, any tag‑based automation must be rebuilt using Freshsales Workflows or Sequences after migration in production.

BoldTrail owner assignments resolve by email match against Freshsales user email addresses. Unmatched owners are flagged before the migration runs — your team either creates Freshsales users first or assigns those records to a designated fallback owner. System-level BoldTrail entities (team accounts, squeeze-page owners) that have no corresponding user email map to a system placeholder in Freshsales.

BoldTrail file attachments on contacts, companies, and deals re-upload to Freshsales under the corresponding record. File name, size, and original upload date are preserved as metadata. Freshsales plan-level storage limits apply — Pro plans include 5GB per user; Enterprise includes 100GB per user.