Migrate from Krayin CRM to Zoho CRM

Krayin Leads map directly to Zoho Leads. We map Krayin's lead name, email, phone, source, and stage fields to the corresponding Zoho Lead fields, preserving the original creation timestamp in a custom field krayin_created_date__c that prevents Zoho from overwriting with the import date. Lead status mapping follows the customer's stage-to-status matrix defined during discovery.

Krayin Persons (individual contacts) map directly to Zoho Contacts. The primary email address is used as the dedupe key during import. We preserve Krayin's Person custom attribute values in matching Zoho Contact custom fields, falling back to direct database read for attribute types (multi-select, date fields) that the Krayin REST API returns incompletely.

Krayin Companies map directly to Zoho Accounts. We create the Account first in the load order so that AccountID is available for resolving Person-to-Contact associations where Krayin Persons are linked to a Company. Company name becomes Account Name; the domain or website field maps to Account Site or Website.

Krayin Deals map to Zoho Potentials. The Krayin dealstage property maps to Zoho Potential Stage, and Krayin pipeline assignment maps to a Zoho Pipeline that we configure before migration. Deal amount, expected close date, and probability migrate to the corresponding Zoho Potential fields. Closed-Lost and Closed-Won dates are preserved in custom fields if the destination Zoho layout includes them.

Each Krayin pipeline becomes a Zoho Pipeline with corresponding Stages. We configure Pipeline definitions in Zoho CRM via the Pipelines API before Deal import begins, mapping Krayin stage names to Zoho stage values and preserving probability percentages. Stage-to-stage automation rules (workflow triggers) do not migrate; we document them for manual rebuild in Zoho Blueprint.

Krayin Products map to Zoho Products with SKU, name, unit price, and tax fields preserved. Product catalog is loaded first in the migration order so that line-item associations on Quotes and Deals resolve correctly during import.

Krayin Quotes map to Zoho Quotes linked to the corresponding Potential. We map line items to Quote Items by resolving the Product reference and populating Quantity, Unit Price, and Total. Custom quote templates and approval workflows do not migrate; we document the active quote approval rules for Zoho admin rebuild.

Krayin Activities (tasks, calls, meetings) split into Zoho Tasks, Events, and Calls based on the activity type field. Each activity's original timestamp migrates to ZohoACTIVITYTIMEFIELD to preserve the activity date in the CRM timeline. Krayin activity owner resolves via email match against Zoho Users. Activity associations (linked to Deal or Person) migrate as WhatId or WhoId lookups in Zoho.

Krayin Users map to Zoho Users by email match. We resolve Krayin's user_id on each record to a Zoho Owner ID via the User lookup. Users without a matching Zoho account go to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission sets require manual reconfiguration in Zoho because Krayin role definitions do not export.

Krayin tags on Leads, Persons, and Deals migrate to Zoho Tags. Tags with no direct equivalent in Zoho are preserved as string arrays and mapped to the customer's chosen taxonomy during scoping. We provide a tag audit listing so the admin can consolidate or rename tags in Zoho before migration.

Krayin's custom attribute system lets admins add fields to standard objects. We probe the Krayin attribute schema during discovery and create matching custom fields in Zoho CRM before migration. For attribute types (dropdowns, multi-select, date fields) that the Krayin REST API returns incompletely, we fall back to a direct database query against the Krayin custom_attributes table. Multi-select picklist values are mapped to Zoho picklist values during the field creation phase.

Krayin stores file attachments on the server filesystem, not as structured objects accessible via the REST API. We cannot retrieve attachments programmatically during migration. We provide a file listing (storage paths and associated record IDs) so the customer can manually export and re-upload files to Zoho post-migration. For inbound migrations to Krayin, we cannot push files via the API; the listing is delivered as a re-upload guide.