Migrate from KulaHub to Nutshell

KulaHub has no separate Company or Account object; all business entities are stored as Contacts. We split KulaHub Contacts into Nutshell Company records (using email domain logic to group business entities) and Person records linked to the corresponding Company via AccountId. Individual contacts without a business domain (personal email addresses) are created as standalone Persons without a Company link. We preserve the original KulaHub Contact ID in a custom field kh_contact_id__c on the Nutshell Person record for reconciliation.

KulaHub activity logs (telephone calls, emails, system events) are stored per Contact as chronological time-series data. We export the full activity history and load it in date order into Nutshell's Activity timeline. Calls map to Task with TaskSubtype=Call; meetings map to Event; emails map to Task or Activity records depending on the Nutshell plan. We preserve the original KulaHub timestamp as the ActivityDate so the timeline ordering is intact on the Nutshell Person record.

KulaHub stores email campaigns, templates, open/click tracking, and GDPR unsubscribe preferences. Campaign metadata (name, dates, subject line) migrates to Nutshell Campaign records if the destination includes the Nutshell Engagement suite. GDPR unsubscribe flags and email preferences migrate as custom fields on the Person record so Nutshell respects existing suppression states. Open and click tracking history migrates as Activity records attached to the relevant Persons.

Documents attached to KulaHub Contact records are linked via a foreign-key relationship. We extract each document blob and re-associate it with the corresponding Nutshell Person record via the Attachment object. File names, sizes, and upload timestamps are preserved. Documents without a matching Person (orphaned during the split) are held in a staging table and presented to the customer for resolution before production migration.

KulaHub Tasks are assigned to specific users and linked to Contacts. We map tasks 1:1 into Nutshell Task records, preserving the assigned-user mapping by cross-referencing the KulaHub user list against the destination Nutshell user directory. Status, Priority, Due Date, and task body text transfer directly. Tasks assigned to users not yet provisioned in Nutshell go to a reconciliation queue.

KulaHub users appear in activity logs and task assignments. We export the full user list first so owner-ID mapping is resolved before any records that reference users are loaded into Nutshell. We match KulaHub users to Nutshell users by email address. Any KulaHub user without a matching Nutshell account is held in a provisioning queue for the customer's admin to create before record migration continues.

KulaHub captures website enquiry forms linked to Contact records, but the form-field schema is not publicly documented. We request a sample export of form-submission data during discovery to build the field mapping. Any unmapped fields are held in a staging table and presented to the customer for manual mapping before the production run. Form submission records migrate as custom field values on the corresponding Nutshell Person record.

KulaHub stores email unsubscribe states and GDPR preference flags per Contact, but the data format used to persist these preferences is not documented. We export the preference flags as custom Person fields (kh_email_opt_out__c, kh_gdpr_consent__c, kh_consent_date__c) in Nutshell so existing suppression lists carry forward without requiring re-opt-in campaigns. The customer should verify their GDPR documentation obligations in the destination jurisdiction before disabling the KulaHub suppression list.