Migrate from Krayin CRM to Nutshell

Krayin Company records map directly to Nutshell Organization. The company name maps to Organization.name, and the company phone, website, and billing address map to their corresponding Nutshell Organization fields. We import Organizations first in the load order because Persons and Deals both carry Organization lookups that must resolve before the Person or Deal insert succeeds. Deduplication is performed on Organization name plus website domain.

Krayin Person records map to Nutshell Person with a direct field-to-field mapping: name fields, email address, phone, and job title. The Krayin organization_id foreign key resolves to the Nutshell Organization record we created in the first load phase, satisfying the Person-to-Organization relationship at insert time. We deduplicate on email address as the primary key and flag duplicates for customer review before they are written to Nutshell.

Krayin Lead records map to Nutshell Person with the Lead flag enabled. The lead source, lead status, and lead score properties from Krayin map to Nutshell Person custom fields (source, status, score) that we configure before migration. The Krayin lead_name and lead_email fields map to Person.name and Person.email. We treat Leads and Persons as a unified Person stream in Nutshell rather than maintaining them separately, since Nutshell's data model collapses this distinction by default.

Krayin Products map to Nutshell line items inside Quotes rather than a standalone product catalog object, because Nutshell does not expose a separate product catalog. We migrate Krayin Product.name as line_item.name, Product.price as unit_price, and Product.sku as a custom field. The customer configures the Quote template in Nutshell post-migration. If the customer requires a reusable product library, we create a custom product lookup object in Nutshell as part of the schema design phase.

Krayin Quotes map to Nutshell Quotes, preserving the quote number, total amount, status, and expiration date. Quote line items migrate with their associated Products resolved to the line item structure Nutshell expects. Custom quote templates, approval workflows, and e-signature status do not migrate; these are configuration tasks for the customer's admin post-migration.

Krayin Deal records map to Nutshell Opportunity. The Krayin pipeline and stage assignment maps to Nutshell's pipeline stage; we configure Nutshell pipeline stages during the schema design phase to match the Krayin stage names and probabilities. The deal amount maps to Opportunity.expected_value, and the primary contact person resolves to a Person lookup. Krayin's deal_type (new business, renewal, upsell) migrates as a custom Opportunity type field.

Krayin Activities map to Nutshell Activities, with the activity type determining whether it lands as a Task or an Event. Call activities become Nutshell Task records with call disposition and duration preserved in custom fields. Meeting activities become Nutshell Event records with attendee lists migrated to EventPeople records. Task activities migrate as Task records with status, priority, and due date preserved. Activity timestamps and owner assignments transfer directly.

Krayin tag assignments migrate as Nutshell Tags. Tags with no exact equivalent in Nutshell's tag taxonomy are held for customer review during scoping; we provide a mapping worksheet listing every Krayin tag and the recommended Nutshell equivalent or New Tag creation. Tag migration is a string array transfer, not a relationship migration, and does not require parent-record lookup resolution.