Migrate from Pipz to Nutshell

Pipz Contacts map directly to Nutshell People records. The primary fields (name, email, phone, address) migrate 1:1 to their Nutshell equivalents. Custom fields on Pipz Contacts migrate to Nutshell Person custom fields, which are created during the pre-migration schema phase. Pipz's Customer Engagement Index is a proprietary behavioral score with no native Nutshell equivalent; we preserve it as a custom numeric field (cei_score) on the Nutshell Person record. Activity association (which Pipz contacts logged which events) resolves via the Contact-to-Person lookup after People records are created.

Pipz Companies map to Nutshell Companies as organizational records. Nutshell People can be linked to multiple Companies, which handles Pipz's scenario where a contact is associated with more than one organizational record. The Company is created in Nutshell before any linked People are inserted so that the lookup relationship is satisfied at the time of Person import. Website, industry, size, and address fields migrate where present on the source Pipz Company record.

Pipz Deals map to Nutshell Opportunities with deal name, value, owner, stage, and close date preserved. The Pipz deal stage maps to the closest Nutshell pipeline stage by name, and any stage probability from Pipz is noted for manual configuration in Nutshell if the customer uses the Pro or Enterprise pipeline goals feature. Closed-Lost and Closed-Won Pipz deal statuses translate to the equivalent Nutshell Opportunity status.

Pipz pipeline stages are transferred as Nutshell pipeline stage names with their relative ordering preserved. Pipz allows automation triggers attached to stage transitions; these do not migrate to Nutshell because Nutshell's pipeline stages are sales-process markers without built-in trigger logic. We deliver a stage-transition trigger list as part of the automation inventory document so the customer's admin can evaluate which stage transitions warrant Nutshell workflow rebuilds.

Pipz Activities span email opens, link clicks, chat conversations, page views, and automation-triggered events. We map each activity type to a Nutshell Task record: email-related events become Task with a type marker, chat sessions become Task with a notes field containing the transcript excerpt, and page views become informational Task entries with the URL in the notes. The original Pipz timestamp (created_at) is preserved as the Nutshell Activity Date so the timeline ordering is intact in Nutshell's activity log.

Pipz Email Campaign records contain metadata (name, subject, send date, status, contact list membership) that migrates to Nutshell as a List record with campaign name and description preserved. Campaign performance metrics (open rate, click rate) do not have a native Nutshell equivalent and are documented in the migration inventory for the customer's reporting rebuild. Email campaign automation triggers (which Pipz uses to enroll contacts in workflows based on campaign actions) do not migrate; they are listed in the automation inventory document.

Pipz Smart Segments are built from demographic rules, tag conditions, and behavioral event filters. Nutshell does not have a native segment-builder equivalent; we transfer segment definitions as written filter criteria (field names, operators, values) in the migration inventory so the customer's admin can recreate them as saved People filters or Nutshell List memberships. The underlying tag and event data that feeds the segment logic does migrate, so the admin has the raw material to rebuild the segment in Nutshell.

Pipz tags are a flexible labeling system applied across Contacts, Companies, Deals, and Campaigns. Nutshell People do not have a native multi-value tag field; we map Pipz tags to a Nutshell custom text field (tags) as a comma-separated string, preserving the full tag set per record. If the customer uses tags for segmentation or reporting, we recommend creating a dedicated custom field per major tag category during the pre-migration schema phase to enable filterable tag-based views in Nutshell.

Pipz custom fields on Contacts, Companies, and Deals map to Nutshell custom fields on Person, Company, and Opportunity respectively. We extract the full field definition including type, options, and default values during scoping. Nutshell supports Text, Long Text, Currency, Date, Number, and Dropdown custom field types. We perform type-mapped creation of each Nutshell custom field before record migration so that the target schema is in place. Pipz custom fields with Pipz-specific automation trigger references are flagged in the field inventory for the customer to evaluate post-migration.

Pipz Users map to Nutshell Users by email address match. Owner assignments on Contacts, Companies, Deals, and Activities resolve via the Nutshell User lookup after the User table is confirmed. Pipz includes unlimited team members on any paid plan, which may exceed the Nutshell seat count if the customer licenses only a subset of Pipz team members. We flag the user count differential during scoping and the customer determines which Pipz users become Nutshell licensed users versus inactive/invited observers.