Migrate from Kylas Sales CRM to Zoho CRM

Kylas Lead records map to Zoho CRM Leads. The Kylas lead_score property maps to a custom numeric field in Zoho. Lead source and status picklist values are remapped by value label rather than ID, since picklist ID namespaces differ between platforms. We flag any Kylas leads that have already been converted (status = converted) and migrate them as Zoho Leads with a note indicating prior conversion date.

Kylas Contacts map directly to Zoho Contacts. Standard fields (name, email, phone, address) use 1:1 field mapping. Custom fields on Contact are exported with their field type and values, then created in Zoho before import. Email uniqueness constraints in Zoho are validated against the import batch before insert to avoid duplicate record errors.

Kylas Companies map to Zoho Accounts. Industry classification, company size, and multi-currency settings transfer to the corresponding Zoho Account fields. Linked Contacts and Deals retain their association through the Account-Contact and Account-Deal lookups, resolved at import time using the Account's external ID.

Kylas Deals map to Zoho Deals with pipeline stage mapped to the Zoho Stage field. Deal value, expected close date, owner assignment, and probability migrate directly. The Kylas pipeline name maps to a Zoho Sales Process or Record Type that we configure in the destination before migration begins.

Kylas supports multiple named Pipelines with fully custom stage names. We map each Kylas pipeline to a Zoho Record Type with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate to the Zoho Stage field's probability mapping. If a Kylas pipeline exceeds Zoho's stage count limit for the customer's edition, we consolidate or flag the excess stages.

Kylas Products map to Zoho Products with SKU preserved as the Product Code. Standard price book entries are created during import if the customer has enabled Products in their Zoho edition.

Kylas activity records attach to Leads, Contacts, Deals, and Companies. Tasks and Calls map to Zoho Tasks with owner assignment and timestamps preserved. Meetings map to Zoho Events. Notes migrate as Zoho Notes linked via the parent record reference. Some activity subtypes such as field-sales check-ins may not have a direct Zoho equivalent; we document these and flag them for the customer's admin.

Documents stored in Kylas export as binary blobs. We map them to Zoho's attachment or Notes with file upload, preserving the parent record association. Very large document stores may require chunked export and import. Zoho's native import wizard has documented limitations with attachments from third-party CRMs, which we handle via API-based upload.

Custom fields on any Kylas object are exported with their field type, picklist value IDs, and current values. We create matching custom fields in Zoho before data import, remapping picklist value ID namespaces to Zoho's. Note: Zoho's Data Migration wizard allows a maximum of 50 custom fields to be created during migration, which is inclusive of the overall custom field limit for the customer's edition.

Kylas user records (name, email, role, profile) are exported and matched to Zoho Users by email. We flag inactive Kylas users and hold their records pending user provisioning in Zoho. Owner assignment on Leads, Contacts, Deals, and Activities resolves to the Zoho User record via the email match.

Tags in Kylas apply across objects. We export the full tag vocabulary and map each tagged record to Zoho's Tags feature. If a record in Zoho receives more than 10 tags, only the first 10 migrate per Zoho's import limit. Tag names exceeding 25 characters are truncated.