Migrate from UPNIFY CRM to Nutshell

UPNIFY Client maps 1:1 to Nutshell Person. Standard fields (name, email, mobile phone, company association) migrate directly. Custom client fields map as key-value pairs into Nutshell custom fields on Person. WhatsApp conversation history is stored in UPNIFY's separate Connect data partition and does not ingest into Nutshell's activity model; we export it as a structured JSON archive and flag it for manual attachment by the admin post-migration.

UPNIFY Company maps to Nutshell Organization. We sequence Organization import before Person import so that the Organization-Person linkage is satisfied at insert time. Domain and address fields map directly; industry and employee-count fields map to Nutshell standard fields where present or to custom fields where the source data does not fit a default field.

UPNIFY Opportunity maps to Nutshell Deal. Pipeline stage names and IDs map via a customer-supplied stage mapping table. Deal value, expected close date, and owner assignment migrate directly. Loss reason and win reason from UPNIFY custom properties map to Nutshell's built-in loss reason field. Each UPNIFY pipeline maps to a Nutshell Deal pipeline configured before migration.

UPNIFY Prospect maps to Nutshell Lead. Prospects represent pre-qualified leads in a separate object from Clients, which maps cleanly to Nutshell's Lead object. We resolve any lifecycle-stage values (lead quality, source, score) as custom fields on the Lead record. The customer chooses whether to migrate Prospects as Leads pending conversion or as Persons already qualified, based on their sales process.

UPNIFY Quotations map to Nutshell Quote with a significant transformation step. Quotations carry embedded multi-currency exchange-rate metadata that must be flattened into a single base-currency price field. We extract the quotation line items, convert to the customer's preferred base currency using the embedded rate, and load the normalized Total and line-item amounts into Nutshell's Quote object. Currency metadata is stored in a custom field for audit.

UPNIFY Products under Catalogs migrate to Nutshell Products. Product name, SKU, price, and description migrate directly. Stock-level data is not consistently populated in UPNIFY and is flagged as a gap if present. If the customer uses Nutshell Quotes, we create Price Book entries alongside Product records.

UPNIFY Calendar entries (tasks, reminders, appointments) migrate to Nutshell Tasks. Task title, status, due date, owner, and completion flag migrate directly. Completed versus open status is preserved. Appointment-type calendar entries with start and end times migrate as Tasks with a date field and a note indicating the original appointment window.

UPNIFY Goals track team or user-level sales targets. Nutshell does not have a native Goals object, so we migrate goal name, period, target value, and owner assignment as custom fields on the related User or Deal record. The customer chooses the target object during scoping. Historical goal records are preserved as read-only reference data.

UPNIFY tags are applied across Clients, Companies, and Opportunities for segmentation. Nutshell supports Tags on Person, Organization, Lead, and Deal. We export all tag assignments per object and reconstruct the tag list in Nutshell, preserving which object each tag was attached to. Tags with more than 50 distinct values are flagged for the admin to consolidate if they exceed Nutshell's tagging limits on the target plan.

Custom fields on UPNIFY Clients, Companies, and Opportunities (types: text, number, date, dropdown) map to Nutshell custom fields on the equivalent objects (Person, Organization, Deal). Field types that do not match exactly — for example, a UPNIFY multi-select dropdown migrating to a Nutshell single-select — are flagged for the admin to resolve before migration. Custom field limits vary by Nutshell plan and are checked during scoping.