Migrate from Kylas Sales CRM to monday CRM

Kylas Leads map to Monday CRM Contacts. The lead_score, lead_source, and lead_status fields from Kylas migrate as custom columns on the Monday CRM Contact. Any Kylas Lead with a linked Company record creates a Monday CRM Contact with a linked Organisation via the CRM relationship feature. Unconverted Leads that existed at migration time are imported as Contacts; the customer decides whether to treat them as unqualified prospects or active sales targets in Monday CRM.

Kylas Contacts map directly to Monday CRM Contacts. Standard fields (name, email, phone, address) map to Monday's built-in Contact columns. Custom fields migrate as additional columns on the Contact. Lifecycle-stage metadata from Kylas custom properties is preserved as a multi-select or text column for segmentation reference.

Kylas Companies map to Monday CRM Organisations. The industry, company_size, and multi-currency fields from Kylas migrate as Organisation columns. Linked Contacts and Deals retain their association through Monday CRM's built-in CRM relationship links. We create the Organisation before importing linked Contacts so the relationship reference is satisfied at import time.

Kylas Deals map to Monday CRM Deals with the pipeline stage mapping to the Monday CRM Deal's Pipeline stage field. Deal value, expected close date, owner assignment, and probability migrate to Monday's deal_value, expected_close_date, owner, and probability columns. We flag any Kylas deal-stage names that do not map cleanly to Monday CRM's stage labels.

Each named Kylas Pipeline becomes a Monday CRM Pipeline. Kylas pipeline stages map to Monday CRM Pipeline stages (New Business, Qualification, Proposal, Negotiation, Closed Won, Closed Lost). Stage probabilities migrate from Kylas to Monday's probability field. If a Kylas pipeline exceeds Monday CRM's stage naming conventions, we document the mapping in the configuration inventory.

Kylas custom fields on any object are exported with field type, picklist value IDs, and current values. We create matching columns in Monday CRM during migration setup. Kylas picklist value IDs are remapped to Monday column options; the original Kylas picklist values are preserved as option labels so that segmentation logic carries over without requiring manual relabelling.

Monday CRM does not have first-class Activity objects. Calls, emails, meetings, and tasks from Kylas are represented as Item updates, notes, or integrated third-party sync entries in Monday CRM. We export activity timestamps, type, owner, and content, then import them as update entries on the parent Monday CRM Contact or Deal Item. Field-sales check-in activities and other Kylas-specific activity subtypes may not have a direct Monday CRM equivalent; these are flagged for manual disposition during scoping.

Kylas Smart Lists are dynamic saved-filter views with no persistent member list to export. We extract the filter criteria for each Smart List and document them as a configuration inventory so the customer's admin can recreate the logic as saved filters within Monday CRM Boards. The records within each Smart List are migrated as standard filtered exports.

Kylas workflow automation rules are not exposed through Kylas's export API. We document every active Kylas automation (triggers, conditions, action sequences) as a written inventory so the customer's admin can rebuild them in Monday's automation builder. Monday's automation model uses board-level triggers and actions that differ from Kylas's workflow builder; the inventory includes a recommended Monday automation equivalent for each Kylas rule.

Kylas tags apply across objects and migrate as Monday CRM Labels on Contacts, Organisations, and Deals. Duplicate tag names are merged. If a Monday CRM plan does not include Labels at the customer's tier, tags are mapped to a multi-select column as an alternative. The full tag vocabulary is preserved in the import so that filtering and segmentation logic based on tags remains functional after cutover.

Kylas user records (name, email, role) are extracted and matched to Monday CRM Team Members by email. Any Kylas Owner without a matching Monday.com user account is flagged in a reconciliation queue for the customer's admin to provision before the production migration runs. Inactive Kylas users are noted separately so that historical owner assignments are preserved as read-only labels if inactive users are not invited to Monday.com.