Migrate from Clientify to Nutshell

Clientify Contacts map directly to Nutshell People. The standard fields (name, email, phone, address) migrate as-is. Custom properties on Clientify Contacts map to Nutshell custom fields on Person, but picklist-type custom properties require pre-creation of the picklist values in Nutshell before the import runs or the records will be rejected. Lead score from Clientify migrates to a numeric custom field for visibility in Nutshell reporting.

Clientify Companies map to Nutshell Companies with a 1:1 mapping on standard fields including company name, industry, size, website, and address. The Company-API-name deduplication key is preserved. We resolve any Company references from Contact records before inserting so that the relationship is satisfied on import.

Clientify Deals map to Nutshell Deals with deal name, value, owner, expected close date, and stage preserved. The Clientify pipeline stage order is mapped to Nutshell's stage sequence, and stage probability percentages transfer where present. Closed-won and closed-lost status maps directly. Any Clientify custom properties on Deals migrate to Nutshell custom fields on Deal.

Clientify pipeline stage names and ordering are read from the export and replicated as Nutshell Deal stages. Nutshell's default pipeline is used for migrations without multi-pipeline requirements; if Clientify uses multiple pipelines, we configure Nutshell's multiple-pipeline feature (available on Pro plan) during schema setup. Stage probability percentages transfer with rounding to Nutshell's supported range.

Clientify Leads (distinct from Contacts in Clientify) map to Nutshell Leads. Lead source, status, and score fields migrate to equivalent Nutshell Lead custom fields. Any lead scoring values from Clientify's AI features transfer as numeric fields in Nutshell. The customer's team determines post-migration whether to convert Leads to People or keep them separate in Nutshell's funnel.

Clientify activity records (logged calls, emails, meetings, and notes tied to Contact or Deal records) map to Nutshell Activity records. Timestamp formats are normalized to match Nutshell's expected datetime format. Activity type labels (call, email, meeting) map to Nutshell's activity type taxonomy. Notes from Clientify migrate to Nutshell's activity-based note system tied to the relevant Person or Company.

Clientify Tasks migrate to Nutshell Tasks with Status, Priority, Due Date, and assigned owner preserved. Task assignment resolves by matching Clientify owner email to Nutshell User. Open tasks migrate as open; completed tasks migrate with their completion timestamp. Any task descriptions transfer to Nutshell's task notes field.

Clientify Owners (CRM users) are mapped to Nutshell Users by email address match. Active and inactive status is preserved. Role and permission settings in Clientify do not transfer; Nutshell's permission model is configured post-migration by the customer's admin. Owners without a matching Nutshell User go to a reconciliation queue for admin provisioning before record migration proceeds.

Clientify tags on Contacts, Companies, and Deals migrate to Nutshell tags. Tags used for segmentation or filtering transfer as-is. If tags represent a large multi-select classification system, we coordinate with the customer during scoping to determine whether they want a tag consolidation strategy or a direct 1:1 migration.

Clientify campaign records with performance metrics (open rates, click rates, sent counts) export and migrate to Nutshell Campaign records. Campaign execution logic including A/B test configurations, trigger conditions, and send-time automation remain in Clientify's campaign builder and must be documented for manual rebuild in Nutshell's email tools or a third-party platform. Campaign performance history migrates as a data record, not as executable campaign logic.