Migrate from knock-ai to Salesforce Service Cloud

Knock AI visitors with company and role identification map to Salesforce Lead or Contact based on qualification status. Anonymously identified visitors with no qualification signal become Salesforce Lead with the enrichment company size and role stored in custom fields (knock_company_size__c, knock_job_title__c). Identified visitors with qualification data become Contact attached to an Account, with the knock_enrichment_status__c field preserving the Knock AI enrichment confidence score.

Knock AI conversation logs map to Salesforce Case as the primary record, with the chat transcript body stored in Case.Description or as an EmailMessage record with IsIncoming=true for threading. Timestamps, buyer email, and rep assignment resolve to Case.CreatedDate, Case.ContactId, and Case.OwnerId respectively. Internal rep notes not exposed by Knock AI are flagged as a gap and documented for manual re-creation in Salesforce Chatter on the Case.

Knock AI Qualified Leads carry a qualification status and routing destination. The qualification status maps to a custom field knock_qualification_status__c on the Salesforce Lead, preserving the Knock AI scoring threshold and the routing assignment (team or rep name). The knock_qualification_score__c custom field holds the numeric score for reporting and segmentation in Salesforce.

Scheduled meetings from Knock AI export as Salesforce Event records with StartDateTime, EndDateTime, Subject (buyer name + meeting type), and Location preserved. EventRelation records link the buyer (WhoId: Contact or Lead) and the rep (WhoId: User). Meeting status from Knock AI (confirmed, cancelled, rescheduled) maps to Salesforce Event Status custom field.

Knock AI routing rules are not exposed via API for export. We document the full rule tree during the scoping call, capturing condition logic (company size, intent score, team capacity), fallback behavior, and priority order. The output is a structured routing specification that your Salesforce admin uses to rebuild equivalent Omni-Channel Routing Configurations, Skills-Based Routing, or Flow-driven assignment in Service Cloud.

Knock AI guardrails, approved answers, and auto-booking trigger conditions are stored as platform-specific settings with no export API. We extract a human-readable summary of all configured topics, fallback behaviors, and auto-booking conditions. The full reimplementation happens in Einstein Service Agent or Salesforce Flow post-migration based on that documentation; we do not migrate the guardrails as executable code.

Each Knock Link is a configurable entry point with its own routing and branding settings. We export the link URL, destination routing, and display configuration and map these to a custom Knock_Link_Source__c picklist field on Case so that case intake origin is preserved for reporting. The routing destination maps to Case.Origin or a custom Case.Entry_Channel__c field.

Knock AI maintains a sync log showing which contacts, companies, and deals were enriched and pushed to HubSpot or Salesforce. We use this log to identify the dedupe key (email or company domain) for each Contact or Account already in the destination org. We apply Salesforce Duplicate Rules and matching rules during import to prevent duplicate creation when migrating enriched records.

Prospect enrichment from Knock AI includes company info, role, intent signals, and CRM status. We map these to Salesforce custom fields on Contact (knock_intent_signals__c, knock_enrichment_confidence__c) or Account (knock_company_domain__c, knock_employee_range__c). We flag any enrichment fields that exceed Salesforce picklist length limits for truncation or multi-select reformatting.

LinkedIn outreach sequences triggered by Knock AI are stored in LinkedIn Sales Navigator, not in Knock AI itself. We do not migrate active LinkedIn sequences. We document which buyers had LinkedIn outreach triggered so your team can cross-reference those sequences in LinkedIn Sales Navigator post-migration. Any future LinkedIn outreach strategy rebuilds in Sales Navigator or a dedicated sales engagement tool.