Migrate from PipelineManager to Nutshell

PipelineManager Pipelines map into Nutshell's single Pipeline as Stage definitions. When PipelineManager has one Pipeline, it maps directly as Nutshell Stages on the People, Company, and Deal record types. When PipelineManager has multiple Pipelines (e.g., separate pipelines for different lines of business), we consolidate them into Nutshell's single Pipeline and create Stage groupings using a custom stage_order field or a Pipeline Type custom field on each record to preserve the original pipeline context. Stage probability values transfer to Nutshell's Stage win probability percentages.

PipelineManager Deals map to Nutshell Opportunities. The deal name, value (amount), stage, owner, expected close date, and created/modified timestamps migrate. PipelineManager's pipeline and stage fields map to Nutshell's pipeline stage. Closed-Lost and Closed-Won dates migrate to Nutshell's last_activity_date and a custom closed_date field. Deals without a linked owner are flagged during scoping for reassignment to an active Nutshell user before migration.

PipelineManager People map directly to Nutshell People records. Core fields (name, email, phone, address, title, company association) migrate 1:1. The company link in PipelineManager People resolves to a Nutshell Company record created first so the People import satisfies the Company lookup. Custom properties on People (e.g., source_channel, preferred_contact_method) map to Nutshell custom fields of matching type (Text, Currency, Date, etc.). If a PipelineManager custom property type has no Nutshell equivalent, it is flagged for manual re-creation post-migration.

PipelineManager Company records map to Nutshell Company records. The company name, domain, address, phone, and industry fields migrate directly. Custom properties on Companies (e.g., account_tier, contract_value) map to Nutshell Company custom fields of equivalent type. The company is created before People import so that the People-Company association is preserved via Nutshell's linked Company field on People.

PipelineManager Activity logs (calls, emails, meetings, notes, and task records) migrate as Nutshell Tasks. Each Activity receives a Task record with the activity type preserved in a custom task_type field (Call, Email, Meeting, Note), the original timestamp set as Task due_date, and the content preserved in the Task description. Activity owner maps by email to the corresponding Nutshell user. Linked Deals or People attach via Nutshell's related record references. If an Activity references a PipelineManager Deal that was not migrated (e.g., closed-lost records excluded by scope), the Activity is linked to the associated Person record instead.

PipelineManager custom fields on People (Text, Number, Date, Dropdown, Checkbox, Currency) map to Nutshell People custom fields of equivalent type. Nutshell supports Text (225 char max), Long Text, Currency, Date, Number, Dropdown, and Checkbox for People custom fields. PipelineManager custom fields that use multi-select picklist, formula, or rollup types cannot migrate directly; we flag them in the discovery report and document the required Nutshell replacement field or manual workaround. Custom field labels are preserved as Nutshell field names; API names receive a pm_ prefix to avoid conflicts.

Same mapping logic as People custom properties applies to Companies. Nutshell Company custom fields support the same type set. PipelineManager custom properties on Companies that exceed Nutshell's supported types are flagged during discovery. We document each unmapped property with its PipelineManager type, current values, and a recommended Nutshell equivalent (e.g., a PipelineManager multi-select maps to a comma-separated text field in Nutshell as a manual workaround).

PipelineManager file attachments migrate to Nutshell's file storage as linked attachments to the parent People, Company, or Deal record. Filenames and original upload timestamps are preserved. We export attachments from PipelineManager via the platform's export interface, map them to the corresponding migrated record via the record's external ID, and upload to Nutshell. If a parent record was excluded from migration scope, its attachments are held in a reconciliation folder for the customer to review.

PipelineManager Owners map to Nutshell Users by email address. We extract all distinct owner IDs referenced on Deals, People, and Companies during discovery. Owners with a matching Nutshell user (by email) map directly. Inactive PipelineManager owners or owners without a Nutshell account are placed in a reconciliation queue; the customer's admin provisions the missing Nutshell user or reassigns the record to an active user before migration resumes. Owner history on Deals is preserved as the assigned Nutshell user on the migrated Opportunity.