Migrate from BenchmarkONE to Nutshell

BenchmarkONE's unified Contact object does not have a direct Nutshell equivalent. Nutshell separates unqualified prospects into Leads and qualified contacts into Contacts attached to Accounts. We resolve the split during scoping using BenchmarkONE's Contact Status and Temperature fields: contacts with Hot/Warm Temperature and a defined deal may map to Nutshell Contact; lower Temperature contacts map to Lead. The original Temperature value migrates as a custom numeric field benchmark_temperature__c on both the Lead and Contact for audit and future segmentation.

BenchmarkONE Company records map 1:1 to Nutshell Account. The Company Name maps to Account Name, Website URL maps to Website, and Phone maps to Phone. The Account is created before Contact import so that the Account lookup reference is available at the moment of Contact insert. Nutshell's Account object does not support hierarchical parent-child structures natively; if the BenchmarkONE account has parent-company relationships, we document them for manual reconfiguration in Nutshell.

BenchmarkONE Deals map directly to Nutshell Deals. Deal name, amount, stage, expected close date, and associated Contact and Company links migrate 1:1. BenchmarkONE deal pipelines map to Nutshell's Deal pipeline, and deal stages map to the corresponding Nutshell stage values. If the BenchmarkONE account has multiple deal pipelines, we document the mapping to Nutshell's single default pipeline for manual reorganization post-migration.

BenchmarkONE Tasks linked to contacts, companies, or deals migrate to Nutshell Activities. Task name maps to Activity subject, due date maps to due, status maps to status, and assigned sales rep maps to the assigned User. BenchmarkONE tasks that are marked as completed retain their completed status in Nutshell. Reviewers have noted that BenchmarkONE Tasks and Deals can feel redundant; we migrate both objects and preserve their associations.

BenchmarkONE tags stored as comma-separated values on each contact migrate to Nutshell's tag field. Each tag becomes an individual Nutshell tag. Multi-tag contacts are split and applied as individual tags on the Nutshell contact record. Tags used for lead source attribution migrate as tags; if a BenchmarkONE account uses tags to track lead sources (e.g., LinkedIn, Referral, Trade Show), these migrate as-is and can be used for Nutshell filtering and reporting.

BenchmarkONE custom fields on Contacts, Companies, and Deals map to Nutshell custom fields. We audit the source custom field schema during scoping, define the equivalent Nutshell custom field type (text, number, date, dropdown), and pre-create the destination fields before migration. A known limitation: Nutshell does not support searching by custom fields via its API, which means custom field values migrate and display correctly but cannot be used as a filter criterion within Nutshell's API queries without a workaround.

BenchmarkONE stores campaign metadata (name, send date, audience size, open rate, click rate) and aggregate performance stats. We map campaign records and aggregate stats to Nutshell Note records with a standardized prefix CAMPAIGN: in the title so they appear at the top of the contact timeline. Individual email event logs (opens, clicks at the per-contact level) do not migrate as granular activity records; aggregate campaign performance is preserved in the Note body.

BenchmarkONE stores social profile URLs (LinkedIn, Twitter/X, Facebook) on contact records. These migrate to Nutshell custom text fields for each social network. The URL fields are preserved as text so they are visible on the contact record but do not create native social link interactions in Nutshell.

BenchmarkONE Users (unlimited seats across all tiers) map to Nutshell Users by email match. We extract every distinct owner referenced on contacts, companies, deals, and tasks and match by email against the Nutshell destination account's user table. Any BenchmarkONE user without a matching Nutshell user is held in a reconciliation queue for the customer's admin to provision before record import resumes.

BenchmarkONE automations triggered by form submissions, website visits, tag changes, link clicks, or purchases are platform-native constructs that do not export as data. We document every active automation's trigger, conditions, and actions during discovery and deliver a written Playbook mapping that maps each BenchmarkONE automation to the equivalent Nutshell Playbook (available on Growth plan and above) or manual process. This is a documentation deliverable, not a data migration step.