Migrate from Knock CRM to Microsoft Dynamics 365 Sales

Knock property-to-prospect relationships collapse into a single AccountId lookup in Dynamics 365

Knock supports linking a single Prospect to multiple Properties (multiple units, multiple communities). Dynamics 365 Contacts have one primary AccountId lookup plus the Account Contact Relationships table for additional associations. When a Prospect has more than one active Property association, we migrate the primary (most-recently-modified) as Contact.AccountId and create Account Contact Relationship records for the rest. If your team relies on viewing all associated properties on a single contact record, a custom Knock_Property_Assignments__c table with N:1 relationships to Account is the correct Dynamics 365 pattern.

Knock's leasing-specific stage labels require value-by-value mapping to Dynamics 365 Opportunity stages

Knock's deal stages are built for the leasing lifecycle (Tour Scheduled, Application In, Lease Sent, Lease Signed). Dynamics 365 Sales ships with sales-focused stages (Prospecting, Qualification, Proposal, Negotiation, Closed Won). There is no automatic translation — each Knock stage label must map to a Dynamics 365 StageName value, and probability percentages need to be set per stage in the Opportunity Stage option set. If your Dynamics 365 admin has already configured stages for a different sales process, this mapping requires coordination to avoid overwriting existing stage configurations.

Dynamics 365 Sales Professional enforces a 15-custom-table limit that Knock Enterprise setups may exceed

If your Knock CRM environment uses more than 15 custom objects or properties, Dynamics 365 Sales Professional will block creation of additional tables once you hit the ceiling. Migrating to Sales Professional when you have 20+ Knock custom fields means those fields have nowhere to land without upgrading to Sales Enterprise. We surface the custom field count during the sample migration phase and advise on whether Sales Professional or Enterprise is the correct target tier before the full migration runs.

Owner resolution by email fails for Knock users without pre-existing Dynamics 365 accounts

Dynamics 365 requires an OwnerId on every Lead, Contact, and Opportunity. Knock owner IDs resolve to Dynamics 365 SystemUser records by email match. If a Knock user does not have a corresponding Dynamics 365 license and user account, their assigned records cannot take that owner. We flag all unmatched owners before migration and either provision Dynamics users or assign to a fallback owner — but this means activity history in Dynamics may not reflect the Knock user who originally logged it.

Knock workflow automations and leasing sequences do not transfer to Dynamics 365

Knock automations tied to leasing events (e.g., 'Send welcome email when Prospect moves to Lease Sent stage') are built in Knock's proprietary rule engine and have no equivalent in Dynamics 365 Sales. Dynamics 365 uses Power Automate flows or classic workflows for equivalent logic, but these must be rebuilt from scratch. We export Knock workflow definitions in a machine-readable format during the migration planning phase so your Dynamics 365 admin has a rebuild reference — but the logic transfer is a manual, billable configuration effort separate from data migration.