Migrate from BenchmarkONE to Salesforce Sales Cloud

BenchmarkONE Contacts with Temperature values of Cold or Warm map to Salesforce Lead. Contacts with Temperature of Hot or Closed Won map to Salesforce Contact attached to an Account. We compute the split at migration time using the temperature property, and preserve the original BenchmarkONE Temperature value in a custom picklist field b1_original_temperature__c on both Lead and Contact for audit and historical reference. The customer defines temperature thresholds during scoping based on their existing lead scoring matrix.

BenchmarkONE Company records map directly to Salesforce Account. The Company Name becomes Account Name and the Website URL maps to the Account Website field. We use Company Name as the dedupe key during import. Account records are created before any Contact or Lead import so that the AccountId Lookup is satisfied at the moment of record insert.

BenchmarkONE Deals map to Salesforce Opportunity. The Deal pipeline and stage values map to a Salesforce Record Type and Sales Process that we configure before migration. We preserve Deal value as Amount, expected close date as CloseDate, and owner assignment as OwnerId. If the customer has custom Deal fields, we audit them against Salesforce Opportunity custom fields during schema design.

Each BenchmarkONE pipeline stage becomes a Salesforce StageName value within the mapped Sales Process. Stage probability percentages migrate from BenchmarkONE to Salesforce StageProbability rounded to the nearest integer. We configure the Sales Process in Salesforce before migration so stage dropdown values are available at insert time.

BenchmarkONE tags are free-form comma-separated values on Contact records. We parse them and populate a Salesforce multi-select picklist field (b1_tags__c) on Lead and Contact. During scoping, we audit total unique tag count; if the tag vocabulary exceeds 150 unique values, we recommend migrating to Salesforce Topics with TopicAssignment records or a junction custom object for more scalable segmentation.

BenchmarkONE's Temperature property (Cold/Warm/Hot) is a built-in lead scoring mechanism. We map it to a custom picklist field b1_temperature__c on Lead and Contact. If the customer has been relying on Temperature for outreach prioritization, we also map it to Salesforce's native Lead Scoring (a Salesforce Labs app available in AppExchange) as a parallel scoring model post-migration, with a note that native Lead Scoring requires activation in Setup.

BenchmarkONE custom fields on Contact records map to Salesforce custom fields on the Lead and Contact objects. We audit the full custom field schema on both sides during scoping, mapping BenchmarkONE field types (text, number, date, dropdown) to equivalent Salesforce field types. Custom fields that are empty across all records are flagged to the customer for deletion before migration to avoid schema clutter in Salesforce.

BenchmarkONE custom fields on Company records map to Salesforce custom fields on the Account object. We apply the same type-mapping audit as with Contact custom fields. Company-level custom field values are preserved on the Account record.

BenchmarkONE custom fields on Deal records map to Salesforce custom fields on the Opportunity object. We create these fields during the schema design phase before any Opportunity data is inserted. The customer confirms which Deal fields are actively used versus historical before we map them.

BenchmarkONE Tasks map to Salesforce Task. Due date maps to ActivityDate, task body to Subject and Description, status to Task Status, and assignee to OwnerId via email-matched User resolution. Tasks linked to a Contact or Company are resolved after the Lead-Contact split, with WhoId and WhatId set on the Salesforce Task record. Completed status migrates directly to Completed on Salesforce.

BenchmarkONE stores campaign metadata (name, send date, audience count, template) and aggregate performance stats (open rate, click rate, bounce count). We map these to Salesforce Campaign records with aggregate stats as custom fields. Individual email recipient activity (opens, clicks per contact) migrates to CampaignMember with Status and custom tracking fields. Note that Salesforce does not have a native email sending capability in Sales Cloud; if the customer sends email through a third-party marketing platform post-migration, CampaignMember status reflects unsubscribe and delivery states from that system.

BenchmarkONE stores social profile URLs (LinkedIn, Twitter/X, Facebook) on Contact records as labeled URL fields. We map these to custom URL fields on the Lead and Contact objects (b1_linkedin_url__c, b1_twitter_url__c, b1_facebook_url__c) for consistency with the temperature migration split.

BenchmarkONE's Lead Source field on Contact maps directly to Salesforce Lead Source on Lead and Contact. We preserve the existing picklist values and add any new BenchmarkONE Lead Source values to the Salesforce picklist before migration.

BenchmarkONE's Assigned Sales Rep on Contact, Company, and Deal maps to Salesforce OwnerId on Lead, Account, and Opportunity. We resolve by email match against the destination Salesforce User table. Any BenchmarkONE owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before the record phase begins.