Migrate from BenchmarkONE to Freshsales

BenchmarkONE Contacts map to Freshsales Lead if the contact is unqualified (new, outreach, or nurture status) and map to Freshsales Contact if the contact is attached to an active Account or has progressed beyond initial outreach. We use BenchmarkONE's contact status and Temperature fields to determine the split. The original Temperature value (Cold, Warm, Hot) migrates to a custom field benchmark_temp__c on both Lead and Contact for reference during the Freddy AI scoring calibration period.

BenchmarkONE Company records map directly to Freshsales Account. The company name becomes the Account Name, website becomes the Website field, and the associated contacts link via the Account ID. We use the company name as the dedupe key during import. Freshsales Accounts do not support a separate industry vertical field on the free tier; we map BenchmarkONE's industry or segment custom field to a custom text field account_vertical__c on the Growth+ tier.

BenchmarkONE Deals map to Freshsales Opportunities. The deal name becomes Opportunity Name, the deal amount maps to Amount, and the pipeline stage maps to Freshsales Deal Stage. BenchmarkONE deal-stage probability percentages migrate to Freshsales Probability if the field is exposed on the customer's plan tier. Closed-Lost and Closed-Won dates from BenchmarkONE custom fields map to Freshsales Close Date and a custom loss_reason__c field.

BenchmarkONE's single deal pipeline stages map to Freshsales Deal Stage values. We configure the Freshsales Deal Stage picklist to match the exact stage names and probability percentages from BenchmarkONE during the sandbox phase. Stage order and probability values are preserved so that pipeline reporting continuity is maintained post-migration.

BenchmarkONE Tasks map directly to Freshsales Tasks with Subject, Due Date, Status, Priority, and Assigned To preserved. Tasks linked to a Contact or Company in BenchmarkONE retain the parent record lookup via Freshsales' Who Id and What Id fields. Task associations to Deals migrate via the What Id pointing to the mapped Opportunity.

BenchmarkONE tags stored as comma-separated values in the contact export map to Freshsales Contact Segments. We parse the tag string, create one Freshsales segment per unique tag value, and add the contact to each segment corresponding to the original tags. Segment membership is a dynamic membership feature on Growth+ tiers; on the free tier we store tag values as a multi-select picklist custom field benchmark_tags__c.

BenchmarkONE custom contact fields migrate to Freshsales custom fields on the corresponding object. Field types are mapped: text to text, number to number, date to date, checkbox to checkbox, dropdown to picklist. If a BenchmarkONE custom field is a dropdown, we create the Freshsales picklist with the same option values. Custom field definitions are audited during scoping because field type differences between platforms require explicit transformation logic.

BenchmarkONE email campaign metadata (campaign name, send date, audience size, open rate, click rate, bounce count) migrates to Freshsales as a Campaign record with aggregate stats stored in custom fields. The Freshsales native campaign object is available on Growth+ tiers. Individual email event logs (single email opens, clicks) require a separate report export from BenchmarkONE and map to Freshsales Activity records linked to the Contact; we flag this as a partial-history note in the scope document.

BenchmarkONE users assigned as owners to contacts, companies, deals, and tasks map to Freshsales User records by email match. We extract the distinct owner list from all record types during scoping and validate that each owner email has a corresponding Freshsales user provisioned before migration. Any owner without a destination user goes to a reconciliation queue for the customer's admin to provision.

BenchmarkONE social profile URLs (LinkedIn, Twitter/X, Facebook) stored on the contact record migrate to Freshsales custom text fields social_linkedin__c, social_twitter__c, and social_facebook__c on the Contact object. Freshsales does not have native social profile objects; storing as URL fields preserves the data and keeps it accessible on the contact timeline.