Migrate from Kursaha to Nutshell

Kursaha Contact records (name, email, phone, company affiliation, behavioral properties) map to Nutshell People. Standard fields migrate directly where field names align (name, email, phone). Custom contact properties and behavioral event data stored in Kursaha require pre-migration audit to confirm export availability in the CSV; custom properties map to Nutshell People custom fields that we provision before import. Lifecycle stage data from Kursaha maps to a Nutshell People custom field (lifecycle_stage__c) since Nutshell does not have a native lifecycle stage property. Email opt-in status migrates to the standard Nutshell email_opt_out field.

Kursaha audience segments are defined by filter rules against contact properties. We reconstruct segment membership in Nutshell by importing all segment-associated People with a custom field segment_name__c set to the source segment identifier. Nutshell's People filtering and saved-list capabilities then allow the customer's admin to recreate segment rules as Nutshell People filters. Rule complexity that exceeds Nutshell's native filter builder (multi-condition, cross-field logic) is documented as a rebuild item. Segments with more than 20,000 members require batch import in chunks of 500 via Nutshell's REST API.

Kursaha Campaigns do not have a direct Nutshell equivalent because Nutshell is a CRM rather than a marketing automation platform. We offer two migration strategies: (1) map each active Kampaha campaign to a Nutshell Deal with the campaign name and status as the deal name and stage, preserving start and end dates as custom fields; or (2) create a custom Nutshell Campaign object via Nutshell's custom fields and API extensions for teams that need to track campaign attribution across deals. The choice is made during scoping based on the customer's reporting requirements.

Kursaha Channels are linked to campaigns rather than stored as independent objects. We preserve channel affinity by setting a custom field channel_source__c on the migrated Nutshell Person record to the channel(s) that contact engaged with most frequently. Channel-specific engagement counts (mail opens, WhatsApp replies, SMS deliveries) are noted as non-exportable analytics; we do not migrate them as discrete records.

Kursaha templates for each channel include content and styling. We migrate template text content and basic HTML structure to Nutshell Note records attached to the relevant Person or Company. Advanced AMP markup and interactive elements are flagged as a rebuild item because Nutshell does not support AMP email rendering natively. The template library does not carry over as reusable CRM templates without manual reconstruction in Nutshell.

Kursaha user accounts and role assignments (admin, editor, viewer) map to Nutshell User records. We create Nutshell Users by matching on email address from the Kursaha export. Role and permission mapping is noted in the inventory document; Nutshell's permission model (Admin, Standard, Restricted) differs from Kursaha's and requires manual reassignment by the customer's admin post-migration.

Kursaha's real-time analytics and campaign engagement metrics (opens, clicks, conversions, cohort analysis) are computed by the platform's processing layer and are not exported as discrete records. We do not migrate analytics event history. The customer should capture screenshots of any Kampaha analytics dashboards before cutover. Reporting is rebuilt in Nutshell from the migrated People, Company, and Deal data using Nutshell's built-in reporting and activity dashboards.

Kursaha integrations with third-party tools (forms, CRM connectors, analytics) are configuration-level settings that do not carry over during migration. Each integration must be reconfigured independently in Nutshell. We provide a written inventory of every active Kampaha integration identified during scoping, with recommended Nutshell equivalents (such as native Google Workspace sync for email and calendar, or Zapier for other SaaS connections).