Migrate from Krayin CRM to HighLevel

Krayin Company records map directly to GoHighLevel Company objects. The Krayin organization name becomes the Company name field; domain, address, phone, and website migrate to corresponding GoHighLevel fields. We resolve Companies first in the migration load order so that subsequent Person and Deal imports can satisfy the parent-company lookup reference. Krayin's organization_id is preserved in a custom field krayin_org_id__c for reconciliation.

Krayin Person records (Krayin's Contact equivalent) map to GoHighLevel Contacts. Email is the primary deduplication key. First name, last name, phone, address, title, and notes migrate directly. Tags assigned to Krayin Persons map to GoHighLevel Contact tags as string arrays. We set the Contact's associated Company via the GoHighLevel company_id lookup resolved from the Krayin organization_id captured during the Company phase.

Krayin Lead records require a qualification decision during migration. Leads with a status indicating active engagement map to GoHighLevel Contacts with a Lead tag and the original Krayin lead score preserved in a custom field. Leads that were converted to Deals in Krayin are not re-imported as Leads; the Deal-to-Opportunity mapping handles them. We document the split logic during scoping based on the customer's Krayin lead lifecycle definition.

Krayin Deal records map to GoHighLevel Opportunities. Deal name, value, expected close date, stage, and owner migrate directly. Krayin pipeline stage names map to GoHighLevel Pipeline stage values, which we configure in GoHighLevel before migration. The Deal's linked Person (as primary contact) and Company resolve to GoHighLevel Contact and Company IDs during the transform phase. Lost-won reason custom fields map to GoHighLevel custom Opportunity fields.

Krayin pipeline definitions migrate to GoHighLevel Pipeline configurations. Each Krayin pipeline becomes a separate GoHighLevel Pipeline with custom stage names and probabilities. We replicate the Krayin stage order and probability percentages as GoHighLevel stage values. If the customer has multiple Krayin pipelines, we create multiple GoHighLevel Pipelines and map Deals accordingly. Pipeline configuration is deployed before Deal migration begins.

Krayin Products map to GoHighLevel Products. SKU, name, price, description, and inventory quantity migrate directly. We create GoHighLevel Products before any Deal import so that line items on Deals can reference the correct product_id. Custom product attributes from Krayin map to GoHighLevel product custom fields if defined in the destination schema.

Krayin Quotes link a Person, Company, and Products with line item pricing. We map quote header data (quote number, date, total, status) into a set of GoHighLevel Opportunity custom fields, and quote line items into a JSON custom field or a Custom Object if the customer's GoHighLevel plan supports it. Custom quote templates and approval workflows do not migrate; these require manual reconstruction in GoHighLevel's document builder.

Krayin Activity records (tasks, calls, and meetings) map to GoHighLevel Tasks. Activity type determines the Task category field in GoHighLevel: calls use a call disposition custom field, meetings use the meeting location and notes fields, and standard tasks use the description and due date. We preserve the original Krayin activity timestamp as the Task created date and resolve the owner and linked Person/Deal at migration time.

Krayin User records map to GoHighLevel Users. We resolve by email match against the GoHighLevel destination account. Any Krayin User without a matching GoHighLevel User is flagged in a reconciliation queue for the customer's admin to provision before Person and Deal migration proceeds. Role and permission sets require manual reconfiguration in GoHighLevel since the permission models differ architecturally.

Krayin tags assigned to Persons, Companies, and Deals migrate as GoHighLevel Contact, Company, and Opportunity tags respectively. We export tag assignments as string arrays during the transform phase and assign them to the corresponding GoHighLevel records by record ID. Tags with no equivalent name in the target system are preserved as new tags created during migration.

Krayin's custom attribute system allows user-defined fields on standard objects. Some custom attribute types (dropdowns, multi-select, date fields) may not be fully exposed via Krayin's REST API, so we fall back to a direct database read from the Krayin custom_attributes table when the API returns incomplete values. We create matching GoHighLevel custom fields in the destination Contact or Opportunity schema before migration and populate them during the transform phase.