Migrate from Rezolve.ai to HubSpot Service Hub

Rezolve.ai Tickets map to HubSpot Service Hub Tickets, which are functionally equivalent to Salesforce Cases under the CRM hood. We migrate ticket ID, subject, description, status (Open/In Progress/Resolved/Closed), priority (Low/Medium/High/Urgent), and assignee. The Rezolve.ai requester maps to the HubSpot Contact or email recipient. AI resolution flags and auto-resolution metadata are Rezolve.ai-specific and do not transfer; we document these for reconstruction using HubSpot workflow triggers or Breeze AI agent features.

Rezolve.ai conversation threads attached to Tickets map to HubSpot Ticket timeline entries. Each message preserves timestamp, author (agent or employee), direction (inbound/outbound), and body text. Attachments migrate as linked files to the ticket record. Thread metadata such as AI-handled flags and message reaction counts are Rezolve.ai-specific and do not have HubSpot equivalents. We normalize conversation timestamps from UTC to the customer's configured HubSpot timezone.

Rezolve.ai Knowledge Articles map to HubSpot Knowledge Base articles with field-level mapping: article title, body content, category, publish status, and author. AI-resolution metadata (confidence thresholds, linked Skills, auto-resolution rules) are Rezolve.ai-specific and require manual rebuild on HubSpot. We export the raw article content and category hierarchy; the customer's admin rebuilds AI triggers using HubSpot's workflow automation or Breeze AI article-assist features. Knowledge base must be migrated before tickets so that auto-resolution knowledge links can be re-established post-migration.

Rezolve.ai User records (employees who submit requests) map to HubSpot Contacts. We migrate email address (primary key), first name, last name, department, and manager. Rezolve.ai role assignments (end user vs agent) are preserved in custom Contact properties and inform the Agent mapping below. Users without an email address are flagged for the customer's admin to assign a contact record before migration.

Rezolve.ai Agent profiles map to HubSpot Contacts with agent-role properties plus HubSpot Inbox assignment records. We migrate agent email, name, profile status (active/inactive), and team membership. Agent workload data and availability status are point-in-time snapshots and do not transfer as live metrics; these reset on the HubSpot platform at cutover. SLA assignment and escalation rule configuration requires reconstruction in HubSpot Service Hub settings.

Rezolve.ai Teams represent routing groups and service desk squads. We migrate team name, description, and member list. Team-level routing rules map to HubSpot Inbox routing assignments and ticket assignment rules. If Rezolve.ai teams have Skills-based routing (routing to a team based on the Skill category), we document this as a routing requirement for the HubSpot admin to configure using HubSpot's workflow-based assignment logic.

Rezolve.ai Knowledge Skills and Task Skills are AI-resolution units tied to the platform's LLM infrastructure. They have no direct export or HubSpot equivalent. We capture the Skill name, category, linked knowledge articles, and business intent during scoping, then map each Skill to a recommended HubSpot workflow trigger sequence. The customer's admin rebuilds the automation logic in HubSpot's visual workflow builder. This is documented in the pre-migration audit and is not a code migration.

Rezolve.ai Workflows define automation sequences for ticket routing, approvals, and escalations using proprietary AI logic. We export workflow definitions (triggers, conditions, actions) as written documentation. Because the automation logic is Rezolve.ai-specific and has no export format, we cannot perform a direct workflow import. We deliver a written inventory of every active workflow with its trigger conditions, escalation paths, and recommended HubSpot workflow equivalents for the customer's admin to rebuild post-migration.

File attachments on tickets, knowledge articles, and conversation threads migrate as binary blobs to HubSpot. We preserve original file names and attach them to the corresponding destination records (Ticket, Knowledge Base Article). Storage location references from Rezolve.ai do not transfer; files are re-hosted in HubSpot's file management. Maximum file size limits on HubSpot (256 MB per file on Enterprise) are enforced during migration; files exceeding this limit are flagged for manual re-upload.

Custom fields on Rezolve.ai Tickets migrate to HubSpot Ticket custom properties with type mapping: text fields to single-line text, picklists to dropdown, multi-select to multi-select checkbox, date fields to date picker, and numeric fields to number. We flag any custom fields that reference Rezolve.ai-specific picklist values or formulas requiring manual reconfiguration. Custom property dependencies on Skill or Workflow objects are documented separately in the automation inventory.

Rezolve.ai built-in reports cover resolution rates, ticket volumes, and CSAT. We export report definitions and configuration where extractable, but Rezolve.ai report formats do not have direct HubSpot equivalents. We recommend rebuilding key reports on HubSpot using Service Hub's native reporting dashboard (available from Professional tier). CSAT survey responses migrate as ticket property data attached to the relevant ticket records.

Tenant-level settings including branding, notification rules, SLA configurations, and escalation policies migrate selectively. We document existing Rezolve.ai settings as a written configuration audit. SLA timers, escalation thresholds, and notification routing rules require manual recreation in HubSpot Service Hub settings. Notification templates and email signatures migrate as content for the customer's admin to re-enter in HubSpot's inbox settings.

Agent engagement activities such as status changes, assignment actions, and resolution events in Rezolve.ai map to conversation log entries on the HubSpot Ticket timeline. We preserve the activity type, timestamp, agent identity, and notes field. Rezolve.ai AI-resolution events (auto-handled flags) do not transfer as native HubSpot fields; we flag these for reconstruction using HubSpot workflow logs if the customer requires the same audit trail.