Migrate from Kursaha to Microsoft Dynamics 365 Sales

Scoping call and export capability audit

We schedule a scoping call with the customer's team to review their Kursaha tier, identify all data objects in active use (Contacts, Campaigns, Segments, Templates, Users), and request sample CSV exports from the dashboard. We audit the exports for field completeness and flag any objects where dashboard exports are limited or unavailable. If the customer is on an on-premise deployment, we discuss VPN access or direct database extraction requirements. The output is a written migration scope document listing all objects, estimated record counts, export method per object, and any scope-limiting gaps identified.

Dynamics 365 destination schema preparation

We provision the Dynamics 365 destination environment with the required schema elements before any data extraction begins. This includes creating custom fields on Contact, Account, and Campaign to accommodate Kursaha-specific properties that have no direct Dynamics 365 equivalent. We create a custom Template entity for WhatsApp and SMS template storage. We configure the import user with Dataverse API permissions and validate connectivity via OAuth 2.0 before production migration. All schema work is validated in a sandbox or non-production Dynamics 365 environment first.

CSV extraction, staging, and transformation

The customer exports CSV files from the Kursaha dashboard for each data object in scope. We receive the CSV files and stage them in a secure migration workspace. We perform a field-level audit comparing the exported columns against the Dynamics 365 target fields, flagging any custom properties that lack a destination field and requiring the customer to confirm whether they should be created as custom fields or dropped. We transform the CSV data to match Dynamics 365 field types (date formats, picklist values, required field population) and generate a transformation report for customer review before import begins.

Account pre-creation and Contact import in dependency order

We import data in record-dependency order. First, we extract distinct company values from the exported Contact CSV and create Account records in Dynamics 365, using company_name as the Account Name and company_domain as the Website. Second, we import Contacts with the resolved AccountId lookup, mapping email, phone, and custom properties to typed or custom fields. This two-phase approach ensures every Contact has an Account lookup, which is required for Dynamics 365 pipeline and revenue reporting to function correctly. We reconcile record counts after each phase against the source CSV totals.

Campaign and Campaign Member import

We import Campaigns first (campaign name, dates, channel, status), then link Campaign Members (the exported audience membership list) to the corresponding Campaign. We resolve each Campaign Member's Contact reference to the Dynamics 365 Contact record ID. If the exported audience membership is provided as a separate export file rather than inline with the Campaign export, we merge it against the Contact lookup table. Large Campaign Member imports exceeding 50,000 records use the Bulk API with chunking and backoff to avoid Service Protection limit errors.

Cutover, delta sync, and automation handoff

We freeze writes in the source system during the cutover window, run a final delta export of any records modified since the initial export, apply the delta to Dynamics 365, and validate record counts match the source. We verify the Account-Contact relationship integrity, confirm Campaign Member linkages, and run a spot-check sample of 25-50 records against the source CSV. We deliver the Automation Inventory document (listing all active Kursaha workflows and segment rules with recommended Dynamics 365 equivalents) to the customer's admin team. We do not rebuild workflows inside the migration scope. A hypercare window of three business days is included for reconciliation issues raised by the customer's team post-go-live.