Migrate from BoldTrail BackOffice to Freshsales

BoldTrail contacts migrate directly to Freshsales Contacts. The contact's email, phone, and address fields map 1:1. Owner resolution runs by email match against Freshsales Users before migration — any unmatched owners are flagged and assigned to a fallback user so no record lands without an owner.

BoldTrail contacts with a 'Lead' or 'Prospect' status (or no associated transaction) route to Freshsales Leads rather than Contacts. Split logic applies at migration time based on the contact's transaction association and status field values. This routing ensures that prospects in your BoldTrail pipeline are properly staged for follow-up in Freshsales's lifecycle-based workflow, preserving your original lead nurturing sequences.

BoldTrail companies map to Freshsales Accounts. Account Name, Website, Industry, and employee-count fields migrate directly. BoldTrail parent-company hierarchies map to Freshsales Account hierarchical relationships via the parent_account_id field. This hierarchical mapping preserves your organizational structure in Freshsales, allowing you to maintain parent-subsidiary relationships and view companies in their proper corporate context during sales planning and account management activities.

BoldTrail transaction records map to Freshsales Deals. The transaction name becomes Deal Name, the transaction amount maps to Deal Amount, and the close date becomes the Deal Expected Close Date. Pipeline and stage status from BoldTrail map to Freshsales Deal Stages and Sales Pipeline assignment.

BoldTrail transaction status values (e.g., 'Active', 'Pending', 'Closed', 'Terminated') map to Freshsales Deal Stage values. We build a value-mapping table for each BoldTrail status and assign the corresponding Freshsales stage with probability and forecast category applied per stage. This ensures your deal pipeline in Freshsales reflects the same progression logic that your team used in BoldTrail, maintaining consistency in how deals move through your sales process.

BoldTrail agents do not have a direct Freshsales equivalent — Freshsales manages Users (system logins) separately from CRM records. We migrate agent profiles as a custom Agent object in Freshsales, linking each agent to their transaction records via a lookup field. Agent performance data stored in BoldTrail migrates as custom fields on this object.

BoldTrail commission plans and split rules have no Freshsales equivalent. Commission plan names, split percentages, and override rules migrate as custom fields on the Deal object or a dedicated Commission custom module. Rebuiliding commission logic in Freshsales requires a rebuild using Freshsales Workflows or an external commission tool.

BoldTrail document attachments linked to transactions re-upload to Freshsales as Deal attachments. File size limits (Freshsales default 25MB per file) are enforced during migration; inline images in BoldTrail notes are extracted and rehosted as Freshsales file attachments. Files exceeding the 25MB limit are flagged and split into smaller chunks or linked via external storage solutions, ensuring no critical transaction documents are lost during the migration.

BoldTrail transaction notes and comments migrate as Freshsales Notes attached to the corresponding Deal record. Original timestamps and note authors are preserved in the Note record's metadata fields. This preservation of note metadata ensures your team can trace the history of each deal discussion, understand who contributed to communications, and maintain a complete audit trail of deal-related conversations when transitioning to Freshsales.

BoldTrail transaction custom fields (e.g., property address, MLS number, referral source) require Freshsales custom fields created before migration. FlitStack delivers a custom field setup plan listing each BoldTrail custom field, its data type, and the Freshsales field to create. Your Freshsales administrator reviews and creates these fields prior to migration, ensuring all property-specific and transaction-specific data migrates correctly without truncation or data loss.

BoldTrail users mapped as transaction or contact owners are matched to Freshsales Users by email address. A user-mapping table is generated before migration; any BoldTrail user without a Freshsales counterpart is assigned to a designated migration owner and flagged for admin action.