Migrate from Kizen to Salesforce Sales Cloud

Kizen's standard Contact Object maps to Salesforce Lead or Contact depending on the contact's lifecycle stage. We define the split rule during schema discovery by reviewing Kizen's lifecycle stage property values. Unqualified prospects map to Salesforce Lead; qualified buyers map to Salesforce Contact attached to an Account. The original Kizen lifecycle stage is preserved in a custom field kizen_lifecycle_stage__c on both Lead and Contact for audit and reporting continuity.

Kizen Company records map to Salesforce Account. The company domain stored in Kizen's website field becomes the Account's Website and is used as the dedupe key during import. We create the Account record before any Contact import so that the AccountId Lookup is satisfied at the moment of Contact insert.

Kizen Deal records map to Salesforce Opportunity. The deal stage maps to Salesforce StageName, and the Kizen pipeline assignment maps to a Salesforce Record Type and Sales Process that we configure before migration. Closed-Lost and Closed-Won reason fields from Kizen custom properties migrate to Salesforce LossReason and Win Reason standard fields.

Kizen pipelines map to Salesforce Record Types on Opportunity. Each Record Type gets a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from Kizen to Salesforce StageProbability with rounding to the nearest integer.

Kizen custom Objects discovered during schema enumeration migrate to Salesforce custom Objects of equivalent API name. We pre-create the destination schema including all custom fields, relationship fields, and validation rules in a Sandbox before any data import. Kizen's Primary relationship fields map to Salesforce Master-Detail where the destination requires referential integrity; Additional relationships map to Lookup or are denormalized to a text field depending on cardinality.

Kizen Primary relationships create one-to-many links between Objects. We map these to Salesforce Lookup fields where the child record can exist independently, or Master-Detail where cascade delete is required. The destination field type is determined during scoping based on business requirements for orphaning behavior.

Kizen Additional relationships create many-to-many associations. In Salesforce, these require a Junction Object with two Master-Detail or Lookup fields pointing to the related Objects. We build the Junction Object during schema design and migrate the relationship records as Junction Object entries during data load.

Kizen Activities (calls, emails, meetings, tasks) migrate to Salesforce Task and Event objects. We preserve the activity type, timestamp, owner assignment, and linked Object reference. Task records use TaskSubtype to distinguish calls from general tasks. Activity ordering is preserved by setting ActivityDate to the original Kizen timestamp.

File attachments linked to Kizen Objects migrate as Salesforce ContentVersion binary blobs with ContentDocumentLink records attaching them to the parent Salesforce record (Lead, Contact, Account, Opportunity, or Custom Object). We preserve the original filename, MIME type, and creation date.

Kizen tags stored as label values on Object records migrate to Salesforce multi-select picklist fields. If the number of unique tags exceeds Salesforce's picklist limit (1,000 values per field), we fall back to a text field or a custom tagging object with tag-name records and a junction relationship.

Kizen Form and Survey submissions create or update Object records in Kizen. The submitted field data migrates as standard field values on the target Salesforce record. The form definition itself (field names, types, conditional logic) does not migrate; we document the form schema for the customer's admin to replicate in Salesforce Web-to-Lead, Experience Cloud forms, or a form builder app.

Kizen standard automations (field updates, email sends, task creation) are catalogued as a written inventory. Each automation's trigger conditions, action sequences, and object scope are documented with a recommended Salesforce Flow equivalent. We do not migrate automations as code because the execution models differ structurally.

Kizen AI-driven automations involving multi-agent orchestration, RAG-based knowledge retrieval, or LLM-dependent logic are flagged separately from standard workflows. These cannot be replicated in a standard CRM migration. We export the trigger conditions and action sequences as plain-text logic notes and recommend a Salesforce Agentforce scoping conversation as a separate engagement.

Kizen Owner records map to Salesforce User by email match. Any Kizen Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive owners migrate as inactive Salesforce Users with the original owner ID preserved in a custom field for audit.