Migrate from Crust CRM to Nutshell

Crust CRM Contacts map to Nutshell People. Both platforms share a standard contact schema with name, email, phone, and address fields. We preserve all standard properties and any lifecycle stage designation from Crust CRM as a custom People field in Nutshell. Email deduplication runs against existing Nutshell People records before insert to prevent duplicate contacts on migration day.

Crust CRM Company records map directly to Nutshell Company. The company-contact relationship is preserved by resolving the Crust CRM company_id against Nutshell Company records at import time. Nutshell requires a Company to exist before a Person can be associated with it, so we import Companies before People in every migration. We run deduplication against existing Company records using domain as the match key.

Crust CRM Deals map to Nutshell Deals. We extract deal amount, close date, owner, pipeline stage, and custom fields from Crust CRM. The Crust CRM pipeline stage name maps to a Nutshell stage using the translation table generated during discovery. Crust CRM deal_owner_id resolves to Nutshell User by email match before import.

Where Crust CRM maintains a separate Lead object from Contact, we preserve the Lead_Status property as a custom field on the migrated Nutshell Person record rather than creating a separate object. Nutshell handles lead qualification through Person properties rather than a distinct Lead object. We document the original Lead record count and status distribution for the customer's admin to act on in Nutshell.

Crust CRM engagement records—calls, emails, meetings, notes, and tasks—migrate as Nutshell Activity records linked to their parent Person, Company, or Deal. We preserve the original timestamp on each activity record to maintain timeline ordering. Activity types map to Nutshell activity types: call engagements to Calls, meeting engagements to Meetings, emails to Emails, and notes to Notes.

Crust CRM pipeline-stage definitions migrate as Nutshell Pipeline configurations. We generate a stage translation table during discovery that maps each Crust CRM pipeline and stage name to the target Nutshell Pipeline and Stage. Stage probabilities migrate as percentage values against each stage. The customer configures pipeline visualizations (List, Map, Chart, Board) in Nutshell after migration.

Crust CRM User records and owner assignments on Contacts, Companies, and Deals map to Nutshell User records. We resolve owners by email match. Any Crust CRM Owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import begins.

Crust CRM attachments stored per record are exported individually with filename and record association preserved. Files are re-attached to the corresponding Nutshell Person, Company, or Deal record after the parent record exists in Nutshell. We handle both database-stored attachments (self-hosted) and API-served attachments (cloud-hosted) depending on the Crust CRM deployment type.

Crust CRM's configurable module architecture means every organization may have unique custom objects and field types. We audit the full custom object schema during discovery, map field types to Nutshell custom field equivalents where available, and document any fields that require custom field creation in Nutshell post-migration. Custom objects that cannot map to Nutshell's standard schema are recorded as a configuration handoff for the customer's admin. We do not migrate custom objects as code.