Migrate from Unanet CRM by Cosential to Nutshell

Unanet Organizations map directly to Nutshell Companies. Both represent a business entity with name, address, industry, and contact associations. We map Organization.name → Company.name and Organization.address fields to Nutshell's address fields. Multi-branch organizations in Unanet collapse to one Nutshell Company record with the primary address; branches can be tracked via custom fields if required.

Unanet Persons map to Nutshell People — a one-to-one translation for most fields. Person.firstName, Person.lastName, Person.email, Person.phone, Person.title, and Person.address map directly. Person records that represent leads in Unanet (identified by lifecycle status) route to Nutshell's Lead model rather than Person, based on the source lifecycle value we read from the API response.

Unanet Persons without an assigned role on an active Organization — or Persons flagged as prospects in Unanet's internal status — migrate to Nutshell Leads. This split prevents a Person record from existing without a primary company link in Nutshell. The source API's person status field drives the split; we preserve the original status as a Nutshell custom field for audit continuity.

Unanet Pursuits are the closest analogue to Nutshell Deals. Pursuit.pursuitName → Deal.name, Pursuit.estimatedValue → Deal.value, Pursuit.probability → Deal.probability (mapped to Nutshell's probability field if present), and Pursuit.closeDate → Deal.closeDate. Pursuit stage names map to Nutshell pipeline stage names via a value-by-value lookup table we build during discovery.

Unanet's configurable pursuit stages (e.g., Prospect, Qualified, Proposal, Negotiation, Won, Lost) map to Nutshell pipeline stage names. We create a value-mapping table during scoping: each Unanet stage string maps to the closest Nutshell stage name. Probability values associated with each Unanet stage carry forward as custom fields on the Nutshell Deal since Nutshell's built-in probability is per-stage by default on certain tiers.

Unanet allows multiple Persons to be associated with an Organization in an N:N relationship, each with a role label (e.g., Estimator, PM, Principal). Nutshell Person has a single primaryCompany field. We set the primary company to the most recently modified Organization-Person association, and store additional role labels as comma-separated tags on the Nutshell Person record so the full relationship history is searchable.

Unanet Organization custom fields (e.g., NAICS codes, bonding capacity, contract type preferences) require corresponding custom fields to be created in Nutshell before migration. We create each custom field via Nutshell's Settings → Custom Fields API, matching the field type (text, number, date, picklist) from Unanet's Compass API field definition. Picklist custom fields in Unanet require a full value-mapping list in Nutshell.

Unanet Person custom fields (e.g., professional certifications, licenses, secondary phone numbers) migrate to Nutshell Person custom fields. Field type conversion follows the same logic as Organization custom fields. Cosential stores some person metadata in the Person.FirmName field for organization-less persons; we parse this and route it to the appropriate Nutshell field during transformation.

Pursuit custom fields (e.g., project type, contract vehicle, incumbent status, past performance ratings) migrate to Nutshell Deal custom fields. These fields are critical for AEC firms tracking pursuit-specific attributes beyond stage and value. We map field types exactly and preserve picklist values as Nutshell picklist options where available.

Unanet activity records attached to a Person or Pursuit map to Nutshell Activities with the matching type. Call activities → Nutshell Call, Email → Nutshell Email, Meeting → Nutshell Meeting, Note → Nutshell Note. Original timestamps, activity owners (resolved by email match to Nutshell users), and parent record links (Person or Deal) are preserved. Nutshell's activity model supports rich text notes.

Unanet file attachments on Organizations, Persons, and Pursuits are downloaded from the Compass API and re-uploaded to Nutshell's file storage, linked to the corresponding Nutshell record (Company, Person, or Deal). File size limits on Nutshell's storage apply; files exceeding limits are flagged before migration and handled case-by-case.

Unanet owner assignments on Pursuits and Persons are resolved by email match against Nutshell Users. If a Unanet owner email has no matching Nutshell User, the record is assigned to the Nutshell account admin and the unmatched owner email is stored in a Source_Owner_Email__c custom field for post-migration reassignment.

Unanet workflows, pursuit gating rules, and automated alerts do not migrate to Nutshell. These are destination-side automation constructs with no structural equivalent in Nutshell. We export the workflow definitions as a JSON reference file from Unanet's Compass API so your Nutshell admin can rebuild equivalent rules in Nutshell's automation tools.

Unanet's proposal automation templates and generated proposals are document artifacts, not CRM data. They do not migrate. We export a list of proposal template names and field mappings as a reference document for rebuilding in Nutshell's proposal tools or a third-party proposal platform.