Migrate from Unim to Nutshell

Unim's standard Contact entity base fields (name, email, phone, address) map directly to Nutshell Person fields. We resolve any active custom fields on the Contact ModelID at schema discovery time and create corresponding Nutshell custom fields on Person before the record import begins. The email field on Person is used as the dedupe key during import, with duplicate records merged or flagged per the customer's preference.

Unim Company records map to Nutshell Company. Standard fields (company name, domain, address, phone) map 1:1. Any active custom fields on the Company ModelID in Unim translate to Nutshell Company custom fields. We create the Company record in Nutshell before importing any related Person records so that the Person-to-Company link is satisfied at insert time.

Unim Deal records map to Nutshell Deal with Deal name, value, and stage. We inspect the Unim deal stage set at schema discovery and map each stage to the corresponding Nutshell pipeline stage value. Closed-won and closed-lost dates from Unim migrate as Nutshell Deal close date fields. Custom fields on Deal in Unim migrate to Nutshell Deal custom fields.

Unim Activity records—calls, emails, meetings, tasks, and notes—carry timestamps, owner references, and optionally linked custom fields. We preserve the activity-to-Person or activity-to-Company linkage by resolving the Nutshell Person or Company record ID at migration time. Call duration and disposition from Unim migrate to Nutshell Call custom fields. Meeting details migrate to Nutshell Activity records with start/end time and location preserved.

Unim exposes a dedicated custom-fields API route with Name, ModelID, DataType, and Nullable flag. DataTypes are looked up via the valuelists endpoint. We query this endpoint during schema discovery, map each Unim datatype to the equivalent Nutshell custom field type (Text, Long Text, Currency, Date, Dropdown, Checkbox), and create the fields in Nutshell before the record migration begins. Nutshell text fields carry a 225-character limit on lower plans; we truncate any Unim text values exceeding this limit and flag the truncation in the migration report.

Bespoke object types beyond the standard Contact/Company/Activity triad are defined at the application level in Unim. We discover these via schema introspection and handle each as an additional migration object. If Nutshell's custom field model cannot represent the bespoke entity (for example, if the entity has multiple independent relationships), we represent it as a linked Note or a custom object on the highest-tier Nutshell plan available to the customer, with the full original payload preserved as structured JSON in a Long Text field for audit recovery.

Attachments in Unim are served via the Files dimension, not inline with the record. Each attachment requires a separate API call to fetch the binary. We paginate file extraction to avoid overwhelming the Unim API, apply retry logic on 429 responses, and re-associate files with the target records in Nutshell as linked attachments, preserving original filenames and content types.

Tag associations in Unim are stored as separate linked records or array fields depending on the specific deployment. We preserve tag-to-record linkages as a join table during migration and apply them to the corresponding Nutshell Person or Company records as tags. Nutshell's tagging model applies tags at the Person or Company level; tags that were entity-specific in Unim are preserved as a text list in a custom field if no equivalent direct tag mapping exists.