Migrate from Pipeliner CRM to Nutshell

Pipeliner Account records map directly to Nutshell Company. The Account Name becomes the Company name field, and any custom fields on the Account migrate to custom fields on the Company object assuming the destination Nutshell plan supports custom fields (Pro tier and above). Account website, address, and industry fields map to their Nutshell equivalents. We use the Company record as the parent anchor so that related People records can reference it via CompanyId during the import phase.

Pipeliner Contact records map to Nutshell People. If the Contact is linked to an Account, we set the People.CompanyId to the migrated Company record during import. First name, last name, email, phone, title, and all standard fields migrate directly. Custom fields on Contact map to People custom fields. We flag any Contact records where the associated Account was not migrated (due to deletion or data cleaning) so the customer can decide whether to import them as standalone People or exclude them.

Pipeliner Lead records map to Nutshell People with the Lead status flag set to indicate pre-conversion status. Lead score, lead status, and source fields from Pipeliner migrate to Nutshell People custom fields. We do not merge Leads and Contacts into a single import pass—Leads are imported after Companies and People are in place so that the Lead-to-Account association resolves correctly. Customers who do not use Pipeliner's separate Lead object (many SMB teams use Contacts only) skip this step entirely.

Pipeliner Opportunity records map to Nutshell Deal. The Opportunity name becomes the Deal name, amount maps to Deal value, close date maps to expected close date, and stage maps to the corresponding Nutshell pipeline stage. We resolve Opportunity.AccountId to the migrated Nutshell CompanyId at migration time and set Opportunity.OwnerId to the matching Nutshell User. Stage probability percentages from Pipeliner are stored as a custom field in Nutshell because Deals do not natively expose probability in the same way.

Pipeliner Quotes linked to Opportunities map to Nutshell's built-in Quoting tool, which is available on Pro and above plans. Quote line items and totals migrate to Nutshell Quoting line items, and the linked Account and Opportunity map to the corresponding Nutshell Company and Deal. If the customer is on Nutshell Foundation (no Quoting tool), we flag this during scoping and either exclude Quote migration or document a post-migration manual setup. Nutshell Quoting requires the customer to configure products and a price list before Quotes can be attached to Deals.

Pipeliner Product catalog items map to Nutshell Products. Product name, SKU, unit price, and description migrate to the Nutshell Product object. Products linked to Opportunities via Pipeliner's Product Grid migrate as line items on the corresponding Nutshell Deal. We confirm during scoping whether Nutshell's Quoting tool is enabled on the destination plan because Product-to-Quoting-line-item mapping depends on it.

Pipeliner Activities (Tasks and Appointments) linked to Accounts, Contacts, or Opportunities map to Nutshell Activity records linked to the corresponding Company or People record. Appointment start and end times, location, and notes migrate to Nutshell Activity fields. Task status, priority, and due date map directly. We resolve the parent record (Company or People) by matching against the migrated Pipeliner entity IDs.

Pipeliner Project records link to Accounts, Contacts, and Opportunities with date-based tracking. Nutshell does not have a native Project object. We flag all Project records during scoping and ask the customer to choose between migrating Project data as Notes attached to the related Company or Deal, or excluding Projects from the migration scope. Projects are not a standard CRM object in Nutshell and there is no native replacement within the platform.

Pipeliner supports fully custom entity creation beyond its eight standard objects. Nutshell does not have a general-purpose custom entity model. Any custom entities the customer has created in Pipeliner must be assessed individually during scoping: if the data can be restructured as custom fields on a standard Nutshell object (Company, People, Deal) we apply that transformation; if the data requires a true separate object, we exclude it and document the gap for the customer to address in a separate engagement or via Nutshell's API-based custom storage.