Migrate from Grow CRM to Nutshell

Grow CRM Contact records map directly to Nutshell Person records. Standard fields (name, email, phone, address, tags) migrate via CSV export. Email addresses serve as the dedupe key during Nutshell import. Any custom fields on Contacts in Grow CRM require pre-creation in Nutshell's custom fields section before import; we extract the field definitions from Grow CRM during scoping and document them as a schema specification for the customer to provision before the migration load runs.

Grow CRM Company records map to Nutshell Company records with a direct field-to-field translation. The Company-to-Person relationship is preserved by resolving the Grow CRM contact-to-company foreign key at import time, linking each Nutshell Person to its parent Company via the Account (Company) lookup. Nutshell does not enforce a strict Account-Contact hierarchy but supports the relationship for reporting.

Grow CRM Lead records migrate to Nutshell Lead records with status, source, and owner assignment preserved. Grow CRM's lead status values map to Nutshell's Lead Status picklist. Owner resolution happens by email match against Nutshell Users; any Grow CRM Owner without a matching Nutshell User enters a reconciliation queue for the customer admin to provision.

Grow CRM Opportunities map to Nutshell Deals. Deal value, stage, expected close date, and owner assignment transfer directly. Pipeline stage names from Grow CRM map to Nutshell's pipeline stages, which we configure in Nutshell before the migration import. Grow CRM's deal-to-contact relationship is preserved as the Deal's linked Person in Nutshell.

Grow CRM Tasks migrate to Nutshell Tasks with status, priority, due date, and assignment preserved. Grow CRM Tasks support custom fields, which are not included in the standard CSV export; we extract custom field definitions from the Grow CRM UI or database during scoping, document them as a schema specification, and require the customer to pre-create matching custom fields in Nutshell before the migration load. Task assignment resolves by email match against Nutshell Users.

Nutshell does not have a native invoice object. Grow CRM Invoices (including line items, totals, tax, and payment status) are converted to Nutshell Note records attached to the corresponding Person or Company. The Note body contains a structured summary of the invoice data. Historical paid invoices migrate as closed records; open invoices are flagged for the customer's admin to recreate in a dedicated billing tool post-migration.

Grow CRM Payments (amounts, payment gateway, date, linked invoice) do not have a native Nutshell equivalent and are converted to Note records attached to the Person or Company. The Note captures payment date, amount, and gateway (Stripe or PayPal). Full payment reconciliation requires a dedicated accounting or invoicing tool; Nutshell is not designed to replace Grow CRM's financial records.

Nutshell does not include a native help desk or case management object at the tiers most small teams use. Grow CRM Help Desk Tickets (with status, priority, assignee, and conversation history) are converted to Note records attached to the Person or Company. Conversation threads are preserved as plain text in the Note body. Customers planning to use Nutshell's Enterprise tier with Service Cloud or a separate help desk tool should treat this as a migration of historical context rather than live ticket data.

Grow CRM custom fields on Clients (Contacts) and Tasks require manual schema extraction and pre-creation in Nutshell. We document each custom field definition (name, type, picklist options if applicable) from the Grow CRM UI or database during scoping. Nutshell's custom field creation UI is straightforward but must be provisioned before the data import runs; failing to pre-create fields results in import failures for records that reference them. This step is a prerequisite in our migration checklist.

Grow CRM tags on Contacts, Companies, and Opportunities are stored as comma-separated values in the CSV export. We normalize tag values during the transform phase and recreate them as Nutshell Tags, which can be applied to People, Companies, Leads, and Deals. Tag taxonomy is preserved in full.

Grow CRM client portal access records and login credentials are not included in any export path. Clients who had portal logins must be re-invited in the new system. We flag all Contacts that had portal access in the scoping report so the customer can run a bulk re-invite post-migration. This is a Grow CRM data model constraint and cannot be worked around without Grow CRM database-level access, which is not available for SaaS-hosted Grow CRM instances.