Migrate from Knock CRM to HighLevel

Knock's Lead object maps directly to HighLevel Contact. Guest-card fields including source, move-in date, budget, and unit preference migrate as custom fields on the HighLevel Contact record. Original Knock lead ID is preserved as a custom field for traceability and delta-run de-duplication. Any custom properties attached to the Lead in Knock that don't have direct HighLevel equivalents are migrated as additional custom fields, ensuring no data is lost during the transition.

Knock Properties representing apartment communities or buildings map to HighLevel Companies. Property-level fields including address, unit count, amenities, and market rent migrate as custom fields on the HighLevel Company record. Parent-property hierarchies are mapped to HighLevel Company relationships where applicable, preserving the organizational structure of the portfolio.

Each Knock Deal represents a lease application or renewal tied to a specific unit and prospect. Deals map to HighLevel Opportunities with the pipeline configured as an Opportunity pipeline. Deal stage (Applied, Approved, Leased, Renewed) maps to Opportunity stage within the target pipeline.

Knock deal stage values including Applied, Under Review, Approved, Leased, Lost, and Renewed map value-by-value to corresponding HighLevel Opportunity pipeline stages. Stage-entry timestamps from Knock are preserved as custom datetime fields on the Opportunity record for reporting continuity and historical tracking purposes.

Knock tasks tied to tours, prospect follow-ups, and lease renewal reminders map to HighLevel Tasks. Task type (Tour, Call, Email, Custom) preserved in a custom task-type field. Original due dates, assignees (resolved by email match), and completion status carry over.

Knock notes attached to guest cards or deal records migrate as HighLevel Notes with their rich-text formatting fully preserved during the transfer. Notes are linked to the parent Contact or Opportunity record using HighLevel's note association model, maintaining the contextual relationship between notes and the records they reference.

Files attached to Knock guest cards or deal records, including lease applications, ID scans, and addendum documents, are downloaded and re-uploaded to HighLevel Files, then linked to the corresponding Contact or Opportunity record. Original file names and MIME types are preserved to maintain document integrity and ensure compatibility with downstream processes.

Knock tags applied to leads and deals, such as 'high-intent', 'referral', or 'renewal-candidate', migrate as HighLevel Tags. These tags are applied to the corresponding Contact or Opportunity record during migration and become available for HighLevel Workflow triggers post-migration, enabling automated sequences based on lead or deal classification.

Knock's guest-card custom properties (e.g., 'Desired Move-In', 'Lease Term Preference', 'Budget Range', 'Source Channel') that do not map to a standard HighLevel field are created as custom fields on the Contact or Company object. Field type is matched as closely as possible: date fields to date pickers, text fields to text inputs, pick-lists to choice fields.

Knock owner records (leasing agents, property managers) are resolved against HighLevel users by email address. Unmatched owners are flagged before migration; records can be assigned to a fallback user or held pending HighLevel user provisioning. Owner history on deals is preserved as a custom field.

Knock Now tour scheduling data (appointment slots, calendar links, confirmed times) has no direct HighLevel equivalent. Scheduling configuration must be rebuilt in HighLevel's Calendar tool. Historical appointment records that exist as completed tasks migrate as Task records with appointment metadata preserved in custom fields.