Migrate from Follow Up Boss to Nutshell

Follow Up Boss Person maps to Nutshell Lead if the person has no associated Deal or is in the 'New' stage. People in Active or Client stage, or those with a Deal attached, land as Nutshell Contact. The split rule is configurable — teams can specify that all People migrate as Leads and sort in Nutshell afterward.

Follow Up Boss Company maps 1:1 to Nutshell Account. Follow Up Boss stores one primary company per Person; Nutshell Contacts link to one primary Account. If a Follow Up Boss Person has no company, we attach to a placeholder 'No Company' Account or leave the Account field blank, per your configuration preference.

Follow Up Boss Deal maps to Nutshell Deal. Nutshell Deals attach to an Account; Follow Up Boss Deals attach to a Person. We resolve the Deal-to-Account link by finding the Person's primary Company (now Account) and linking the Deal to that Account. Deal amount, name, stage, and close date transfer directly.

Follow Up Boss person stage values (New, Active, Client) map to Nutshell's Status field on Lead using a value-by-value lookup table. Client-stage people landing as Contacts use a custom Stage__c field, since Nutshell Contacts do not have a native stage property. Stage-enter timestamps are preserved in a custom field.

Follow Up Boss Deal Pipeline maps to a Nutshell Pipeline. Each Follow Up Boss pipeline becomes one Nutshell pipeline with its own stage set. Stage names map value-by-value. Nutshell supports multiple pipelines with different stage configurations — we create each one during schema setup and map stages per pipeline.

Follow Up Boss Action Plans — automated drip email sequences, SMS auto-replies, task-creation triggers, and lead-routing rules — have no direct equivalent in Nutshell. Nutshell's workflow rules are individual triggers (e.g., 'when lead enters stage, create task') but lack the multi-step sequence builder. We export Action Plan definitions as a structured reference document for your Nutshell admin to rebuild.

Follow Up Boss Smart Lists are dynamic segment definitions based on filter rules (stage, source, custom field conditions). These rules do not auto-migrate. We export Smart List definitions as a filter-reference sheet. Nutshell saved filters replicate the display logic, but dynamic re-evaluation of membership based on real-time changes requires manual filter setup.

Follow Up Boss email, call, and meeting activities map to Nutshell Activities. Notes map to Nutshell Notes. Original timestamps, owners, and linked Person/Deal associations are preserved. Nutshell Activities display in the timeline view of the linked Contact or Lead record.

Follow Up Boss custom fields (text, date, number, dropdown types) map to Nutshell custom fields on the corresponding object (Person fields migrate to Lead/Contact custom fields; Company fields to Account custom fields; Deal fields to Deal custom fields). Dropdown fields map value-by-value. Nutshell custom field names follow its labeling conventions — we translate the API name to a readable label during creation.

Follow Up Boss owner ID resolves to a Nutshell User by email address. Unmatched owners are flagged before migration — your team either creates the Nutshell user first or assigns records to a fallback user. Follow Up Boss does not store passwords or permissions, so user access configuration is destination-side work.

Follow Up Boss tracks lead source (referral, portal, website) natively. Nutshell has no standard Lead Source field — we create a Lead_Source__c custom pick-list on the Lead object and populate it with Follow Up Boss source values. Real estate portal sources (Zillow, Realtor.com) migrate as-is; teams rebuilding integrations in Nutshell map those to new source values.

Follow Up Boss file attachments associated with People or Deals migrate as Nutshell Attachments linked to the corresponding Contact or Deal record. Files are downloaded from Follow Up Boss and re-uploaded to Nutshell. File size limits are enforced by Nutshell's storage tier — we flag any file exceeding the destination limit before the full migration runs.