CRM migration
Field-level mapping, validation, and rollback between Kordeva and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Kordeva
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
7 of 8
objects map 1:1 between Kordeva and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Kordeva to Microsoft Microsoft Dynamics 365 Sales is a platform migration for small-to-mid-sized teams that have outgrown Kordeva's limited market traction and sparse API surface. Kordeva uses a unified Contact object and a Company-Deal-Activity schema that maps directly to Dynamics 365's Contact-Account-Opportunity-Activity structure, but the sparse API documentation means we require an explicit connectivity test against Kordeva's Custom Fields and base CRM endpoints before committing to API-based extraction. We fallback to CSV export from the Kordeva UI when API access cannot be confirmed, which may not capture custom field definitions or full activity history. We preserve custom field definitions as Dynamics 365 custom fields, resolve Accounts before Contacts for lookup satisfaction, and map Deals to Opportunities with pipeline stage configuration done before migration. Intelligent Workflow automations (Premium tier) and In-Depth Reporting do not migrate; we deliver a written automation inventory for the customer's admin to rebuild in Microsoft Dynamics 365 Sales .
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Kordeva platform overview
Scorecard, SWOT, gotchas, and pricing for Kordeva.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Kordeva object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Kordeva
Contact
Microsoft Dynamics 365 Sales
Contact
1:1Kordeva Contact records map directly to Dynamics 365 Contact. Standard fields (fullname, emailaddress1, telephone1, address) migrate as typed Dataverse fields. We enumerate all custom contact attributes via the Kordeva Custom Fields API and recreate them as Dynamics 365 custom fields (fieldname_schema_name__c) before import. Parent account lookup resolves after Account migration completes.
Kordeva
Company
Microsoft Dynamics 365 Sales
Account
1:1Kordeva Company records map to Dynamics 365 Account. The company name becomes accountname; industry and website migrate as accountindustrycode and websiteurl. We create Account records before Contact import so that the parentcustomerid_account lookup is satisfied at Contact insert time. Kordeva company-contact associations preserve as Contact.parentcustomerid references.
Kordeva
Deal
Microsoft Dynamics 365 Sales
Opportunity
1:1Kordeva Deals map to Dynamics 365 Opportunity. The deal amount maps to estimatedvalue, close date maps to estimatedclosedate, and pipeline stage maps to a Microsoft Dynamics 365 Sales Process configured before migration. We require customer confirmation of stage name mapping since Kordeva pipeline layouts are customer-configurable and not exported via API.
Kordeva
Activity (Call, Email, Meeting, Task)
Microsoft Dynamics 365 Sales
Task, EmailMessage, Event
1:1Kordeva Activity records (calls, emails, meetings, tasks) linked to Contacts and Deals map to Dynamics 365 Task and Event objects. Calls map to Task with tasksubtype = Call; emails map to EmailMessage linked to an Activity Task; meetings map to Event with starttime and endtime preserved. Activity-to-contact and Activity-to-opportunity links resolve via the WhoId and WhatId lookups after Contact and Opportunity migration completes.
Kordeva
Custom Field Definition
Microsoft Dynamics 365 Sales
Custom Field
lossyKordeva's Custom Fields API exposes extended resource attributes as key-value pairs. We enumerate all custom field definitions during discovery, capture the field type (text, number, date, picklist), and recreate each as a Dynamics 365 custom field on the appropriate entity (Contact, Account, Opportunity). Picklist-type custom fields require a global option set in Dynamics 365 with matching integer values; we configure this before data import to avoid validation failures.
Kordeva
Owner
Microsoft Dynamics 365 Sales
User
1:1Kordeva Owner references on Contact, Company, Deal, and Activity records resolve by email match against the destination Dynamics 365 User table. Owners without a matching active User go to a reconciliation queue; the customer's Dynamics 365 admin provisions missing Users before record import resumes. OwnerId on Opportunity is required for production insert.
Kordeva
Accounts and Invoicing
Microsoft Dynamics 365 Sales
Account (financial fields)
1:1Kordeva's bundled Accounts and Invoicing (included in Regular tier) may contain customer financial records beyond standard Account fields. We map invoice totals and outstanding balance to custom currency fields on the Dynamics 365 Account. Full invoice line items and payment history require custom field mapping and may represent a separate migration scope depending on volume and the customer's use of Dynamics 365 Finance module.
Kordeva
Ticket
Microsoft Dynamics 365 Sales
Case
1:1If the Kordeva CRM environment includes ticket or support records, these map to Dynamics 365 Case when the destination org includes Service Cloud or a Customer Service license. Ticket status maps to casestatuscode; ticket priority maps to prioritycode. Ticket conversations migrate as EmailMessage records linked to the Case.
| Kordeva | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Activity (Call, Email, Meeting, Task) | Task, EmailMessage, Event1:1 | Fully supported | |
| Custom Field Definition | Custom Fieldlossy | Fully supported | |
| Owner | User1:1 | Fully supported | |
| Accounts and Invoicing | Account (financial fields)1:1 | Mapping required | |
| Ticket | Case1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Kordeva gotchas
Sparse public API documentation limits migration tooling confidence
Premium-tier feature boundary affects what data exists to migrate
Single verified review on G2 creates information asymmetry
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
API connectivity test and extraction method selection
We request Kordeva API credentials (Custom Fields API and base CRM endpoints) and run a connectivity test during scoping. We verify response schema, field availability, and pagination behavior. If the API responds with valid data for Contacts, Companies, Deals, and Activities, we proceed with API-based extraction. If API access is unavailable or returns incomplete data, we fall back to CSV export from the Kordeva UI, which may require manual steps for custom field capture and activity history. The extraction method decision gates timeline and price and is documented in the signed scope.
Custom field enumeration and Dynamics 365 schema design
We enumerate every custom field definition exposed by the Kordeva Custom Fields API, capture field types and picklist values, and map each to a corresponding Dynamics 365 custom field on the appropriate entity (Contact, Account, Opportunity). For picklist-type fields, we create a global option set in Dynamics 365 with matching integer values. We configure the Microsoft Dynamics 365 Sales Process and stage values before any record import. Schema design deploys to a Sandbox org first for validation by the customer's Dynamics 365 admin.
Account and Owner provisioning before record migration
We extract every distinct Kordeva Owner and Company for pre-provisioning. Owner emails match against the Dynamics 365 User table; missing Users go to a reconciliation queue. Kordeva Company records create as Dynamics 365 Account before any Contact import so that the parentcustomerid_account lookup is satisfied. Any Kordeva custom account fields map to the corresponding Dynamics 365 custom account fields during this phase.
Contact and Opportunity migration with parent-record resolution
We migrate Kordeva Contacts with the parentcustomerid_account reference resolved to the Account created in the prior step. Kordeva Deals migrate as Dynamics 365 Opportunities with the estimatedvalue, estimatedclosedate, and stage name mapped to the configured Sales Process. Opportunity.ownerid resolves to the User mapped from the original Kordeva Owner. We validate record counts after each batch before proceeding.
Activity history migration via Bulk API or CSV import
Kordeva Activity records (calls, emails, meetings, tasks) migrate as Dynamics 365 Task and Event objects with WhoId (Contact or Lead) and WhatId (Opportunity or Account) lookups resolved after the parent record migration completes. If API access is confirmed, we use the Dynamics 365 Bulk API with batch chunking and exponential backoff for large activity volumes. If CSV export is the extraction method, we use the Data Import Wizard or manual CSV mapping with field-level validation. Activity timeline ordering is preserved by setting actualdurationminutes and activitydate to the original Kordeva timestamps.
Cutover, validation, and automation rebuild handoff
We freeze Kordeva writes during cutover, run a final delta migration of any records modified during the migration window, then enable Dynamics 365 as the system of record. We deliver a reconciliation report comparing record counts and spot-checking field values against the Kordeva source. We deliver the Intelligent Workflow and In-Depth Reporting inventory document for the customer's admin to rebuild in Power Automate and Power BI. We support a one-week hypercare window for reconciliation issues. We do not rebuild workflows or reports as part of standard migration scope.
Platform deep dives
Kordeva
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Kordeva and Microsoft Dynamics 365 Sales .
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Kordeva: Not publicly documented.
Data volume sensitivity
Kordeva doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Kordeva to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Kordeva to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Kordeva
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
