Migrate from Berry crm to Nutshell

Berry CRM Contacts map to Nutshell People records. Standard fields (name, email, phone, address) map directly. We detect any custom fields during the discovery export and create matching Nutshell custom fields on the Person object before import. Contact-to-Company relationships are preserved by resolving the parent Company ID to a Nutshell Company lookup during insertion.

Berry CRM Company records map 1:1 to Nutshell Company records. Company name, domain, address, and any custom fields transfer directly. We extract the company-contact relationship table to maintain the People-to-Company link in Nutshell's data model.

Berry CRM Deals map to Nutshell Opportunities. Deal name, amount, close date, and stage map to Opportunity name, amount, expected_close_date, and stage. We extract the full stage list from Berry CRM during discovery and configure Nutshell pipeline stages to match the original stage names before migration so that reporting continuity is preserved.

Berry CRM Sales Quotes are extracted with line items, pricing, status, and the associated Contact and Deal references. Nutshell does not have a native Quotes object at the Foundation tier, so we configure a custom Quote object in Nutshell during setup and map quote fields to custom fields. If the customer upgrades to a Nutshell plan supporting quotes or uses a quotes integration, we remap to the native structure. Quote-to-Deal associations preserve via the Opportunity lookup on the custom Quote record.

Berry CRM Products map to Nutshell Products with name, description, and unit price. ProductCode from Berry CRM maps to Nutshell's SKU field. We extract all active products during discovery; archived or inactive products are flagged for the customer's decision on whether to include or exclude from the migrated catalog.

Berry CRM Price Books define price lists tied to products. Nutshell uses a single Standard Price Book per account. We flatten the Price Book structure during import: for products with multiple price book entries, we migrate the primary price book entry as the Nutshell Product price and flag any additional price book entries in a custom field on the Product record for manual review.

Berry CRM Invoices are extracted as a reference record for billing history. Nutshell does not include native invoicing; invoicing typically relies on an accounting integration (QuickBooks, Xero, FreshBooks). We migrate invoice data as a read-only custom object in Nutshell or as a note attachment on the related Company or Person record so that billing history is accessible without requiring a return to the source system.

Berry CRM Projects are a distinct object tied to Companies or Deals. Nutshell is a CRM, not a project management tool, and has no native Projects object. We extract project metadata (name, status, dates, description) and attach it as notes or custom fields on the related Company or Opportunity record. For teams requiring project tracking post-migration, we recommend a separate project management tool (Asana, Monday.com, or Nutshell's integration ecosystem) and document the project mapping as part of the post-migration setup handoff.

Berry CRM Tasks map to Nutshell Tasks with title, due date, assignee, and completion status preserved. Task-to-Contact and Task-to-Company associations migrate via Nutshell's People and Company lookups. We extract the task assignment by email and resolve to a Nutshell User during insertion; unresolved assignees are held in a reconciliation queue for the customer's admin to resolve.

Berry CRM custom fields are detected during the discovery export by comparing the full field list against the standard Berry CRM schema. Each custom field is mapped to a Nutshell custom field on the appropriate object (Person, Company, or Opportunity). Field type conversion is handled explicitly: checkbox lists become Nutshell dropdowns or multi-select fields; date fields become date pickers; text fields become text inputs. Custom field mapping is the primary reason the discovery phase for Berry CRM is longer than for platforms with published schemas.