Migrate from Kylas Sales CRM to Pipedrive

Kylas Lead records (with source, status, and lead_score fields) map to Pipedrive People by default. On Pipedrive Advanced and Power plans, a separate Lead object is available; we map Kylas Lead to Pipedrive Lead in that case. Kylas lead_score migrates to a custom numeric field kylas_lead_score__c on the People or Lead record. The decision between People and Lead destination depends on the customer's Pipedrive plan tier and whether they want to maintain a separate pre-contact pipeline.

Kylas Contact records map directly to Pipedrive People. Standard fields (name, email, phone, address) map 1:1. Custom properties on the Contact record migrate to custom fields in Pipedrive. We validate email uniqueness before import to avoid duplicate People records in Pipedrive.

Kylas Company records map to Pipedrive Organization. Industry classification, company size, and multi-currency settings from Kylas migrate to equivalent Pipedrive Organization fields. Organization is created before any linked People import so the relationship is satisfied at the time of People insert.

Kylas Deal records map to Pipedrive Deal with pipeline stage, deal value, expected close date, owner assignment, and custom fields preserved. The Kylas pipeline name maps to a Pipedrive pipeline we create before migration. Stage names and probabilities migrate from Kylas stage definitions to Pipedrive stage configuration.

Kylas named Pipelines with custom stage definitions map to Pipedrive Pipelines. We create Pipedrive pipelines before Deal migration, copying stage names, stage order, and probability percentages from Kylas. Pipedrive supports multiple pipelines at all paid tiers; no upgrade is required for multi-pipeline migrations.

Kylas Activity records (Tasks, Calls, Notes) attach to Leads, Contacts, Deals, and Companies. Timestamps and owner assignment are preserved. Call disposition and duration migrate to custom Activity fields in Pipedrive. Field-sales check-in activities (a Kylas mobile feature) have no direct Pipedrive equivalent; we map them to Notes with a custom field activity_type__c = field_checkin to preserve the record without forcing a schema mismatch.

Kylas Documents stored as binary blobs migrate to Pipedrive as file attachments on the parent record (People, Organization, Deal). We map the parent record association to maintain context. Very large document stores (over 5 GB total) may require separate file transfer tooling; we flag this during the pre-migration audit.

Custom fields on any Kylas object (Lead, Contact, Company, Deal) are exported with their field type, picklist value IDs, and current values. We create matching custom fields in Pipedrive before migration, remapping picklist value IDs to Pipedrive picklist values. Pipedrive custom fields apply per object type; if a custom field exists on multiple Kylas objects, we create it on each equivalent Pipedrive object.

Kylas tags apply across objects and migrate to Pipedrive Labels. We export the full tag vocabulary and map each tagged record to a Pipedrive Label with the same name. Duplicate tag names merge during migration. Pipedrive Labels are attached to People, Organizations, and Deals; we preserve the cross-object tagging behaviour where supported.

Kylas User records (name, email, role, profile) are exported and mapped to Pipedrive Users by email match. We flag inactive Kylas users and hold them in a reconciliation queue; the customer provisions matching Pipedrive users before migration of owner-assigned records resumes. User roles map to Pipedrive permission sets and admin status.

Kylas Smart Lists are dynamic saved searches evaluated at display time; they have no persistent member list to export. We export the filter criteria (field names, operators, values) for each Smart List as a written specification so the customer's Pipedrive admin can recreate the logic as Pipedrive Filters. The records within each Smart List migrate as standard filtered exports, not as Smart List members.