Migrate from Krayin CRM to Salesforce Sales Cloud

Krayin Users map to Salesforce Users by email address as the dedupe key. We export all Krayin Users via the REST API and match them against the destination Salesforce org's User table before any record migration begins, because OwnerId references on Leads, Persons, Deals, and Activities require a valid Salesforce User ID. Any Krayin User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record migration resumes.

Krayin Company records map directly to Salesforce Account. The Company name becomes Account Name, and any domain or website field maps to Account's Website field. Account is created first in the migration load order so that the AccountId lookup is satisfied when we import Persons and Deals. Krayin Company custom attributes (stored in the custom_attributes table when the API does not expose them fully) map to custom fields on Account__c.

Krayin Person records (Krayin's Contact equivalent) map to Salesforce Contact. Email is the primary deduplication key; we check for existing Contacts with the same email address and flag duplicates for the customer's admin to resolve before insert. The Krayin organization_id (link to Company) maps to Salesforce AccountId via a pre-computed lookup table built from the Account migration results. Krayin Person phone, address, title, and custom attribute fields map to typed Salesforce Contact fields.

Krayin Lead records map to Salesforce Lead. Unlike HubSpot (which uses a unified Contact with Lifecycle Stage), Krayin separates Leads from Persons at the object level, which maps more directly to Salesforce's Lead model. We preserve the Krayin lead status value as a custom field krayin_lead_status__c and map it to a Salesforce Lead Status value that the customer's admin configures before migration. OwnerId resolves via the User email mapping.

Krayin Products map to Salesforce Product2 records. The Krayin SKU becomes Product2 ProductCode. Standard Price Book entries are created during migration so that Products are available for OpportunityLineItem creation. We also migrate product inventory levels when Krayin's inventory tracking fields are present in the source data.

Krayin Deal records map to Salesforce Opportunity. The Krayin pipeline and stage map to a Salesforce Record Type and Sales Process that we configure in the destination org before migration. AccountId, ContactId (via Contact roles), and OwnerId are all resolved at migration time using the pre-built lookup tables from the Account and User migration phases. Krayin's loss_reason and notes fields migrate to custom Opportunity fields.

Krayin's multiple pipeline support maps to Salesforce Record Types on Opportunity. Each Krayin pipeline becomes a Salesforce Record Type with its own Page Layout and Sales Process. Stage names and probabilities migrate to StageName and StageProbability values within each Sales Process. The customer chooses whether to consolidate Krayin pipelines into fewer Salesforce Record Types or preserve them one-to-one.

Krayin Quotes map to Salesforce Quote (a standard object from Sales Cloud Professional). Quote PDFs are not migratable because they are generated dynamically by Krayin's templating system. We migrate line item data (Products, quantities, prices, discounts) as QuoteLineItem records linked to the Quote. The Quote is attached to the corresponding Opportunity via the OpportunityId lookup.

Krayin Activity records (tasks, calls, meetings) attached to Leads and Deals map to Salesforce Task and Event objects. Call activities become Task with TaskSubtype = Call; meetings become Event with StartDateTime and EndDateTime preserved; tasks migrate as Task with Status, Priority, and ActivityDate. The WhoId links to the resolved Lead or Contact; the WhatId links to the resolved Opportunity or Account. Activity timestamps are preserved as ActivityDate for timeline ordering.

Krayin tag assignments stored as string arrays on Persons, Companies, and Deals migrate to Salesforce either as Topics with TopicAssignment records (for cross-object tagging) or as multi-select picklist values on the respective object (for object-scoped tags). The customer chooses the tagging strategy during scoping. Tags with no equivalent in Salesforce are flagged in the migration report for the admin to review.

Krayin's custom attribute system allows user-defined fields on standard objects. We export custom attribute definitions and values via direct database query to the custom_attributes table when the REST API returns incomplete field data (a known Krayin limitation for some field types). Custom attributes become Salesforce custom fields on the corresponding object (Contact, Account, Lead, Opportunity). Field type mapping follows: Krayin dropdown and multi-select map to Salesforce picklist and multi-select picklist; date fields map to Date; text fields map to Text or Long Text Area.

Krayin stores file attachments on the server filesystem, not as structured objects accessible via the REST API. We cannot retrieve or migrate attachments programmatically. During discovery, we flag this gap and instruct the customer to export files manually from the Krayin storage directory before cutover. Post-migration, the customer re-uploads files to Salesforce Files. We provide a manifest of all attachment file paths and the associated Krayin record ID so the customer can re-associate files manually.