Migrate from PipelinePRO to Nutshell

PipelinePRO Contact records export as CSV with name, email, phone, and any custom field columns. We map these to Nutshell People records using email as the dedupe key. Any PipelinePRO custom properties on the contact require explicit field-by-field mapping: we request a screenshot or field list from the customer before migration, create matching Nutshell custom fields for People, and apply a migration-specific prefix on any field names that conflict with Nutshell reserved names. First name and last name split from the full name field where the source stores them together.

PipelinePRO Company records map to Nutshell Company records. Export quality depends on how consistently the account owner populated the company field on contacts before export. We flag sparse company records (records with no address, website, or phone) for customer review before importing, because Nutshell Company records are linked to People records via a lookup that must be satisfied at import time. Website domain from the PipelinePRO company record becomes the Nutshell Company website field and is used as an additional dedupe signal alongside company name.

PipelinePRO Deal records include name, value, stage, owner, and expected close date. We ask the customer during scoping whether the migrated deals represent qualified sales opportunities (mapped to Nutshell Deals) or early-stage prospects requiring a separate lead workflow (mapped to Nutshell Leads). Deal owner maps to Nutshell user by email match. If the PipelinePRO account uses the same pipeline for both leads and won/lost opportunities, we split them by stage name using a customer-reviewed mapping table before import.

PipelinePRO Lead records function as early-stage contacts with their own status field. Nutshell has a native Lead object separate from People. We preserve the PipelinePRO lead status as a custom property on the destination Nutshell Lead record when the destination's standard Lead Status picklist does not cover the source status values. We create the custom field during schema setup and populate it during import.

PipelinePRO uses customizable pipeline boards with drag-and-drop stage definitions. We extract the pipeline name and stage list from the exported data and rebuild the equivalent pipeline structure in Nutshell before Deal import. Nutshell Pipelines support stage names, probabilities, and pipeline-specific views. We configure these via Nutshell's pipeline management interface and match stage probabilities to the source values.

Stage names and order are configurable per pipeline in PipelinePRO. We map source stages to Nutshell stages using a customer-reviewed mapping table before bulk record migration. Closed-Lost and Closed-Won stages from PipelinePRO map to Nutshell's Lost and Won status flags on the Deal record rather than distinct stage names. The mapping table is reviewed and signed off by the customer before any Deal records are imported.

PipelinePRO custom fields exist per object but there is no bulk schema export. We ask the customer to provide a screenshot or list of custom field names and their data types (text, number, date, checkbox, dropdown) before migration. We create matching Nutshell custom fields for People, Companies, and Leads during schema setup. Custom field mapping is one of the first steps in the migration timeline because downstream record import depends on the destination schema being complete.

Tags on PipelinePRO contacts and deals export as comma-separated values in the CSV. We parse these and apply them as native Nutshell tags during import. Nutshell supports multiple tags per record. If a tag name in the source contains characters that Nutshell restricts (commas, semicolons), we normalize them to hyphen-separated equivalents during the transform step and document the normalization in the mapping reference.

PipelinePRO user accounts with names and email addresses export as a simple list. We map these to Nutshell user records and reassign owned deals and contacts accordingly. Owner resolution happens by email match. Any PipelinePRO user without a matching Nutshell account goes to a reconciliation queue for the customer to provision before record import resumes, because Nutshell requires a valid owner reference on Deal and People records.

Uploaded files attached to deals or contacts in PipelinePRO export via download links if the links are accessible from the export. We retrieve attachments during the extraction phase and re-upload them as Nutshell attachments linked to the corresponding People, Company, or Deal record. We flag any documents we cannot retrieve (broken links, access-restricted files) for manual handling during the migration scoping call.