Migrate from Kursaha to Zoho CRM

Kursaha Contacts with behavioral properties (lifecycle stage, engagement score, tags) map to Zoho CRM Leads for unqualified prospects and Contacts for qualified buyers. We extract behavioral properties from the Contact CSV export as custom fields on both Lead and Contact in Zoho (lifecycle_stage__c, engagement_score__c, hs_createdate__c for the original Kursaha creation date). The split rule is defined during discovery based on the customer's lifecycle stage matrix. Any custom behavioral properties require pre-migration audit to confirm they appear in the dashboard export field list.

Kursaha Campaigns map to a combination of Zoho objects. Campaign name, status, start/end dates, and channel assignments migrate as a custom Campaign__c module with fields for campaign metadata. Campaign-audience membership (which Contacts were in which Campaign) migrates as a Campaign Members custom object linking to Lead and Contact. Individual Campaign performance metrics (opens, clicks, conversions) cannot be migrated because they are computed by Kursaha's processing layer and are not discrete exportable records. We document this data loss and recommend the customer capture screenshots before cutover.

Kursaha Audience Segments defined by filter rules against contact properties map to Zoho CRM Workflow Rules (for automated tag assignment and list population) or Advanced Filters (for manual segmentation). We export the segment definition from the dashboard, translate the rule conditions into Zoho Deluge script for workflow criteria, and deliver the reconstructed rules as part of the written automation inventory. Highly complex segments with more than 10 conditions or nested rule groups may require simplification or manual recreation in Zoho Advanced Filters.

Kursaha channel associations attached to Campaigns or Contacts map to Zoho CRM Tags on the Contact or Lead record (mail_subscriber, whatsapp_opted_in, sms_consent). Email template content from Kursaha migrates as Zoho CRM Email Templates. WhatsApp and SMS templates migrate to Zoho WhatsApp Message Templates or Zoho SMS Templates respectively, subject to Zoho's channel integration setup (WhatsApp Business Account linking, SMS gateway configuration). Channel-specific template styling may require adjustment in Zoho's template editor.

Kursaha templates for each channel include content and basic HTML structure. We migrate template text content and standard HTML markup to Zoho CRM Email Templates, WhatsApp Business Templates, and SMS Templates. AMP markup and interactive elements used in Kursaha email templates are flagged as requiring rebuild in Zoho because Zoho does not support AMP in standard email templates. Plain text content migrates without transformation.

Kursaha user accounts with admin, editor, and viewer roles map to Zoho CRM User records. We map admin to Zoho Standard Role and editor to Zoho Professional Role with the appropriate module-level permissions. Viewer maps to a Zoho custom role with read-only access. Since Kursaha does not appear to support SSO or directory integration, we provision Zoho User accounts manually using the source email address as the username. User assignment on Contact, Campaign, and Segment records is resolved by email match during migration. Any owner references without a matching Zoho User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Kursaha campaign activity logs (sends, opens, clicks, replies, unsubscribes) are computed platform metrics, not discrete exportable records. We do not migrate campaign activity logs. The customer should capture screenshots of campaign performance dashboards before cutover. Post-migration, Zoho CRM's built-in reporting and Zoho Analytics provide campaign performance tracking for new campaigns created in Zoho.

Kursaha custom properties on Contact records (beyond standard fields like name, email, phone, company) migrate as Zoho CRM custom fields on the Lead or Contact module. We pre-create custom fields during the Zoho schema setup phase, mapping the Kursaha property type (text, number, date, checkbox, dropdown) to the corresponding Zoho field type. Multi-select custom properties map to Zoho Multi-Select fields. Any custom properties not present in the dashboard CSV export are flagged during scoping for manual data entry or alternative export method exploration.

Kursaha custom fields on Campaign records migrate as custom fields on the Campaign__c custom module we create in Zoho. Standard Campaign fields (name, status, start date, end date, channel assignment) map to standard fields on the custom module. Custom campaign properties (budget, target audience size, UTM parameters) are created as Zoho custom fields during the schema setup phase. The customer confirms the complete list of custom campaign fields during the discovery call before CSV export begins.

Kursaha integrations with third-party tools are configuration-level settings (form embeds, webhook URLs, third-party analytics connections) that do not carry over as records during migration. Each active integration requires manual reconfiguration in Zoho CRM using Zoho's native connectors, Zoho Flow, or webhook-based integrations. We deliver a written inventory of detected integrations during discovery so the customer can plan reconfiguration. This is outside standard migration scope but we surface it proactively to prevent post-migration surprises.