Migrate from Fireberry to Nutshell

Fireberry Contact records map directly to Nutshell People. The standard fields (name, email, phone, address, owner assignment) migrate 1:1. We use the contact's primary email as the dedupe key during import to avoid creating duplicate People records. Fireberry's lifecycle stage property (if used) migrates as a custom text field on the Nutshell Person since Nutshell does not have a native lifecycle stage concept. Active status maps directly; inactive Fireberry contacts can be imported as inactive Nutshell People at the customer's option.

Fireberry Company records map directly to Nutshell Company. Company name is the dedupe key. Industry, size, address, and domain fields migrate to equivalent Nutshell Company fields. The Company-to-Contact relationship is preserved by maintaining the foreign-key linkage in our import sequencing: Companies are imported first, then People with their Company reference resolved before People insert begins.

Fireberry Deal records map to Nutshell Deal. Amount, stage, probability, expected close date, and pipeline assignment migrate directly. Nutshell uses a single pipeline model with configurable stages; Fireberry pipeline definitions are mapped to Nutshell stage names. If Fireberry uses multiple pipelines, we consolidate them into a single Nutshell pipeline with stage names that capture the original pipeline context, or we create separate Nutshell workspaces at the customer's option.

Fireberry's named pipelines with configurable stages map to Nutshell Deal stages. We extract the stage ordering and probability percentages from Fireberry and configure Nutshell's stage sequence to match. Any Fireberry stage with no migrated Deals is flagged for removal after migration. Stage names that are pipeline-specific (e.g., 'Enterprise - Demo Scheduled') are renamed to generic equivalents ('Demo Scheduled') unless the customer specifies a different convention.

Fireberry activity records (notes, calls, meetings, tasks) map to Nutshell Activity records of equivalent type. Each activity carries its original timestamp, owner assignment, and linked Contact and Company references. We resolve Nutshell Person and Company IDs before inserting Activities so that the activity timeline on each Person/Company record is complete. Attachments stored in Fireberry migrate as file references or re-upload links since we do not host file storage.

Fireberry's user-defined Components (custom objects) cannot map to a native Nutshell equivalent because Nutshell uses a fixed schema model. During schema discovery, we enumerate every active Component and determine whether it is: (a) a true standalone custom object requiring a separate entity, in which case we flag it for the customer to evaluate whether to recreate as a Nutshell Custom Field on Person/Company/Deal or as a linked record in a third-party tool, or (b) a set of extra fields on a standard object, in which case we create matching custom fields in Nutshell and migrate the values into those fields during the standard object import.

Fireberry custom fields on Contact, Company, and Deal objects map to Nutshell custom fields on the equivalent object. Picklist and multi-select fields from Fireberry are recreated as Nutshell custom fields with matching picklist options. Formula fields from Fireberry are flagged as non-migratable because Nutshell does not support formula field migration; the customer decides whether to rebuild the formula logic in Nutshell after migration. Required field settings are evaluated during migration: if a Fireberry custom field is required but the Nutshell equivalent cannot be required due to data gaps, we set it as optional.

Fireberry tags on Contacts and Companies are exported as flat lists per record. Tags migrate as Nutshell Tags on the equivalent Person or Company record. Tags that do not exist in Nutshell are created during migration. The customer specifies whether to use a tag-based taxonomy or a custom field strategy for tags that represent categorical data (e.g., industry segment) rather than loose labels.

Fireberry User records (name, email, role, team assignment) map to Nutshell User records by email match. We resolve active Fireberry users against Nutshell's user table. Any Fireberry user without a matching Nutshell User is placed in a reconciliation queue for the customer to provision before record import resumes. Inactive Fireberry users are optionally migrated as inactive Nutshell Users so that historical owner assignments are preserved in the audit trail.

File attachments stored against Fireberry records are exported as download references. We preserve the attachment URL and filename, and note that any files hosted internally by Fireberry require re-upload to Nutshell or a file storage service (Google Drive, Dropbox, SharePoint) with the link updated post-migration. Attachments that were email attachments in Fireberry activity records are flagged for the customer to re-attach after migration.