Migrate from Kursaha to HighLevel

Kursaha Contact records export as CSV including standard fields (name, email, phone, company) plus custom behavioral properties and lifecycle stage. We map email, phone, first_name, last_name, and company_name directly to GoHighLevel Contact fields. Custom properties migrate to GoHighLevel Custom Fields (Settings > Custom Fields > Contact). Lifecycle stage from Kursaha becomes a custom picklist field on GoHighLevel Contact. Deduplication uses email as the primary key; duplicate emails receive a suffix during import and are flagged for customer review.

Kursaha Campaign records (name, status, start/end dates, channel assignments) do not have a direct GoHighLevel equivalent. We map campaign name to Workflow name, campaign status to Workflow enabled/disabled state, and channel assignments to Workflow triggers (email trigger for mail, SMS trigger for SMS). The campaign's audience membership rules require reconstruction in GoHighLevel using Workflow filter conditions and Smart List membership. We deliver a written mapping document that specifies each campaign's trigger, conditions, and actions for the customer's admin to rebuild in GoHighLevel's Workflow builder.

Kursaha Audience segments are defined by filter rules against contact properties. We document each segment's rule logic (property name, operator, value) and reconstruct it in GoHighLevel using Groups (static lists) or Smart List filters (dynamic). Complex nested conditions may require multiple Smart Lists or a re-evaluation of the segmentation logic given GoHighLevel's filter builder syntax. We flag any segment logic that cannot be expressed in GoHighLevel's filter model during scoping.

Kursaha Channels (mail, WhatsApp, SMS) are linked to Campaigns rather than stored as independent objects. We preserve channel-to-contact associations as GoHighLevel Tags (e.g., channel_email, channel_whatsapp) applied to Contact records. Channel subscription preferences migrate to custom contact fields for opt-in tracking. WhatsApp and SMS channel configuration requires separate setup in GoHighLevel's LC SMS and LC Voice modules post-migration.

Kursaha email template text content and basic HTML structure export with the template list. We map template name, subject line, and HTML body to GoHighLevel Email Templates. Advanced AMP markup and interactive elements are flagged as a manual rebuild item because AMP for Email requires GoHighLevel template editor compatibility verification. The customer reviews each migrated template in GoHighLevel's editor before sending.

Kursaha WhatsApp and SMS template text content migrates to GoHighLevel LC SMS Templates. Character limits and variable placeholder syntax differ between platforms, so we document the variable mapping for each template (e.g., Kursaha {{contact.first_name}} becomes GoHighLevel {{contact.first_name}} or a custom merge field). WhatsApp-specific formatting (buttons, lists) does not carry over and is flagged for manual rebuild in GoHighLevel's WhatsApp template builder.

Kursaha user accounts (name, email, role: admin/editor/viewer) map to GoHighLevel Team Members. We extract user records from the dashboard export and create GoHighLevel user accounts with matching role assignments. GoHighLevel permissions are assigned via the Agency > Team Members section. Users without an active email in GoHighLevel's invitation system require manual account creation and invitation during cutover.

Kursaha analytics and campaign performance metrics (opens, clicks, conversions, engagement rates) are computed by the platform's processing layer and are not available as discrete exportable records. We do not migrate analytics event history. Customers should capture screenshots of historical campaign performance in Kursaha before cutover. GoHighLevel's reporting dashboards provide a starting point for new campaign analytics; historical trend data cannot be carried forward and must be rebuilt from the point of migration onward.