Migrate from CRUMP CRM to Nutshell

CRUMP CRM Contacts stored in Dynamics 365 contact entity map directly to Nutshell People. Standard fields (full name, email address, phone number, physical address, owner assignment) migrate 1:1. We preserve the original contact owner by resolving the Dynamics 365 ownerid to a Nutshell user by email match. Any inactive Dynamics 365 users are flagged for archival rather than import to avoid ghost records.

CRUMP CRM Accounts map to Nutshell Companies. The account name becomes the company name, and the primary domain from the account website field becomes the company website. We preserve the parent-account hierarchy if present in Dynamics 365 and reconstruct it in Nutshell by creating parent companies first, then linking child companies to their parent via Nutshell's company relationship fields.

CRUMP CRM Deals in Dynamics 365 CRM map to Nutshell Deals. The deal name, value, expected close date, and pipeline stage migrate directly. Stage names from Dynamics 365 are enumerated during the audit phase and mapped to Nutshell's deal stages, which are configurable per Nutshell plan. We preserve any custom deal fields as Nutshell custom fields against the deal record.

CRUMP CRM Helpdesk tickets (Dynamics 365 Cases) map to Nutshell Cases. Case status (Open, Pending, Resolved, Closed) migrates to Nutshell Case status. Case priority, description text, and linked contact association migrate. Case conversations and internal notes require a separate pass as Nutshell Cases support note attachments and linked People records but not a full threaded conversation log.

CRUMP CRM's Project Management module has no Nutshell equivalent. We export project records including project name, status, dates, assigned team members, and project-level notes, but deliver them as a structured CSV inventory rather than as native Nutshell records. The customer's admin decides whether to create Nutshell Companies or Deals to represent project context or to manage projects in a dedicated tool post-migration.

CRUMP CRM's invoicing module has no Nutshell equivalent. Invoice records (line items, totals, payment status, and link to originating Deal or Project) export as a structured CSV inventory. We note the relationship between invoices and their source Deals so the customer's accounting team can re-establish the link if they adopt a separate accounting tool.

CRUMP CRM tasks exist across multiple Dynamics 365 modules (CRM tasks, project tasks, helpdesk tasks). We deduplicate by task ID, label each by its origin module, and migrate all tasks to Nutshell Tasks. Task subject, due date, status, priority, and assigned owner resolve against the Nutshell user table by email match. Tasks linked to CRM Contacts or Deals reconnect to the migrated Nutshell People or Deals using external ID tracking.

CRUMP CRM user accounts and their role assignments in Dynamics 365 require explicit mapping to Nutshell Users. We extract the full user list, identify inactive users, and flag those for archival import. Active users map by email to Nutshell User records, and the Dynamics 365 security role names are documented in the role-mapping inventory so the customer's Nutshell admin can assign equivalent permissions.

CRUMP CRM custom entities created on the Dynamics 365 layer are enumerated during the audit phase. Each custom entity, its fields, and data types are documented individually. We create equivalent Nutshell custom fields on the matching standard object (Person, Company, Deal, or Case) before migration begins. Note: Nutshell Foundation has a cap on custom field creation; Pro and above support more permissive custom field schemas. We confirm the destination plan during scoping and flag any entity that exceeds the plan limit.