Migrate from KulaHub to Zoho CRM

KulaHub Contacts with a clear individual name and no associated business entity map to Zoho CRM Contact. Contacts that contain company-level fields (company name, business address, business phone) are flagged for the Account split. KulaHub's lifecyclestage-equivalent property (if present) maps to Zoho Lead Status for Contacts flagged as prospects and is preserved as a custom field kula_lifecycle_stage__c for audit. We split at migration time using a pre-approved mapping matrix provided by the customer during scoping.

KulaHub has no separate Company object, so company-level data embedded in Contact records must be extracted into Zoho CRM Accounts before the corresponding Contacts are linked. We run a field audit during discovery to identify all company-typed fields in the KulaHub Contact schema, create Zoho Accounts first, then re-link each Contact by resolving the AccountId lookup. Any company-level data that cannot be cleanly split (e.g., records where the individual and company fields are ambiguous) is held in a reconciliation queue for the customer's admin to disambiguate before the production run.

KulaHub call logs map to Zoho CRM Tasks with Task Subtype set to Call. Call duration, disposition, and outcome migrate to custom fields call_duration__c and call_disposition__c. Activity timestamps preserve chronological ordering by setting the Task Due Date to the original KulaHub event time.

KulaHub email engagements migrate to Zoho CRM Tasks (for the activity timeline entry) with email content stored as an associated Note record. Subject, body, sender, and recipient data transfer from the KulaHub engagement record. The Task links to the resolved Contact or Account via the WhatId field.

KulaHub task engagements map directly to Zoho CRM Tasks, preserving Status, Priority, Due Date, and assigned owner. Owner resolution uses the email-based user mapping. Tasks without a resolvable owner are placed in a staging queue for admin review.

KulaHub meeting records map to Zoho CRM Events with Start DateTime, End DateTime, Location, and description preserved. Attendee information migrates as Event Participants linked to the corresponding Contact or Account records in Zoho.

Documents attached to KulaHub Contacts are extracted as binary blobs and re-uploaded to Zoho CRM as Attachments linked to the corresponding Contact or Account record. We preserve the original filename and content type. Attachments exceeding Zoho's size limit (25 MB per file) are flagged for the customer to assess as cloud storage alternatives.

KulaHub email campaigns, templates, and tracking data (open counts, click counts, unsubscribe status) do not map to a standard Zoho CRM module. We export the campaign history as key-value records and write them as custom fields on the associated Contact (campaign_name__c, last_email_sent__c, email_open_count__c, email_click_count__c). GDPR unsubscribe preferences migrate to the standard Zoho Email Optout field. Campaign-level summary data is written as a Note on the primary Contact.

KulaHub users are exported by email address and matched to Zoho CRM Users by email. Any KulaHub user without a matching Zoho User is held in a reconciliation queue; the customer's Zoho admin provisions the missing user before record import resumes. Inactive KulaHub users are matched to inactive Zoho Users to preserve historical ownership on closed records.

KulaHub form submission data is not mapped to a standard Zoho CRM object. The form-field schema is not publicly documented, so we request a sample export of form submission data during discovery. Each unique form field becomes a custom Contact field in Zoho CRM (prefixed kula_form_). Fields that do not map cleanly to a Zoho field type (e.g., multi-select) are written as text fields and flagged for admin review.

KulaHub's GDPR unsubscribe flags and email preference data transfer to the Zoho CRM standard Email Optout field and to custom preference fields (kula_email_consent__c, kula_consent_date__c) on the Contact. We export the preference data as a structured custom field set so the destination system can respect suppression lists without requiring a separate consent management tool.

KulaHub reports and CRM activity reports are not migrated as functional Zoho reports because the two platforms have different schema and metric definitions. We include a CSV export of available KulaHub reports in the scope delivery so the customer's admin has the raw data to recreate reports in Zoho's report builder. Zoho CRM's Standard and higher tiers include a built-in report builder with over 25 pre-configured report types.