Migrate from Kursaha to Pipedrive

Kursaha Contact records map to Pipedrive Person. Standard fields (name, email, phone, company) map directly. Behavioral properties and lifecycle stage data from Kursaha migrate to custom fields on Person (we create custom fields with the type-matching Pipedrive field type during schema setup). Email address serves as the dedupe key to prevent duplicate Person records on import. Phone number and address fields migrate to Pipedrive's labeled phone and address fields.

Kursaha Campaign records map to Pipedrive Deal. Campaign name becomes Deal title, campaign status maps to Deal status (open/closed won/closed lost), and campaign start/end dates migrate to Deal custom date fields. Channel assignments (mail, WhatsApp, SMS) from the Campaign record are preserved as a custom multi-select field or note on the Deal. Since Deals require a Person or Organization link in Pipedrive, we link each Deal to the primary Contact from the campaign's audience.

Kursaha audience segments are defined by filter rules against contact properties. Pipedrive does not have an equivalent audience segment object; instead, we reconstruct segment logic as Pipedrive filters on the Person list view. Complex multi-condition segments may require simplification or a mapping document for the customer to rebuild as saved filter views. We document the original segment definition rules in the migration workbook for admin reference.

Kursaha Channels (mail, WhatsApp, SMS) are linked to campaigns rather than stored as independent records. We preserve channel associations as Notes attached to the corresponding Deal (mapped from the Campaign) describing the channel used and its configuration. Channel-specific templates do not migrate as reusable templates; we extract template text content and store it as Note body for reference.

Kursaha templates for each channel (mail, WhatsApp, SMS) include content and styling. We extract template text content and basic HTML structure and store it as a Pipedrive Note attached to a reference Deal or as a standalone Note tagged with the template type. Advanced AMP markup and interactive elements are flagged as requiring rebuild in the destination platform's template tool. Template metadata (name, channel type, last modified) is preserved as Note title and custom fields.

Kursaha user accounts and role assignments (admin, editor, viewer) map to Pipedrive User records. We resolve by email match between the Kursaha owner email on each record and the Pipedrive User email field. Any Kursaha user without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before the migration begins. Role hierarchy from Kursaha maps to Pipedrive's admin and regular user permissions.

If Kursaha exports include company or organization data linked to Contacts, those records map to Pipedrive Organization. Organization name maps to name, domain maps to website, and any company-level custom properties migrate to custom fields on Organization. The Organization is created before Person import so that the OrganizationId lookup is satisfied at the moment of Person insert.

Kursaha's real-time analytics and campaign engagement metrics (opens, clicks, conversions) are computed by the platform's processing layer and are not exported as discrete records. We do not migrate analytics event history. Customers expecting campaign performance history to carry over should capture screenshots of dashboards before cutover. Reporting must be re-established in Pipedrive's native Insights tool or a connected analytics platform 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 Pipedrive using its native integrations or Zapier connections. We provide a written inventory of detected integrations during discovery so the customer's admin knows what requires rebuild.

Kursaha contact-level and campaign-level custom properties migrate to Pipedrive custom fields on the corresponding object (Person or Deal). We create custom fields during schema setup using Pipedrive's field type system (text, number, date, picklist, multi-select) matched to the source data type. Custom properties with complex data structures (arrays, nested objects) are flattened to text fields or serialized as JSON in a text custom field.