Migrate from CRM Runner to Nutshell

CRM Runner Contact records map directly to Nutshell Person records. Standard fields (name, email, phone, address) migrate 1:1. Any CRM Runner custom fields on contacts map to Nutshell custom fields on Person, which are available on all paid Nutshell plans. We use email as the deduplication key and preserve the original CRM Runner contact ID in a custom field for audit tracing.

CRM Runner Company records map to Nutshell Company records with a direct field-to-field mapping. The CRM Runner contact-to-company relationship is preserved by linking each Person record to the matched Nutshell Company via the Person-Company association at migration time. Company name serves as the deduplication key.

CRM Runner Jobs are the primary field-service object tracking work orders with status, location, assigned team member, and time entries. Nutshell has no native Jobs module, so Jobs map to Nutshell Deals. CRM Runner job status values (e.g., Pending, Scheduled, In Progress, Completed, Cancelled) map to Nutshell pipeline stage names, either by matching existing stages or creating custom stages during Nutshell configuration. Job location, scheduled date, and assigned team member migrate as Deal fields or custom fields.

CRM Runner Team Member records map to Nutshell User records. Role and department information from CRM Runner migrate as custom fields on the Nutshell User record. Any CRM Runner permission profile assignments are flagged in the migration report for manual reconfiguration in Nutshell, as permission models differ between platforms. Active team members provision as active Nutshell users; inactive members are migrated as inactive users for historical record ownership preservation.

CRM Runner Communication records (calls, SMS, in-app chat) attached to contacts or jobs flatten into Nutshell Activity records linked to the corresponding Person or Deal. Call duration, disposition, and timestamp transfer to Activity fields. Call recording URLs are preserved in a custom field on the Activity record, though playback requires CRM Runner access or an independently migrated recording storage system.

CRM Runner Time Entries embedded within Jobs and tied to Team Members are extracted as a dedicated CSV during migration scoping. They are mapped to Nutshell Tasks with ActivityDate representing the clock-in timestamp, and task descriptions carrying clock-in, clock-out, and duration data. Because they are payroll-adjacent and do not represent CRM engagement activity, we recommend pairing this CRM migration with a dedicated payroll or accounting tool migration for the time entry dataset.

CRM Runner's configurable pipeline stages map to Nutshell Pipeline stages. Stage names are recreated in Nutshell to match CRM Runner's workflow. Stage order and probability percentages transfer to Nutshell stage definitions. We configure the Nutshell pipeline before Deal migration so that stage mapping is satisfied at import time.

CRM Runner custom field definitions across contacts, companies, and jobs are extracted during scoping. We map each custom field to the equivalent Nutshell custom field on the corresponding object (Person, Company, or Deal), matching field type to the closest Nutshell type (text, date, checkbox, dropdown). Dropdown values and picklist options migrate as Nutshell picklist values. Any CRM Runner custom field with no Nutshell equivalent is flagged in the migration report with a recommended workaround.

CRM Runner automations are configured through a proprietary trigger-action interface that has no documented export or migration path. We do not migrate automations as code. During discovery we document every identified automation as a written specification covering trigger type, conditions, and actions. The customer's admin uses this document to rebuild automations in Nutshell's workflow automation builder (available on Nutshell Pro and above). This is a post-migration step outside standard migration scope.

CRM Runner payment records are embedded within Jobs and tied to contacts. They are accounting-adjacent and do not map cleanly to standard CRM objects in Nutshell. We export them as a separate financial CSV package during migration, which the customer's accounting or bookkeeping team handles. We do not recommend importing payment records into Nutshell as a CRM object; a dedicated accounting tool migration is the appropriate path for this data.