Migrate your Knock CRM data

Prospect records are the core object in Knock. Every renter inquiry, walk-in, or referral lands here. Standard fields include contact info, source attribution, lifecycle stage, and assigned leasing consultant. We migrate Prospects 1:1 and preserve the attribution source as a custom property at the destination.

Guest Cards extend Prospects with leasing-specific context — rental history, move-in date range, unit preferences, and co-applicant details. The schema is flat but rich. We map Guest Card fields to standard Contact properties in the destination, flagging any fields that cannot be represented as simple key-value pairs.

Each Property represents a physical apartment community. Standard fields include address, unit count, year built, and portfolio association. We migrate Properties as top-level records and preserve the portfolio hierarchy at the destination if the target supports hierarchical structures.

Units are children of Properties and track floor plan, bedroom/bath count, rent amount, availability date, and current status. We map Units to a property-child object in the destination CRM, preserving the parent Property relationship.

Tours record scheduled and completed prospect visits, linking a Prospect to a specific Unit and a time slot. Knock Now self-scheduling creates Tour records automatically. We migrate Tour history including completion status, scheduled time, and assigned agent.

Tasks are leasing-action items assigned to consultants — follow-up calls, document reminders, lease renewals. Knock gamifies task completion to drive NOI. We migrate Tasks as a standard task/activity object in the destination, but custom gamification metadata is preserved as a custom field only.

Knock centralizes email, text, voice, and chat into a single-screen inbox per Prospect. Communication history is tied to the Prospect record. We migrate message threads and metadata (direction, timestamp, channel), but chat-native interactions may require field-splitting at the destination.

Lease records capture executed rental agreements, linking a Prospect to a Unit with lease start/end dates and rent amount. We migrate Lease records as deal-like objects with standard date fields and amount fields, preserving the prospect-to-unit linkage.

Knock uses pipeline stages to track prospect lifecycle from Inquiry through Move-In. Stage names and counts vary by property configuration. We map stages to destination pipeline stages and flag any custom stages that need manual recreation.

Knock tracks which marketing channel generated each prospect — digital ads, organic, referral, etc. Attribution data is stored as a Prospect property. We carry attribution values forward as custom Contact properties in the destination CRM.

Properties can have custom fields at the Prospect and Unit level. We migrate custom field definitions alongside their values, noting which destination CRM field types will accept the data and which require a workaround.

User records represent the leasing team members who own prospects and tasks. We migrate User records and map them to Owner/User objects in the destination, preserving the assignment relationships on Prospects and Tasks.