Migrate from Knock CRM to Zoho CRM

Knock stores all people as Contacts with a lifecycle_status value (Inquiry, Tour Scheduled, Application, Resident, Former). Zoho separates Leads and Contacts. FlitStack routes Knock contacts with status 'Resident' or 'Former Resident' to Zoho Contacts, and everything else to Zoho Leads. The original Knock lifecycle_status is preserved as a custom pick-list field on both Lead and Contact so the Zoho admin can build reports on resident status post-migration.

Knock's Company object maps directly to Zoho's Account module. Property name, street address, city, state, and zip transfer as Account.Name, Street, City, State, and Zip_Code. Multi-property portfolios where a Knock company has child properties map to Zoho's parent-account hierarchy using Account.Parent_Account. Knock's property type (apartment, townhome, mixed-use) transfers as a value-mapped pick-list in a custom field.

Knock Deal maps to Zoho Deal — both use deal-stage pipelines with owner assignment and close dates. The Knock lease stage names (Inquiry, Tour Scheduled, Application, Lease Signed, Active, Former) map value-by-value to Zoho Deal Stage pick-list values. FlitStack creates the target stage names in Zoho first, then maps each Knock stage to the corresponding Zoho stage during migration so no records land without a valid stage value.

Knock owner records carry a name and email. Zoho CRM requires an active user record to assign ownership. FlitStack resolves Knock owners to Zoho users by email match. Any Knock owner whose email has no corresponding Zoho user is flagged before migration; your team either creates the Zoho user first or assigns those records to a fallback owner. No record migrates without an owner assignment.

Knock task records map to Zoho Tasks — subject, due date, owner, and status transfer directly. Task status (Open, Completed, Overdue) maps to Zoho's Status field. Completed tasks from Knock retain their Completed status. Tasks without a due date land in Zoho with no Due_Date. Notes attached to Knock tasks transfer as Zoho task descriptions.

Knock notes on contacts, companies, and deals migrate to Zoho Notes linked to the corresponding record. The note body, author (mapped by email to Zoho user), and creation timestamp transfer. Rich-text formatting in Knock notes is simplified to plain text in Zoho Notes. Notes attached to multiple Knock records are duplicated as separate Zoho Notes per parent record.

Knock file attachments — lease agreements, ID scans, application documents — re-upload to Zoho CRM as Attachments linked to the corresponding Deal or Contact. File size limits in Zoho CRM apply (ZIP file cap of 25 GB total, 2 GB per file). FlitStack downloads each attachment from Knock, validates file integrity, and uploads to the target Zoho record. Files without a valid target record are held in a staging folder for manual assignment.

Knock tracks which unit a prospect toured or a resident occupies. Zoho has no native unit-number field on Contacts or Deals. FlitStack creates a custom single-line text field (Unit_Number__c) on the Contact module and a corresponding field on the Deal module. Values transfer directly. The Zoho admin should add the field to relevant page layouts post-migration.

Knock captures lease start and end dates on Deal records. Zoho Deal has Close_Date (the close date), but no native lease-term fields. FlitStack creates Lease_Start_Date__c and Lease_End_Date__c as custom date fields on the Deal module. Values map directly from Knock. These fields are critical for lease-renewal reporting in Zoho and should be added to the Deal layout.

Knock's visitor log tracks how a prospect found the property — website inquiry, apartments.com, referral, walk-in. Zoho has no native visitor-attribution field on Leads or Contacts. FlitStack creates a custom pick-list field (Lead_Source_Detail__c) on the Lead module to preserve this context. Values transfer as-is. This field is especially valuable for marketing attribution reporting in Zoho Analytics.

Knock tracks resident lifecycle (Current Resident, Former Resident, Non-Resident) on the Contact record. Zoho's standard Contact object has no resident-status field. FlitStack creates a pick-list custom field (Resident_Status__c) on the Contact module. Knock's status values map directly to Zoho pick-list values. The mapping plan also flags which Former Resident contacts should be archived vs. kept active in Zoho.

Knock Now allows prospective renters to self-schedule tours from a website widget. This is a platform configuration, not data. It cannot be exported or transferred to Zoho CRM. FlitStack documents each Knock Now rule (trigger URL, availability settings, notification email) as a reference spec for rebuilding with Zoho's appointment-scheduling tools or a third-party integration (Calendly, Acuity).