Migrate from UPilot to Nutshell

UPilot Contact records map directly to Nutshell People. Standard fields (name, email, phone, company association) migrate 1:1. UPilot's 360-degree contact view embeds task context alongside contact records; in Nutshell, task relationships link via People-Activity associations rather than embedded display. We preserve task associations as linked Activity records rather than embedding, requiring the destination team to adjust workflow expectations for viewing task context.

UPilot Company records map to Nutshell Company records. The one-to-many relationship with Contacts (People in Nutshell) is preserved via the People-Company link field. We use company name or domain as the dedupe key during import. Nutshell's Company object does not support nested hierarchies; parent-company structures in UPilot flatten to separate Company records.

UPilot Deals map to Nutshell Deals with deal value, stage, expected close date, and associated contacts (People) preserved. Multiple contacts per deal with role assignments migrate as linked People records. We map UPilot's pipeline stage names to Nutshell's stage names and configure the stage probability settings during migration.

UPilot organizes Deals into colored pipeline views with customizable stages. We map the pipeline structure and stage history to Nutshell's pipeline configuration. Nutshell supports pipeline customization including stage names, colors, and probability percentages. Stage history (dates of stage transitions) migrates as Activity records or custom fields if the customer requires that level of audit trail.

UPilot Tasks migrate to Nutshell Activities (Tasks). Task status, priority, due date, and description transfer. Task associations with Contacts (People) and Deals migrate as linked Activity records. Note that UPilot's inline task editing in pipeline view has no direct Nutshell equivalent; tasks display in a separate Activity feed in Nutshell rather than embedded in pipeline rows.

UPilot custom fields on Contacts, Companies, and Deals require field-level mapping to Nutshell's custom fields. Nutshell creates custom fields for Companies, People, and Leads but handles them via the API customFields dictionary rather than a dedicated UI for all field types. We create the custom field definitions in Nutshell first, then map UPilot field values using the field name as the key in the customFields object. Nutshell supports Text (225 char max), Long Text, Currency, and Date field types for custom fields.

UPilot Support Tickets migrate to Nutshell Cases if the destination includes Nutshell's optional support functionality. Ticket pipeline becomes Case pipeline, ticket stages become Case status values, and conversation threads migrate as Activity records linked to the Case. Note that UPilot's email and live chat integration semantics differ from Nutshell's; threading may not preserve exactly as displayed in UPilot.

UPilot Owners (users) map to Nutshell Users. We resolve owners by email match. Any UPilot Owner without a matching Nutshell User goes to a reconciliation queue for the customer to provision before record import resumes. Owner assignment on Deals and Tasks migrates once the User mapping is validated.