Migrate from knock-ai to Intercom

Knock AI captures anonymous site visitors and identifies them by company and role with real-time enrichment signals. We map these to Intercom Contacts, preserving enrichment data including company size, role, intent signals, and ICP match scores as custom attributes on the Contact record. Visitors that Knock AI identified but did not qualify become Intercom Contacts with a lead_source of 'knock-ai' and qualification_status set to 'not_qualified'. We deduplicate against existing Intercom Contacts using email address as the primary key, flagging any matches for customer review before import.

Knock AI conversation logs including full chat history, timestamps, participant information, and routing destination map to Intercom Conversations. Each conversation is linked to the corresponding Intercom Contact. Note that Knock AI exports buyer-facing logs only; internal rep notes are not included in the export and must be captured separately from Knock AI's interface for manual re-association post-migration.

Leads that pass Knock AI's AI qualification criteria carry a qualification status, score, and routing destination. We map the qualification status to a custom Intercom contact attribute qualification_status and preserve the score as qualification_score. The routing destination (which rep or team was assigned) is stored as a custom attribute original_routing_destination for reimplementation reference in Intercom workflows.

Scheduled meetings from Knock AI include buyer details, meeting type, and booking status. We export these as structured records and map them to Intercom Conversations as event-attached notes or as calendar-linked notes using Intercom's note attachment capability. If the customer uses a separate calendar system, we flag the meeting records for CRM or calendar integration setup post-migration.

Prospect enrichment includes company information, role, intent signals, and CRM sync status pulled in real time by Knock AI. We map enrichment fields to Intercom Contact custom attributes, preserving all enrichment signals as read-only or attributed fields. Where enrichment data overlaps with an existing CRM sync log (HubSpot or Salesforce), we cross-reference to avoid duplicating data that already exists in the customer's CRM.

Knock AI's intelligent routing assigns leads to reps or teams based on configurable conditions. Routing logic is not exposed via API for bulk export. We document the full rule tree during scoping and produce a structured routing specification with conditions, priority logic, and assignment targets that your team or implementation partner can use to rebuild equivalent routing in Intercom's Workflow builder. This is a specification deliverable, not an automated migration.

AI agent guardrails, approved answers, auto-booking trigger conditions, and fallback behaviors are stored as Knock AI platform settings with no documented API endpoint for export. We extract a human-readable summary of all configured topics, fallback behaviors, and routing logic during scoping, but the guardrails themselves must be manually reconfigured in Intercom Fin AI using your help center articles and Fin AI training interface. We do not migrate AI agent configurations as code.

Knock AI maintains a sync log showing what data was pushed to HubSpot or Salesforce. We use this log to reconcile which contacts, companies, and deals were enriched during Knock AI's operation, avoiding duplicate creation in your CRM if you maintain the HubSpot or Salesforce integration post-migration. We flag contacts that already exist in your CRM with a different record ID and provide a deduplication recommendation before migration. We do not write to your CRM during migration without explicit coordination.

Each Knock Link is a configurable entry point with its own routing and branding settings. We export the link configuration including destination routing and display settings as a reference document. Intercom does not have a direct Knock Link equivalent; chat links are typically implemented as Intercom inbox or workspace rules. We document the source configuration for your team to reimplement as Intercom routing rules post-migration.

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 or outreach data; those remain in LinkedIn and are unaffected by the Knock AI to Intercom migration. If LinkedIn sequence continuity is required during migration, coordinate separately with LinkedIn Sales Navigator administrators to pause or transfer sequences outside this migration scope.