Migrate from Knock CRM to Salesforce Sales Cloud

Knock contacts map to Salesforce Contacts. Salesforce requires each Contact to have an AccountId lookup — contacts without a primary company in Knock land against a default placeholder Account or receive a custom field flag for manual Account assignment post-migration.

Knock companies map directly to Salesforce Accounts. Knock's company hierarchy (parent/child property relationships) maps to Account.ParentId. Multi-company associations that Knock supports natively require Salesforce Account hierarchies or a custom junction object. If a Knock organization uses multiple linked companies for joint ventures or affiliate properties, those relationships map to Salesforce Account hierarchy levels or a dedicated Affiliation__c junction object to preserve the network structure.

Knock deals map to Salesforce Opportunities. Since Knock has no native pipeline grouping, the deal pipeline name from Knock becomes a custom Opportunity field (Pipeline__c) in Salesforce. Opportunity StageName values are mapped from Knock dealstage pick-list values. The mapping preserves the original deal stage progression, allowing historical reporting to reflect Knock's sales cycle without manual re‑entry.

Knock call and email engagement logs map to Salesforce Tasks with Type = 'Call' or 'Email'. Original timestamps, owners, and subject lines are preserved. Salesforce Tasks do not store rich email body content — body text migrates as a custom long-text field if it is business-critical.

Knock Tour records carry tour date, prospect name, unit toured, and outcome. The core tour metadata migrates as a Salesforce Task with Type = 'Tour'; unit and outcome details land in custom fields (Tour_Unit__c, Tour_Outcome__c) since Salesforce has no native tour object.

Knock Lease records with start date, end date, monthly rent, and security deposit have no Salesforce standard equivalent. We create a custom Lease__c object with those fields plus a lookup to the Account (property). Your admin configures page layout and sharing settings before migration runs.

Knock Unit records with unit number, property association, unit type, and bed/bath count have no Salesforce standard equivalent. Unit__c is created as a custom object with a lookup to the Account (property) and a relationship to Lease__c. Each Unit__c record also includes a Status__c pick‑list field to track availability (e.g., Available, Leased, Under Maintenance) and a Rent_Range__c text field for reporting.

Knock custom objects map 1:1 to Salesforce custom objects. Knock custom-object relationships that use a many-to-many model in Knock require Salesforce junction objects since Salesforce uses explicit lookup fields rather than association tables. We inventory each Knock custom object's schema, identify N:N associations, and create the corresponding junction objects and lookup fields in Salesforce before loading data.

Knock file attachments on contact, company, or deal records are downloaded and re-uploaded to Salesforce Files. Salesforce enforces a 25MB per-file limit. Inline images embedded in Knock notes are extracted, rehosted, and linked in Salesforce Notes. Files larger than 25MB are flagged in the pre‑migration audit, and we recommend splitting them or using Salesforce CRM Content for bulk storage.

Knock owner IDs resolve to Salesforce Users by email match. Unmatched owners are flagged before migration — the team either creates Salesforce user accounts or assigns records to a fallback owner. No record lands in Salesforce without a resolved OwnerId.

Knock sequences and outreach automations are specific to Knock's event engine and do not have a Salesforce equivalent. We export the sequence definitions as a rebuild reference for your Salesforce admin. Workflows and task triggers must be recreated in Flow.

Knock pre-built leasing reports and dashboards have no Salesforce equivalent and cannot be migrated. The underlying data they reference migrates fully, so reports can be rebuilt on migrated data. We document which Knock reports exist so your Salesforce admin can prioritize rebuilds.