Migrate from Kursaha to Salesforce Sales Cloud

Kursaha Contacts map to Salesforce Lead for unqualified prospects and Contact for qualified buyers. We use the contact's lifecycle status, engagement score, and campaign membership to determine placement. Any Kursaha Contact with active pipeline association or closed-won campaign history maps to Salesforce Contact with a resolved AccountId reference. The original Kursaha contact ID and behavioral properties (engagement_score, last_activity_date) migrate as custom fields on both Lead and Contact for audit and reporting continuity.

Kursaha Campaigns are the central object and map to Salesforce Opportunity. Campaign name becomes Opportunity Name, start and end dates map to CloseDate, campaign status maps to Opportunity StageName with a custom hs_campaign_status__c field preserving the original Kursaha status value. Channel assignments (mail, WhatsApp, SMS) migrate as multi-select picklist fields on the Opportunity so sales reps can see the original campaign channel in the CRM record.

Kursaha Campaign records also create Salesforce Campaign records to preserve marketing attribution history. Opportunity.CampaignId links the sales Opportunity to the marketing Campaign for influence reporting. Campaign member status from Kursaha (subscribed, unsubscribed, bounced) maps to Salesforce CampaignMember Status values.

Kursaha Audience Segments are defined by filter rules against contact properties. We reconstruct these as Salesforce Campaign records with Campaign Members added based on the segment criteria, or as Static Lists using custom List__c objects with ListMember__c junction records. Rule complexity (nested conditions, date-based filters) is flagged during scoping because advanced segment logic may require manual recreation in Salesforce Reports and Filters rather than automated migration.

Kursaha Channels (mail, WhatsApp, SMS) are linked to Campaigns rather than stored as independent objects. We preserve channel-to-campaign associations as a custom multi-select picklist field channel_type__c on the Opportunity. Channel-specific templates migrate as Notes attached to the parent Campaign or Opportunity record with a naming convention identifying the channel (e.g., EMAIL_TEMPLATE, WHATSAPP_TEMPLATE).

Kursaha templates for each channel include content and basic HTML structure. We migrate template text content and HTML as Salesforce Note records linked to the relevant Campaign or as Salesforce EmailTemplate records for mail templates. Advanced AMP markup and interactive elements do not migrate; we flag these as requiring rebuild in Salesforce using Lightning Email Templates or Marketing Cloud Content Builder. Channel assignment (mail, WhatsApp, SMS) is preserved as a Note Title prefix.

Kursaha user accounts (admin, editor, viewer roles) map to Salesforce User records. We resolve users by email match against the destination Salesforce org. Any Kursaha user without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import. Role and permission sets are not migrated as code; we deliver a role mapping table for the admin to configure post-migration.

Kursaha stores behavioral properties on Contact records (engagement_score, lifecycle_stage, tags). We map these to custom fields on the Salesforce Lead or Contact object (e.g., engagement_score__c, kursaha_lifecycle_stage__c, tags__c as multi-select picklist). Custom field creation happens in the destination Salesforce org during schema design phase, deployed to Sandbox for validation before production migration.

Campaign engagement activity (email sends, opens, clicks, meeting registrations) from Kursaha's activity log migrates as Salesforce Task and Event records linked to the corresponding Campaign and Contact. We use the Bulk API for large activity volumes, chunking by ContactId and setting WhoId on Task/Event to the migrated Contact record. Activity timestamp is preserved as ActivityDate on Task and StartDateTime on Event.

If the customer has deal records in Kursaha (custom configuration or from a billing integration), these map to Salesforce Opportunity with Amount, StageName, and CloseDate preserved. Deal custom fields migrate as Opportunity custom fields created during schema design. Pipeline and deal stage mapping follows the same Record Type and Sales Process configuration as the Campaign-to-Opportunity mapping.

Kursaha's real-time analytics and campaign performance metrics (opens, clicks, conversions, conversion rates) are generated by the platform's processing layer and are not available as discrete exportable records. We do not migrate analytics event history. The customer should capture screenshots of dashboards before cutover. Reporting is rebuilt from migrated Opportunity, Contact, and Activity data in Salesforce Reports and Einstein Analytics post-migration.

Kursaha integrations with third-party tools (forms, CRM, analytics) are configuration-level settings that do not carry over during migration. Each integration must be reconfigured independently in Salesforce. We deliver a written inventory of all detected Kursaha integrations with recommended AppExchange equivalents or Salesforce native solutions (e.g., Web-to-Lead for form capture, native CRM sync for other platforms).