Migrate from ClearFeed to HubSpot Service Hub

ClearFeed Tickets (CF-XXXXX format) map to HubSpot Tickets as the primary record. The original ClearFeed ticket ID is preserved in a custom ticket property (clearfeed_ticket_id__c) so that the FlitStack AI manifest references the original source record. Ticket title, status (Open, Pending, Resolved, Closed), priority (Low, Medium, High, Urgent), and creation timestamp migrate directly. HubSpot assigns its own numeric ticket ID at insert time.

Standard custom fields on ClearFeed tickets map to HubSpot Ticket Properties of equivalent type (text, number, date, checkbox, dropdown). We flag AI Fields (fields auto-populated by ClearFeed's language model extraction) in the migration manifest with the note that HubSpot Breeze AI can be configured to reproduce similar extraction behavior on Professional+ plans, but the extraction logic must be rebuilt manually. All custom property values migrate as static data regardless of how they were originally populated.

Each ClearFeed ticket's full Slack thread migrates as HubSpot Ticket Conversations. We preserve the chronological message sequence, message author, timestamp, and the distinction between internal notes and external replies. ClearFeed marks internal notes with a lock emoji; these map to HubSpot's internal ticket notes. The original Slack thread URL is stored as a custom property (clearfeed_thread_url__c) on the ticket for reference.

ClearFeed Collections (e.g. by product line, region, or team) do not have a direct HubSpot equivalent. We map Collection membership to HubSpot Ticket Tags as a multi-value property, preserving the collection name as the tag value. If the customer uses Collections to drive SLA tiering, we recommend mapping Collections to HubSpot Pipelines or Ticket Record Types during scoping so that SLA policies apply correctly per collection in HubSpot.

ClearFeed Agents map to HubSpot Users by email address match. Display name, email, and active/inactive status migrate. Role and permission hierarchies differ between platforms: ClearFeed's agent roles (Admin, Agent, Viewer) do not map directly to HubSpot's permission structure, and the customer's HubSpot admin must assign HubSpot roles and team memberships post-migration. We provide a role-mapping reference document during scoping.

Ticket tags migrate as HubSpot Ticket Tags. Tags used for categorization, routing, or SLA classification in ClearFeed preserve their original values as a tag array on each ticket. The customer chooses whether to migrate all tags or a filtered subset during scoping.

SLA rules from ClearFeed Internal Helpdesk or External Helpdesk migrate as HubSpot SLA Policies on Professional+ tier. We map ClearFeed's first response time and resolution time SLA targets to HubSpot SLA Policy metrics, but the SLA enforcement triggers (time-based alerts, escalations) require recreation as HubSpot Workflows post-migration. Note: SLA data is NOT available from the Integrations Edition and must be sourced from the connected external ticketing platform before migration begins.

ClearFeed Request Channels (the Slack channels capturing incoming requests) are preserved as metadata on each ticket. We map the source channel name to a HubSpot Ticket Property (clearfeed_channel__c) as a text field. HubSpot's native channel tracking (Email, Chat, Facebook, Instagram) does not directly map from ClearFeed channels, so the FlitStack AI manifest notes the original channel for the customer's admin to set source attribution.

ClearFeed Forms capture structured request data and auto-fill ticket fields. Form definitions migrate as HubSpot Forms with field-level mapping documented. Form responses that generated tickets during the migration window are included in the ticket migration. We do not reproduce the form-to-field auto-fill logic; the customer's admin configures HubSpot Forms post-migration.

ClearFeed AI Agents automate FAQ responses and connect to external tools like Okta, Jira, and HubSpot. AI Agent configurations are platform-specific and cannot migrate as functional code. We deliver a written inventory of every ClearFeed AI Agent, its trigger conditions, connected tools, and FAQ coverage, with a recommendation for HubSpot Breeze AI Agent configuration as the replacement. The customer's admin must rebuild the AI agent behavior in HubSpot.

ClearFeed automation rules including SLA alerts, escalations, out-of-office responses, and dynamic routing do not migrate to HubSpot Workflows. We deliver a written automation inventory documenting every ClearFeed rule with its trigger, conditions, and actions, plus a recommended HubSpot Workflow equivalent for each. The customer's admin rebuilds automations post-migration. This is standard scope for all FlitStack AI migrations.

Bi-directional sync links from ClearFeed to Zendesk, Jira, JSM, ClickUp, Linear, GitHub, Intercom, Salesforce, and HubSpot are platform-native and do not replicate in the destination. We export integration configuration metadata (connected platform, sync direction, object mappings) as a written reference document. The customer's admin configures new HubSpot integrations post-migration. Note that if ClearFeed was connected to Salesforce via the Integrations Edition, the customer may already have HubSpot CRM; we flag this scenario during scoping to avoid duplicate integrations.