Migrate from User.com to Nutshell

User.com Contacts map directly to Nutshell People. The primary email address becomes the Person's email field. We normalize any Bool values that export as f/t back to proper boolean representations before loading. Address, phone, and custom properties migrate to Nutshell's standard Person fields and custom Person fields respectively. All records that carry an email, phone, or chat_interaction attribute in User.com are flagged as having billing-triggering attributes — this matters only for teams returning to a contact-metered platform, but we include it in the record profile for completeness.

User.com Company records map to Nutshell Company records. The company name, domain, address, phone, and industry fields align directly. We preserve the company-contact association by importing Companies before People and resolving the Company lookup reference on each Person record at the time of insert. Nutshell's Company object does not support custom objects, so any User.com company-level custom properties migrate to Nutshell Company custom fields.

User.com Deals map to Nutshell Deals. Deal stage, value, owner, expected close date, and custom deal fields migrate directly. We map the User.com deal pipeline to Nutshell's deal status or a custom pipeline configuration depending on the complexity of the source pipeline. Closed-won and closed-lost statuses translate to Nutshell's Won and Lost deal states. Deals without an associated contact in User.com are loaded as unlinked deals in Nutshell and flagged for manual association.

User.com Events (calendar and activity events) map to Nutshell Activities. Event timestamps migrate in ISO 8601 format and are normalized during the transform phase. Attendee lists migrate as Activity party records linked to the relevant Person or Company. Event type attributes (meeting, call, task) map to Nutshell's activity type taxonomy.

User.com custom properties on Contacts, Companies, and Deals are exported with their full schema and mapped to Nutshell's custom field structure. Choice and fixed-choice fields in User.com use {} bracket notation in the export — we normalize these to comma-delimited values compatible with Nutshell's custom field format. Nutshell's field type support includes Text, Long Text, Currency, Date, and Number (per the Nutshell Help Center). Fields that do not map to a supported Nutshell type are flagged for manual field creation before migration.

Tags assigned to Contacts and Deals in User.com migrate to Nutshell Tags on the corresponding Person and Deal records. Tag values transfer as-is; no transformation is required since both platforms use simple string tag arrays. Teams that used tags as a segmentation proxy in User.com should be aware that Nutshell Tags are labels, not dynamic group definitions.

User.com dynamic Segments — groups of Contacts re-evaluated on attribute and behavior conditions — have no equivalent in Nutshell, which uses static Lists. We export each Segment's membership at migration time and create a corresponding Nutshell Static List containing exactly the Person records that matched the segment criteria on the export date. The list is static; it does not update dynamically after migration. We flag this limitation explicitly and recommend the customer document segment criteria for manual list refreshes.

User.com Activities — logged calls, emails, meetings, tasks, and notes — map to Nutshell Activities. Email opens, chat sessions, and push notifications have behavioral metadata that requires field-level mapping to Nutshell's activity model. We preserve the activity timestamp, owner, and description fields, and flag any activity type that has no direct Nutshell equivalent.