Migrate from Gauss Box CRM & Sales to Nutshell

Gauss Box Organizations map to Nutshell Companies using Organization name as the primary key and address fields (street, city, country, postal code) mapping directly to Nutshell's address fields. D&B business intelligence fields present on Gauss Box Organizations (credit score, risk rating, employee count from D&B) are stored as custom attributes on the Gauss Box side; we enumerate these during discovery and create matching custom fields in Nutshell before import. Companies are loaded first because both Contacts and Deals reference them as parent lookups.

Gauss Box Products map to Nutshell Products with product name, category, item type, price, and sale tax configuration migrating as-is. The product code or SKU maps to Nutshell's product_code field. Products are loaded second because Deals reference them via deal-product associations that we resolve at migration time. Nutshell's product importer supports CSV and direct API insertion; we use whichever method produces fewer schema mismatches for the specific product attribute count.

Gauss Box Contacts map to Nutshell People. Name, email, phone, and address fields map directly. Any custom attributes defined in the account's Gauss Box attribute set (region, industry classification, custom flags) are enumerated during discovery and created as Nutshell custom fields on People before import. We use email as the deduplication key; duplicate email addresses are flagged for the customer to resolve before final import.

Gauss Box Leads map to Nutshell Leads. The lead's work status, assigned team member, and lead source migrate directly. We preserve the Gauss Box lead-to-contact link by storing the corresponding Contact's ID in a custom field on the Nutshell Lead record so that the customer can manually convert the Lead and link it to the correct Person once in Nutshell. Gauss Box does not have an automated lead-convert action, so this manual step is required.

Gauss Box Deals map to Nutshell Deals with stage, owner, value, and budget fields. The Gauss Box pipeline stage name (account-specific, e.g., 'Offer Sent' or 'Negotiation') maps to a Nutshell deal stage that we configure before migration, with probability percentages matching the Gauss Box stage configuration. Deal owner resolves by email to the Nutshell user. Deals carry product associations from the Gauss Box product catalog that we link to the Nutshell Deal as line items.

Gauss Box's configurable pipeline stages are account-specific and not standardized across tenants. We enumerate the exact stage names and probabilities from the customer's Gauss Box account during discovery and configure matching Nutshell deal stages with corresponding probability percentages. Nutshell does not support multiple simultaneous deal pipelines; if the customer uses multiple pipelines in Gauss Box, we consolidate to a single Nutshell pipeline with all stage values from all source pipelines included and flagged with a custom pipeline-source field.

Gauss Box Activities (calls, emails, meetings, tasks linked to Deals and Contacts) map to Nutshell Activities. We preserve the activity type, timestamp, description, and the parent object link (Deal or Contact reference). Gauss Box embeds automatic reminders within record metadata rather than as independent rows; we extract what is present in the export, flag records with active reminders that will not carry over, and recommend the customer document open reminder counts before migration so they can recreate priority reminders in Nutshell's task due-date system.

Gauss Box's attribute-set system lets each account define custom fields on Contacts, Organizations, Deals, and Products. These fields are not standardized across accounts — a field called 'Region' on one account may not exist on another. We run a mandatory discovery phase to enumerate every active attribute set and field before mapping to Nutshell. Each Gauss Box custom field must be created as a new custom field in Nutshell (on People, Companies, Leads, or Deals) before data is imported; skipping this step results in data landing in the wrong columns or being silently dropped.

Gauss Box stores documents per record with access permissions. We extract files from the export package and re-attach them to the corresponding migrated record in Nutshell, preserving filename and any stored metadata. Nutshell supports file attachments on People, Companies, Leads, and Deals. Document versions are not preserved; only the current version of each document migrates. Access permissions do not transfer and are recreated manually in Nutshell post-migration.

Deals, Leads, and Activities carry owner assignments tied to Gauss Box user accounts. We extract every distinct owner email referenced on records and attempt to match by email against the Nutshell destination account's user directory. Any owner without a matching Nutshell user is flagged in a reconciliation queue for the customer's admin to provision before record import resumes. Gauss Box user roles and department structures do not map to Nutshell roles (Nutshell uses a simpler permission model); these are documented in the inventory delivered to the customer for manual rebuild.