Migrate from Knock CRM to Freshsales

Knock Guest Cards are the primary contact record for prospects. We split them by lifecycle position: active prospects route to Freshsales Lead; prospects who have signed a lease and are in a post-move-in tracking status route to Freshsales Contact under the corresponding Account (Property). The split rule is configurable by your team based on whether you want to manage pre-lease prospects as Leads or Contacts.

Knock Properties map directly to Freshsales Accounts. Property name becomes Account Name, property address maps to the Account's billing address fields, and the property website maps to Account.website. If the property has a parent company or portfolio management structure, we preserve the hierarchy using Freshsales Account Hierarchy where available or a custom parent-account field.

Knock Units do not have a direct Freshsales equivalent — Freshsales has no native unit-tracking object. We create a Freshsales custom object called Property_Unit with fields for unit number, floor plan type, bedrooms, bathrooms, market rent, and lease status. Each Unit links to its parent Property (Account) via a lookup relationship.

Knock Leases carry lease start date, lease end date, monthly rent, security deposit, and unit association. We migrate these to a custom Lease object in Freshsales linked to the Contact (resident) and the Unit (Property_Unit). If your team uses leases to track revenue pipeline, we can alternatively map active leases to Opportunity records with close date = lease start and amount = monthly rent for revenue forecasting.

Knock's leasing pipeline stages (Prospect, Touring, Applied, Leased, Renewed) map value-by-value to Freshsales Opportunity Stage values. We preserve stage-entered timestamps as custom datetime fields on each Opportunity so reporting continuity is maintained. Stage probability and forecast category are re-applied from Freshsales side once the stage mapping is confirmed.

Knock team members who are assigned as owners of Guest Cards, Properties, or Leases are matched to Freshsales users by email address. Unmatched owners are flagged before migration. You can either invite them to Freshsales first or assign their records to a fallback owner — no record lands without a valid Freshsales user as owner.

Knock activities — phone calls, emails, meetings, and notes attached to Guest Cards or Properties — migrate to Freshsales Tasks and Events. Original timestamps, activity owners, and parent-record links are preserved. Knock notes with rich-text formatting migrate to Freshsales Notes where supported, or as Task records with the note body in the description field.

Files attached to Knock Guest Cards, Properties, or Leases are re-uploaded to Freshsales Files, linked to the corresponding record. File size limits apply (Freshsales caps files at 25MB per upload). Inline images in Knock notes are downloaded and re-hosted as Freshsales attachments on the parent record.

Knock's custom property fields (e.g., property type, year built, number of amenities, renewal rate) migrate as Freshsales custom fields on the Account or Property_Unit object. Fields with pick-list values require value-by-value mapping against Freshsales pick-list options. Long-text or multi-select Knock fields map to Freshsales Long Text Area or Multi-Select Picklist respectively.

Knock custom fields on Guest Cards (e.g., lead source detail, referral type, budget range, preferred move-in date) migrate as Freshsales custom fields on Lead and Contact. These are created as identical field names for consistency. If a Knock field uses a data type not supported natively by Freshsales, we map it to the closest equivalent (e.g., Knock date field → Freshsales Date field) and note the transformation.

Knock tour records (scheduled via Knock Now or manually logged) migrate to Freshsales Events with original start/end times, assigned user, and the related Guest Card or Property as the parent record. Tour status (Scheduled, Completed, No-Show) maps to a custom Event Status field in Freshsales.

Knock automations (auto-follow-up rules, stage-transition triggers, task-creation workflows) do not have a Freshsales equivalent. We export your Knock workflow definitions as a structured JSON document and a rebuild checklist so your Freshsales admin can recreate the logic using Freshsales Workflows, assignment rules, or the Freshsales API.

Knock reports and dashboards do not transfer. The underlying data (Guest Cards, Properties, Leases, Activities) does migrate, so your Freshsales admin can rebuild equivalent reports from the migrated data. We deliver a report-mapping worksheet that lists each Knock report and its nearest Freshsales analogue.