Train Your Team on the New Platform

Converge Team

• Updated March 12, 2026

Part of the HubSpot Service Hub migration guide

How to train your support team when switching from HubSpot Service Hub, including onboarding timelines and best practices.

Training Your Team After Switching from HubSpot Service Hub

HubSpot Service Hub uses a ticket-centric model built around the Help Desk workspace, ticket pipelines, and ticket stages. The biggest adjustment for your team is moving from structured ticket workflows with pipeline stages to a conversation-based unified inbox where messages from all channels appear in a single stream.

Key Concept Mapping

HubSpot concepts translate like this: Tickets → Conversations, Ticket Pipelines → Status tabs (open/resolved/closed), Ticket Stages → Conversation status, Help Desk Spaces → Inbox filters and views, Snippets → Quick Replies (pre-written responses), Ticket Assignment Rules → Auto-routing (round-robin or load-balanced), Knowledge Base articles → FAQ section in widget, SLA Policies → SLA policies (direct equivalent with per-priority targets). The main conceptual shift: HubSpot separates everything into pipelines with stages, while a unified inbox uses simpler status-based organization.

Day 1: Core Navigation (30 min)

Walk through the unified inbox showing how all messages — from WhatsApp, Messenger, email, Telegram, Discord, and widget — appear in one conversation list. Unlike HubSpot's Help Desk where tickets are organized into pipeline views and team spaces, unified inbox platforms show all conversations sorted by status and recency. Demonstrate how to filter by status (open, resolved, closed), how conversation assignment works, and how to use the customer sidebar to view contact details.

Day 1: Recreating Workflows (30 min)

Convert your HubSpot snippets into Quick Replies — copy the text content and note any personalization tokens that need remapping. If you used HubSpot's ticket routing rules (assign to specific users/teams, contact owner, or AI customer agent), configure equivalent auto-routing rules with round-robin or load-balanced assignment. Document any workflow automations that triggered on ticket status changes — some may need to become auto-reply rules or manual processes.

Day 2: Features That Work Differently

HubSpot's ticket pipelines with multiple stages don't have a direct equivalent — unified inbox platforms use simple status progression (open → resolved → closed) instead of custom pipeline stages. HubSpot's custom objects and associations (linking tickets to companies, deals, or custom records) don't carry over — customer data is organized through profiles and tags instead. HubSpot's Coaching page (agent performance metrics) is replaced by employee analytics dashboards.

Week 1: Supervised Practice

Have agents handle real conversations with a team lead available for questions. The shift from clicking through ticket pipelines to working in a real-time conversation stream typically takes 2-3 days. Teams coming from HubSpot often find the simpler interface faster once the initial adjustment period passes — no pipeline navigation, no stage updates, just reply and resolve.

Most teams report that the transition from HubSpot's ticket-based model to a messaging-focused inbox takes about 1 week. The biggest hurdle is unlearning pipeline-stage thinking — conversations flow more naturally without mandatory stage transitions.