Migrate from Kursaha to Odoo CRM

Kursaha Contact records (name, email, phone, company, custom properties, lifecycle stage) map to Odoo Contact (res.partner). Standard fields map directly. Custom properties on Kontaha that have no Odoo standard field equivalent are created as custom fields via Odoo Studio before import. Lifecycle stage from Kontaha migrates as a custom selection field kontact_lifecycle_stage__c on Contact for audit continuity. We resolve the owner-to-User mapping by email match and set responsible_id on Contact during import.

Kursaha Campaigns (name, status, start/end dates, channel assignment) map to Odoo CRM Campaign. Channel assignment (mail, WhatsApp, SMS) is preserved as tag records or a custom channel field on the Odoo campaign. Campaign-level audience membership from Kontaha migrates as Odoo Contact tags with the campaign name as tag value, so sales reps can filter the pipeline by audience origin.

Kursaha audience segments are defined by filter rules against contact properties. We reconstruct segment logic using Odoo's native domain filtering in Saved Filters (ir.filters) with the same field, operator, and value logic. For segments used in campaign targeting, we recreate them as Odoo Contact tags. Rule complexity that exceeds Odoo's domain filter syntax is flagged for manual rebuild or scoped as a custom development item.

Kursaha templates for mail, WhatsApp, and SMS content migrate as Odoo Note records or Odoo Email Templates (mail.template) depending on whether the template is intended for recurring use. We preserve template text content and basic HTML structure. Advanced AMP markup and interactive elements do not carry over and are flagged as a content rebuild item in the migration report.

Kursaha channel assignments (mail, WhatsApp, SMS) are linked to campaigns rather than stored as independent contact records. We preserve channel-to-contact associations as Odoo Contact tags (mail_contact, whatsapp_contact, sms_contact) using a lookup table generated from the Kontaha CSV exports. Tags are created during the campaign import phase and linked during the contact reconciliation phase.

Kursaha user accounts (name, email, role) map to Odoo User records. We match by email and flag any Kontaha user without a matching Odoo User for admin provisioning before contact migration begins. Role assignments (admin, editor, viewer) in Kontaha map to Odoo access rights groups (Sales / Administrator / Custom) that the Odoo admin assigns post-migration.

Kursaha's real-time analytics and campaign engagement metrics (opens, clicks, conversions, cohort analysis) are computed by the platform's processing layer and are not exported as discrete records. We do not migrate analytics event history. Customers should capture screenshots of historical campaign performance dashboards before cutover and rebuild reporting using Odoo's native dashboard builder or a connected BI tool.

Kursaha integrations with third-party tools (forms, CRM connections, analytics) are configuration-level settings that do not carry over during migration. Each integration must be reconfigured independently in Odoo. We document the existing integration list from the Kontaha dashboard during scoping and deliver it as a reconfiguration checklist for the customer's admin team.

Kursaha contacts and campaigns may include custom properties beyond the standard set (name, email, phone, company). We audit custom properties during discovery, create matching Odoo custom fields via Studio or metadata API before import, and map them in the transformation layer. Properties that use non-standard data types in Kontaha are flagged for type-normalization during mapping.

Kursaha campaign activity logs (send events, delivery receipts) are exported as campaign event CSVs. We split these into Odoo Note records attached to the relevant Contact for historical reference, or into Odoo Activity records if the customer requests task-style follow-up reconstruction. Plain-text event content migrates; engagement metrics (open rate, click rate) do not because Kontaha does not export these as discrete records.

Kursaha WhatsApp and SMS channel assignments and message content are preserved as Odoo Contact tags (whatsapp_optin, sms_optin) plus a custom field for the most recent channel interaction date. Full message history is not migratable in the standard scope; we flag it as a separate re-engagement scope if the customer requires it post-migration.

Kursaha behavioral properties on contacts (engagement scores, last active date, click history) are extracted from the contact CSV where available. We map them to Odoo custom fields for numeric/scoring data and to Odoo Tags for categorical behavioral segments. Properties that are computed server-side by Kontaha and not present in the export are flagged as non-migratable in the discovery report.