Migrate from Kylas Sales CRM to HubSpot

Kylas leads map to HubSpot contacts. The lead's status and source information migrate as HubSpot contact properties. Kylas lead scoring values transfer to HubSpot's custom numeric property. The migration assigns the appropriate HubSpot lifecycle stage based on Kylas lead status or your specified routing rule.

Kylas contacts map 1:1 to HubSpot contacts. All standard properties (name, email, phone, address, job title) map directly. Owner assignment resolves by email match against HubSpot users. Multi-phone fields map to HubSpot's phone and mobilephone properties. Original create dates preserve in a custom datetime property.

Kylas company records map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue map to HubSpot's equivalent properties. Kylas parent-child company hierarchies preserve via HubSpot's parent company association. Custom company properties migrate as HubSpot custom properties.

Kylas deals map to HubSpot deals. The deal name, amount, expected close date, and owner assign directly. Kylas pipeline and stage names map to HubSpot deal pipelines and stage values — each Kylas pipeline becomes a HubSpot deal pipeline, and Kylas stage names map value-by-value to HubSpot stage names within that pipeline.

Kylas's multiple named pipelines map to HubSpot deal pipelines. Each Kylas pipeline creates a corresponding HubSpot pipeline. Stage names translate value-by-value — Kylas stage labels map to HubSpot stage names, and stage order and probability percentages map if Kylas stores them. Custom pipeline properties in Kylas become HubSpot deal custom properties.

Kylas call logs migrate to HubSpot calls with original timestamp, duration, direction (inbound/outbound), and outcome preserved. Call notes map to HubSpot call body. The call associates to the matching HubSpot contact or company record by email or company domain lookup.

Kylas email history migrates to HubSpot emails with subject, body, timestamp, and direction preserved. Emails attach to the corresponding HubSpot contact or company record. Kylas email templates do not migrate — they must be recreated in HubSpot's email template library.

Kylas meeting records migrate to HubSpot meetings with meeting title, start/end times, attendees, location, and outcome preserved. The meeting links to the associated HubSpot contact or deal. Kylas meeting templates do not migrate and require recreation in HubSpot's meeting scheduler.

Kylas notes map to HubSpot notes with content, create date, and owner preserved. Notes attach to the correct HubSpot record (contact, company, or deal) based on the original Kylas association. Rich-text formatting in Kylas notes translates to HubSpot's note body format.

Kylas custom contact fields migrate as HubSpot custom properties. Pick-list custom fields require value-by-value mapping since HubSpot manages option labels independently. Numeric and date custom fields map directly. Boolean fields map to HubSpot's checkbox property type.

Kylas custom deal properties migrate to HubSpot deal custom properties. Currency-formatted fields map to HubSpot's number or currency property type. Multi-select pick-list values require manual value-mapping during migration planning. Stage-linked custom fields map based on the deal's final stage value.

Kylas tasks and reminders migrate to HubSpot tasks with subject, due date, status, priority, and owner preserved. Completed vs. open status maps to HubSpot task completion. Kylas task recurrence rules do not carry over — recurring task logic must be rebuilt in HubSpot's workflow automation.

Kylas products associated with deals map to HubSpot products. Product name, SKU, price, and description migrate directly. Kylas line items on deals translate to HubSpot line items associated with the migrated deal record.

Kylas lead scores migrate as a custom numeric property on HubSpot contacts. HubSpot's native lead scoring (available on Professional+ tiers) uses different criteria weights — your team decides whether to adopt HubSpot's native scoring model or continue using the migrated Kylas score values for comparison.