Migrate from Knock CRM to Pipedrive

Knock Contact maps directly to Pipedrive Person. Name, email, phone, job title, and address fields translate field-for-field without transformation. The Knock contact ID is preserved as a custom field (knock_contact_id__c) for traceability, delta-run deduplication, and cross-referencing between systems during the validation phase after migration completes.

Knock's Property object has no direct Pipedrive equivalent. We map Property to Organization, using the property name as Organization name and the property street address as Organization address. Unit-level detail (unit number, floor plan, rent amount) migrates as custom fields on the Organization record.

Knock companies that represent external businesses such as vendors, partner properties, and corporate accounts map directly to Pipedrive Organizations. If no company exists on a contact, the associated Property becomes the Organization as described in the Property-to-Organization mapping. Company records preserve their original industry classification as a custom field when present.

Knock's Lease object (move-in date, move-out date, lease state, monthly rent, security deposit, lease term) has no Pipedrive equivalent. These fields become custom fields on the Person record. If the lease represents a revenue event, a Deal record is also created with the monthly rent as the deal value and the lease state as the deal stage.

Knock's prospect pipeline tracks prospective residents through leasing stages (Inquiry, Tour Scheduled, Application, Approved, Leased). Each Knock stage maps to a Pipedrive deal stage within a configured pipeline. The mapping is value-by-value: stage names and probabilities are preserved as defined in Knock.

Knock activities — logged calls, emails, tour meetings, and notes — map to Pipedrive Activities. The activity type, subject, date, owner, and associated person or property are preserved. Knock's tour scheduling records migrate as Meetings with the scheduled time as the start time.

Knock gamified leasing tasks (follow-up reminders, lease renewal tasks, prospect outreach tasks) map to Pipedrive Activities with type='task'. The task subject, due date, assignee, and completion status are preserved. Knock's automated task-generation rules are not migrated — they are exported as JSON for rebuild in Pipedrive Automations.

Knock contact custom properties (e.g., referral source, prospect rating, leasing-agent assignment, preferred move-in window) require Pipedrive custom fields on the Person object. We create each custom field with the matching data type (text, number, date, picklist) before migration and map values row-by-row.

Knock property custom properties such as unit count, property type, amenities list, market rent, and occupancy rate migrate to custom fields on the Organization record. Property-level numeric fields including occupancy rate and market rent use the Number field type in Pipedrive, while text-based fields like amenities use the text field type with appropriate formatting for display.

Knock files attached to contacts, properties, or leases are downloaded and re-uploaded to Pipedrive's activity attachments where supported. Files without an associated activity are preserved as a Google Drive or Dropbox link stored in a custom URL field on the Person or Organization.

Knock owner IDs are resolved by email match against Pipedrive users. Unmatched owners are flagged before migration — the team either creates the Pipedrive user first or assigns records to a fallback user. Knock's owner-level performance metrics do not migrate; they are exported as a reference CSV.