Migrate from Krayin CRM to Freshsales

Krayin's Persons object serves as both early-stage and qualified contacts. We split on Deal association: Persons linked to a Deal (via the Persons_to_organization relationship table) become Freshsales Contacts with a resolved AccountId. Persons with no Deal association become Freshsales Leads. Email is the primary deduplication key on both paths. We preserve Krayin's person stage and lifecycle properties in Freshsales custom fields (krayin_lifecycle_stage__c, krayin_person_type__c) for audit. This split must be designed during scoping because Freshsales converts Leads to Contacts attached to Accounts at a later point in the sales process.

Krayin Companies map directly to Freshsales Accounts. The company name, domain, address fields, phone, and website map to Freshsales Account fields. Account is inserted first in the load order so that AccountId can be resolved at Person-to-Contact insert time. Parent-child company hierarchies in Krayin map to Freshsales Parent Account lookup.

Krayin's Lead object (distinct from Persons in Krayin's data model) maps to Freshsales Lead. We import via Krayin's REST API using the /leads endpoint, mapping lead source, status, and custom attribute fields. Freshsales Lead custom field mapping during conversion is configured in Admin Settings so that lead field data transfers to the corresponding Contact, Account, and Deal fields on conversion. Krayin lead scores map to Freshsales custom lead score fields if the customer has configured scoring in Krayin.

Krayin Deals map to Freshsales Deals. The Krayin dealstage property maps to Freshsales Deal Stage, and the Krayin pipeline assignment maps to a Freshsales Deal pipeline that we configure before migration. Closed-Won and Closed-Lost reasons from Krayin custom fields migrate to Freshsales custom deal fields. The owning Person and Company are resolved to Freshsales ContactId and AccountId at migration time using the lookup table joins.

Krayin's multi-pipeline support maps to Freshsales Deal pipelines. We create Freshsales Deal pipelines during schema setup, with stage names and probabilities translated from Krayin's pipeline configuration. Each Freshsales Deal pipeline is assigned a deal type (newbusiness, renewal, upsell) to distinguish lines of business.

Krayin Products map to Freshsales Products. SKU, name, price, and inventory attributes migrate directly. Krayin's Data Transfer package supports product CSV export, which we transform into Freshsales Product records via the API. Products are imported before Deals so that Deal line items can reference valid ProductIds.

Krayin Activities of type Task migrate to Freshsales Task records. Subject, description, due date, status, and priority map directly. Owner resolution uses the Krayin user-to-Freshsales User email lookup. Task activity timestamps are preserved as ActivityDate to maintain the timeline order in Freshsales.

Krayin call activities migrate to Freshsales Task with TaskSubtype=Call. Call duration, disposition notes, and phone number from Krayin custom activity fields map to Freshsales Task custom fields. We preserve the original call timestamp as ActivityDate.

Krayin meeting activities migrate to Freshsales Task records with a custom meeting flag field. Meeting title, description, scheduled date and time, location, and attendees (person names) transfer. Attendee linking to Freshsales Contact or Lead records is handled via a custom text field holding the person's name, with the customer's admin reconciling attendee resolution post-migration.

Krayin Users map to Freshsales User records as Deal and Contact owners. We match on email address as the primary key. Any Krayin User without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission sets require manual reconfiguration in Freshsales because Krayin role data is not fully exposed via API.

Krayin tags on Persons, Companies, and Deals are extracted as string arrays and mapped to Freshsales custom multi-select picklist fields. During scoping, the customer chooses whether tags become a single unified field per object or split into multiple picklists by tag category. Tags with no equivalent in Freshsales are flagged and optionally dropped.