Migrate from Kylas Sales CRM to HighLevel

Kylas Lead records (pre-conversion prospects with source, status, and scoring fields) map to GoHighLevel Contact records. The lead_score, lead_source, and lifecycle status migrate as Contact custom fields. If the customer uses Kylas Lead stages that represent pre-qualification states, we map those to GoHighLevel Contact tags or a custom status picklist field rather than GoHighLevel's separate Lead object, which is used for inbound marketing leads only.

Kylas Contact records (name, email, phone, address, and custom properties) migrate to GoHighLevel Contact records. Email serves as the dedupe key. Custom properties on Kylas Contacts are mapped to GoHighLevel Contact custom fields, with field type mapping (text to text, picklist to dropdown, date to date, number to number). Kylas lifecycle-stage metadata migrates as a custom Contact field for reporting continuity.

Kylas Company records map to GoHighLevel Company records. Industry classification, company size, and address data migrate directly. Companies with associated Contacts retain their association through the GoHighLevel Company-Contact relationship model. Multi-currency settings on Kylas Companies map to a currency custom field on the GoHighLevel Company record since GoHighLevel handles multi-currency at the account or sub-account level.

Kylas Deal records map to GoHighLevel Opportunity records. Deal value, expected close date, owner assignment, and deal stage migrate. The Kylas pipeline stage name maps to a GoHighLevel pipeline stage with the same order and probability percentage. We create the target pipeline in GoHighLevel before Deal migration begins so that stage assignment is valid at insert time.

Kylas multiple named Pipelines with fully custom stage names map to GoHighLevel Pipelines. We create matching GoHighLevel pipelines with the same stage count, stage names, and probability weights before Deals are imported. If a Kylas pipeline exceeds the destination plan's pipeline count limit, we flag this during scoping so the customer can consolidate pipelines or upgrade.

Kylas activity records (calls, tasks, notes, field-sales check-ins) attach to Leads, Contacts, Deals, and Companies. Timestamps and owner assignment are preserved. WhatsApp conversations linked to Kylas Contacts migrate to GoHighLevel Contact conversations if the customer configures their WhatsApp Business API in GoHighLevel during migration. Field-sales check-ins that have no GoHighLevel equivalent become Notes on the Contact record.

Kylas custom fields on Leads, Contacts, Deals, and Companies are exported with their field type, picklist value IDs, and current values. We pre-create matching GoHighLevel Contact custom fields or Opportunity custom fields during migration setup, remap picklist value IDs to GoHighLevel dropdown options, and validate the full custom field schema in a GoHighLevel sandbox before production import. Field types are mapped directly (Kylas text to GoHighLevel text, Kylas picklist to GoHighLevel dropdown, Kylas date to GoHighLevel date).

Kylas tags apply across objects. We export the full tag vocabulary and map each tagged record to GoHighLevel Tags on the Contact or Company record, merging any duplicate tag names. Tags are one of the most reliably portable data elements across CRM migrations.

Kylas user records (name, email, role, profile) are exported and mapped to GoHighLevel Users. We match by email address. Any Kylas user without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision. Inactive Kylas users are flagged and invited to GoHighLevel as inactive or not provisioned depending on the customer's preference.

Kylas Smart Lists are dynamic saved searches with membership evaluated at query time. They have no persistent record set to export. We export the filter criteria for each Smart List and document them so the customer can recreate the same filter logic in GoHighLevel Smart Lists manually. The migrated records themselves are available in GoHighLevel for filtering.