Migrate from Kordeva to Salesforce Sales Cloud

Kordeva Contacts with no associated pipeline deal or with a lifecycle stage of Prospect map to Salesforce Lead. Kordeva Contacts attached to Deals or with a lifecycle stage of Customer map to Salesforce Contact attached to a parent Account. We enumerate Kordeva's contact lifecycle properties during API discovery, design the split rule against the customer's actual Kordeva data, and preserve the original lifecycle stage in a custom field kordeva_lifecycle_stage__c on both Lead and Contact for post-migration audit.

Kordeva Company records map directly to Salesforce Account. Company name becomes Account Name; domain or website maps to the Website field. Account is created before any Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. If a Kordeva Contact is associated with multiple Companies, we create a primary Account (first listed) and link secondary associations as AccountContactRelation records in Salesforce.

Kordeva Deals map to Salesforce Opportunity. The Kordeva deal stage name maps to a Salesforce StageName value in a Sales Process we configure before migration. Deal amount, close date, owner, and associated contacts transfer directly. Pipeline stage probability percentages from Kordeva migrate to Salesforce StageProbability values rounded to the nearest integer.

Kordeva deal pipelines map to Salesforce Opportunity Record Types. Each Record Type gets a corresponding Sales Process that scopes the available StageName values. We configure Record Types, Stage definitions, and Page Layouts in a Salesforce Sandbox before production migration so the customer can validate the pipeline layout against the Kordeva source.

Kordeva's Custom Fields API exposes extended resource attributes on Contacts, Companies, Deals, and Activities. We enumerate all custom field definitions (name, type, options for picklists) during API discovery and pre-create matching custom fields in Salesforce before any data import. Custom field data transfers alongside standard fields in a single import pass.

Kordeva call logs against Contacts and Deals migrate to Salesforce Task with TaskSubtype = Call. Call disposition, duration, and any recording URL transfer to custom Task fields. The WhatId points to the parent Opportunity or Account; the WhoId points to the related Lead or Contact. Activity ordering is preserved by setting ActivityDate to the original Kordeva timestamp.

Kordeva email logs migrate to Salesforce EmailMessage records (the email content and headers) linked to an Activity Task (the timeline entry). The EmailMessage body, subject, from address, and to address transfer. Email direction (inbound/outbound) is preserved in a custom EmailMessage field. The related Task's WhoId and WhatId link the email to the correct Contact or Opportunity.

Kordeva meeting records migrate to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Attendee mapping creates EventRelation records pointing to the related Leads, Contacts, and Users. If Kordeva captures meeting notes, they transfer as a custom Event field or as an attached Note record.

Kordeva standalone tasks (not attached to a call or email engagement) migrate to Salesforce Task with Status, Priority, Subject, ActivityDate, and OwnerId preserved. Owner resolution uses the User email match established during owner reconciliation. Tasks with a due date in the past retain their original due date for timeline accuracy.

Kordeva notes attached to Contacts, Companies, or Deals migrate to Salesforce Note records linked via ContentDocumentLink to the parent record. Note body transfers as rich text. If Kordeva stores note attachments, they migrate as ContentDocument records with a ContentDocumentLink to the parent. Note timestamps are preserved for audit ordering.

Kordeva users (owners assigned to Contacts, Companies, Deals, and Activities) map to Salesforce User records by email address. We resolve each Kordeva owner to a Salesforce User during scoping and flag any owner without a matching User in a reconciliation queue. The customer's Salesforce admin provisions missing Users before production migration so that OwnerId references are satisfied at insert time.

Kordeva's Accounts and Invoicing module (included at the Regular tier) stores invoice records, line items, and payment status. We treat invoice data as a custom migration scope: line items map to a custom Invoice_Line_Item__c object with a lookup to the parent Account, and payment status fields map to custom fields on the Account or a custom Invoice__c object. The customer confirms whether invoice history is required in Salesforce or archived separately during scoping.