Migrate from Krayin CRM to Pipedrive

Krayin Lead records map directly to Pipedrive Lead. We map Krayin fields (name, email, phone, source, notes, owner_id) to Pipedrive Lead fields. Krayin's lead status and pipeline stage assignments migrate to Pipedrive Lead status and the assigned pipeline. Custom attribute values on Leads migrate to corresponding Pipedrive custom fields on the Lead object, which shares its field schema with Deals per Pipedrive's architecture.

Krayin Person records map directly to Pipedrive Person (Contact). We use email as the primary deduplication key and flag duplicates for the customer's review. Name, email, phone, address, job title, and organization association (linked Company) migrate. If the Krayin Person is associated with a Company, we resolve the Pipedrive Organization ID before inserting the Person record to satisfy the lookup relationship.

Krayin Company records map to Pipedrive Organization. Company name becomes the Organization name field; domain and address data map to their Pipedrive equivalents. Organizations are migrated before Persons so that the organization_id lookup is available at Person insert time. Krayin Company custom attributes migrate to Pipedrive Organization custom fields.

Krayin Product records (name, SKU, price, description, inventory count) map to Pipedrive Products. SKU maps to the Pipedrive Product code field. We create Standard Pricebook entries during migration so that Products are immediately available for Deal line items. Products are migrated before Deals so that product_id references are valid at Deal insert time.

Krayin Deal records map to Pipedrive Deals. Krayin's deal title and value migrate directly; the Krayin pipeline and stage assignment is mapped to a corresponding Pipedrive Pipeline and Stage that we create during the pipeline configuration phase. Krayin's lost_reason and won_reason custom fields migrate to Pipedrive Lost Reason and Won Reason fields if those exist in the destination account.

Krayin pipeline definitions and stage configurations (stage names, probabilities, order) are recreated in Pipedrive's Pipeline builder. We extract the Krayin pipeline schema during discovery, then configure Pipedrive Pipelines and Stages before any Deal data is migrated. Each Krayin pipeline becomes one Pipedrive Pipeline; Krayin stage probabilities are approximated to the nearest Pipedrive-allowed percentage. Stage-to-stage automation rules in Krayin do not migrate and are documented separately for manual rebuild in Pipedrive's automation builder.

Krayin Activity records (type: task, call, or meeting) migrate to equivalent Pipedrive Activities. Call duration and disposition migrate to Pipedrive Call fields; meeting start and end times and attendee data map to Pipedrive Meeting fields. Activity timestamps are preserved to maintain the chronological history. The activity owner maps to the corresponding Pipedrive user by email match. Activity subject and description migrate as-is.

Krayin User records map to Pipedrive Users by email address match. We extract all Krayin Users referenced on Leads, Persons, Companies, Deals, and Activities during discovery and reconcile against the destination Pipedrive account's user list. Users without a matching Pipedrive account go to a reconciliation queue for the customer's admin to provision before record import proceeds. Role and permission sets require manual reconfiguration in Pipedrive since Krayin's role model does not export.

Krayin tag assignments on Leads, Persons, and Deals migrate to Pipedrive Labels. We export the tag taxonomy from Krayin, map each tag to a Pipedrive Label with the same name, and reattach labels to the migrated records. Labels with no Pipedrive equivalent are flagged for the customer to rename or consolidate before migration.

Krayin custom attribute definitions and values migrate to Pipedrive custom fields. Not all Krayin attribute types are equally accessible via the REST API; we probe the schema during discovery and fall back to a direct database query on the custom_attributes table when the API returns incomplete field data. We then create matching Pipedrive custom fields (with the appropriate field type: text, numeric, dropdown, date, checkbox) before populating values.

Krayin workflow definitions cannot be exported via the API. We treat workflow rebuild as a post-migration workstream, not a data migration deliverable. During discovery, we document every active Krayin workflow (trigger type, conditions, actions) and deliver a written inventory with recommended Pipedrive automation equivalents. The customer's admin rebuilds workflows in Pipedrive's automation builder post-migration.

Krayin stores file attachments on the server filesystem, not as structured objects accessible via the REST API. We cannot retrieve or migrate attachments programmatically. During discovery, we provide a filesystem path listing so the customer can manually export files from Krayin's storage directory. Post-migration, we provide instructions for re-uploading files to the relevant Pipedrive records.