Migrate from knock-ai to HubSpot Service Hub

Knock AI visitors with identification data (company name, role, email if captured) map to HubSpot Contact records. Anonymous visitors without email or company are held in a staging table and flagged for manual review if they cannot be enriched. We preserve Knock AI enrichment signals (company size, industry, intent signals) in custom contact properties on HubSpot. If Knock AI enriched a contact that already exists in HubSpot, we match on email domain and update rather than create to avoid duplicates.

Knock AI leads that passed AI qualification criteria carry a qualification status and routing destination. We map the qualification status to HubSpot's lifecyclestage property or a custom qualification_score__c field depending on the customer's preference. The routing destination (rep or team assignment) is preserved as a custom field for reimplementation in HubSpot workflow assignment. Knock AI lead scoring values migrate to a custom property for audit.

Knock AI conversation transcripts map to HubSpot Conversations, which appear in the Shared Team Inbox as message threads. We preserve the full buyer-facing chat log, timestamps, participant information, and conversation status. Internal rep notes attached to Knock AI conversations do not export and must be captured separately; we flag this during scoping and provide a template for manual capture. Knock Link attribution (which chat link initiated the conversation) migrates to a custom conversation property for attribution reporting.

Knock AI company enrichment data (domain, company size, industry, LinkedIn URL) maps directly to HubSpot Company properties. We use domain as the dedupe key during import. Company records must be created before any Contact import so that the Company-Contact association is resolved at insert time.

Scheduled meetings include buyer details, meeting type, and booking status. We export these as HubSpot Meeting records with participant information, meeting type, and status preserved. Meeting links and video conferencing URLs stored in Knock AI are captured in a custom property since HubSpot Meetings auto-generate Zoom or Google Meet links only for meetings created natively.

Knock AI maintains a sync log showing what data was pushed to HubSpot or Salesforce during its active period. We use this log to reconcile which contacts and companies were previously synced, identifying records that should update versus records that are net new. This prevents duplicate contact creation when migrating contacts that Knock AI already pushed to HubSpot during the co-existence period.

Prospect enrichment includes company info, role, intent signals, and CRM status. We map enrichment fields to HubSpot contact and company properties. Intent signal data from Knock AI (page views, engagement scores, topic interest) is preserved in a custom property hs_intent_signals__c on Contact for segmentation and reporting in HubSpot.

Knock AI guardrails, approved answers, topic configurations, fallback behaviors, and auto-booking trigger conditions are stored as platform-specific settings with no exportable API. We extract a human-readable configuration summary covering all configured topics, trigger conditions, and routing logic. The customer must manually rebuild these in HubSpot Breeze Customer Agent or via HubSpot workflow automations based on our documentation. This is a manual reimplementation step outside the automated migration scope.

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—including priority order, condition types, fallback logic, and team assignments—and produce a structured routing specification. The customer rebuilds equivalent routing in HubSpot using workflow enrollment criteria and team assignment actions. Routing rule rebuild is outside the automated migration scope.

Each Knock Link is a configurable entry point to a Knock conversation with its own routing and branding settings. HubSpot Service Hub does not have an equivalent Knock Link concept; conversations enter through the Shared Team Inbox via email, live chat, Facebook Messenger, or portal submission. We document each Knock Link configuration (name, routing destination, branding, qualification criteria) and map it to a HubSpot Inbox create ticket routing rule or a specific inbox team assignment.

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 because they do not exist in Knock AI's data store. We document which contacts were flagged for LinkedIn outreach in a custom hs_linkedin_outreach_flag__c property on Contact so the customer's sales team can take manual action in LinkedIn Sales Navigator or a LinkedIn-connected sales engagement tool post-migration.

If Knock AI created tickets in HubSpot via its native sync, those tickets may already exist in HubSpot. We check for matching tickets using subject and contact lookup during scoping. Pre-existing tickets are updated with any new conversation data rather than recreated. Tickets created directly in Knock AI without CRM sync are imported as HubSpot Tickets with conversation history attached.