Migrate from Pipeline CRM to Nutshell

Pipeline CRM People records map directly to Nutshell Contacts. We preserve all standard fields (name, email, phone, address) and custom Person fields by recreating the field schema in Nutshell before import. Person-to-Company linkage is preserved by matching the associated Company name against the Account import, which creates the Contact-to-Account relationship at load time. Owner email is resolved against Nutshell User records during import.

Pipeline CRM Companies map to Nutshell Accounts. We import Accounts first to establish the hierarchy that Contacts and Opportunities reference. Company name is used as the primary dedupe key during import to prevent duplicate Accounts. Industry, size, revenue, and custom Company fields are created in Nutshell before the CSV load begins, matching the field type and picklist values defined in Pipeline CRM.

Pipeline CRM Deals map to Nutshell Opportunities with Deal value, stage, probability, and close date preserved. The Deal-to-Company relationship resolves to the Account lookup in Nutshell by matching Company name. Closed-Lost and Closed-Won reasons migrate to Nutshell's loss_reason field if configured. We coordinate stage mapping before migration so Opportunities land in the correct Nutshell pipeline stage.

Pipeline CRM's multiple pipelines (up to 10 on Start, 20 on Develop, unlimited on Grow) map to Nutshell Pipelines on a 1:1 basis. Each Pipeline CRM pipeline stage name is mapped to the corresponding Nutshell pipeline stage. We create the Nutshell pipeline structure before Deal import so that the pipeline and stage options are available as dropdown values during the load.

Pipeline CRM Activities linked to People or Companies are disaggregated into Notes (for logged email and meeting content) and Tasks (for logged calls and action items) in Nutshell. We use the Activity type field from Pipeline CRM to determine the split: emails and meetings become Notes; calls and logged call dispositions become Tasks. The linked Person or Company ID is resolved to the migrated Nutshell Contact or Account record. Not all destination CRMs support a separate Activity concept, which is why this disaggregation is required.

Pipeline CRM Agenda Tasks migrate to Nutshell Tasks with Status, Priority, due date (due_date or agenda_event_start), and assignee preserved. Task assignment is resolved by matching the Pipeline CRM Owner email to a Nutshell User. Tasks without a matching assignee are assigned to the account owner as a default. Completed status migrates as completed; open tasks retain their due date and priority.

Pipeline CRM Agenda Events (calendar items) migrate to Nutshell Events with start time, end time, title, location, and description preserved. Events are linked to the associated Contact or Account by resolving the Person or Company ID to the migrated Nutshell record. Recurring events require a note in the migration report because recurrence rules do not export and must be rebuilt manually in Nutshell's calendar integration.

Pipeline CRM custom fields defined on Company, Deal, and Person objects are recreated in Nutshell before migration. We map field types as follows: text fields to Nutshell Text fields, dropdowns to Picklist, dates to Date, numbers to Number, and checkboxes to Checkbox. Nutshell's pipeline-scoped custom field feature means that fields specific to one pipeline can be scoped to that pipeline's lead pages during setup, which requires the Nutshell pipeline to exist before custom field creation.

Pipeline CRM Owners are mapped to Nutshell Users by email address match. Any Pipeline CRM Owner not found in the Nutshell destination org is flagged in a reconciliation report before migration. The customer's admin provisions any missing Users before the main migration run so that OwnerId references are satisfied on Contact, Account, and Opportunity records.

Pipeline CRM Tags applied to People, Companies, and Deals migrate to Nutshell's native tag feature on Contacts, Accounts, and Opportunities. If the customer uses tags as a classification system rather than a labeling system, we discuss whether to map them to a multi-select custom field instead during scoping.