Migrate from Krayin CRM to Microsoft Dynamics 365 Sales

Krayin User records map to Microsoft Dynamics 365 Sales User entities via the Dataverse User table. We export Users from Krayin's REST API with email, name, and role metadata, then match by email against the destination Microsoft 365 tenant User list. OwnerId references on all migrated records are resolved against this User map. If the Krayin instance has Users not yet provisioned in the customer's Microsoft 365 tenant, they enter a reconciliation queue for admin provisioning before record migration proceeds.

Krayin Companies map to Microsoft Dynamics 365 Sales Accounts. We load Accounts first in every migration run so that AccountId lookups are satisfied when we import Persons and Deals. Krayin's company name, domain, phone, address fields, and industry attributes map to the corresponding Dataverse Account fields. The company domain serves as a dedupe key if Accounts already exist in the destination org.

Krayin Persons (Krayin's Contact equivalent) map to Microsoft Dynamics 365 Sales Contacts. Each Person record is linked to a parent Company via the organization_id field, which we resolve to the migrated Account's accountid before Contact import. Email address is the primary dedupe key. Phone, job title, address, and custom attribute values transfer to the Contact record. Any Persons without a matching Company are imported with AccountId set to null and flagged for post-migration cleanup.

Krayin Leads map directly to Microsoft Dynamics 365 Sales Leads. Lead source, status, score, and custom fields migrate to the corresponding Dataverse Lead attributes. We preserve the Krayin lead_id as a custom field krayin_lead_id__c for audit traceability. OwnerId maps from the User mapping. Leads without a Krayin-assigned owner are assigned to a default migration User.

Krayin Deals map to Microsoft Dynamics 365 Sales Opportunities. We resolve the AccountId from the Deal's linked Company, the OwnerId from the Deal's assigned User, and the stage value from Krayin's pipeline stage mapping. Deal amount, close date, probability (if defined in Krayin), and custom fields transfer to Opportunity fields. We create a custom field krayin_deal_id__c on Opportunity for cross-reference.

Krayin Products map to Microsoft Dynamics 365 Sales Products (Product table in Dataverse). SKU, name, price, cost, and inventory quantity transfer. Products are loaded before any Deals that reference them so that Opportunity Product Line Items can be created with valid product references. If Krayin uses multiple price lists, we create corresponding Price Lists in Microsoft Dynamics 365 Sales during the product migration phase.

Krayin Quotes map to Microsoft Dynamics 365 Sales Quotes linked to the parent Opportunity and Contact. Line items transfer as Quote Details with resolved Product references and pricing. Krayin's quote status values map to the Microsoft Dynamics 365 Sales Quote Status options. Custom quote templates, approval workflows, and e-signature status do not migrate; we document these for manual reconfiguration.

Krayin Activities (calls, emails, meetings, tasks) map to Microsoft Dynamics 365 Sales Activity entities. Calls migrate as Task records with TaskSubtype=Call and duration preserved. Emails migrate as EmailMessage records linked to Tasks. Meetings migrate as Event records with start and end times preserved. Tasks migrate as Task records with status, priority, and due date. All Activity records are linked to their parent record (Lead, Contact, Account, or Opportunity) via the Dataverse RegardingObjectId lookup. Activity timestamps are preserved as the original Krayin values.

Krayin tag assignments stored as string arrays on Leads, Persons, and Deals migrate to Microsoft Dynamics 365 Sales multi-select picklist fields. We pre-create the picklist field on each target entity, populate the allowed values from the distinct tag set extracted from Krayin, and load tag strings as pipe-delimited values during record migration. Tags with no equivalent are flagged in the migration report for manual cleanup.

Krayin's custom attribute system allows user-defined fields on standard objects. Some custom attribute types (dropdowns, multi-select, date fields) are not fully accessible via the Krayin REST API and require a direct MySQL database query to the custom_attributes table during extraction. We probe the attribute schema during discovery, fall back to database read when the API returns incomplete data, map the custom field type to the nearest Dataverse attribute type, pre-create the fields in the destination Microsoft Dynamics 365 Sales environment, and load values during the standard object migration phase.