Migrate from Kizen to Nutshell

Standard Kizen Contacts (first_name, last_name, email, phone, address, lifecycle_stage, owner) map to Nutshell Person. We resolve name fields into Person.first_name and Person.last_name, email into Person.email, and phone into Person.phone. Address fields map to Person.address. Owner assignment resolves via email match to the Nutshell User table. Lifecycle stage data from Kizen migrates as a custom field on Person since Nutshell does not have a native lifecycle model.

Kizen Company records map to Nutshell Company. HubSpot-style domain field maps to Company.website, industry maps to Company.industry, and size/revenue fields migrate as Company custom fields. Company-to-Contact relationships (Primary one-to-many) require denormalization: we store the parent Company ID in a custom field on the Person record since Nutshell links Persons to Companies via an entity reference rather than a typed relationship field.

Kizen Deal records map to Nutshell Deal with stage, amount, close_date, and owner preserved. Kizen dealstage maps to Nutshell status (Out for signature, In progress, Won, Lost). Amount migrates as Deal.price. Close date maps to Deal.close_date. The owner resolves by email to a Nutshell User. Custom Deal fields from Kizen map to Nutshell custom fields on Deal.

Each Kizen Custom Object is unique and requires schema discovery before mapping. We inspect the custom Object fields via the Kizen API, identify its semantic role (is it a project tracker? a subscription record? a vehicle?), and map it to the closest Nutshell standard entity with custom fields. Where the custom Object has relationships back to Contact or Company, we denormalize the relationship into a text or ID field on the Nutshell record. We cannot preserve Kizen's custom Object as a standalone entity in Nutshell because Nutshell does not support user-defined Objects.

Kizen pipeline definitions (pipeline name, ordered stages, stage probabilities) map to Nutshell Deal pipelines. Nutshell supports one pipeline per account on Starter; Professional supports multiple pipelines. We create the Nutshell pipeline structure matching the Kizen stages during schema configuration. Stage probabilities migrate as percentage values on each stage definition.

Kizen Activities are interaction records linked to Objects. We map call activities to Nutshell Person.calls with disposition, duration, and timestamp preserved. Email activities map to Person.email_logs with subject, body, and recipient preserved. Meeting activities map to Person.meetings with date, duration, and attendees preserved. Task activities map to Person.tasks with status, due date, and assignment preserved. The original Kizen Object reference denormalizes into a note field on the Nutshell activity since Nutshell activities are scoped to Person rather than cross-object.

File attachments linked to Kizen Objects are exported as binary blobs with parent record reference. We import them into Nutshell's file attachment system linked to the corresponding Person, Company, or Deal record. Nutshell's attachment storage limits apply; we flag any attachments exceeding Nutshell's file size limits for customer decision before import.

Kizen tags applied to Object records migrate as Nutshell tags on the corresponding Person, Company, or Deal. Tags stored as multi-select values in Kizen map to Nutshell's tag array format. Tags without a clear Nutshell equivalent are preserved in a custom field on the target entity.