HubSpot Help Desk vs Inbox: Migrate Right (2026 Canada)

01. The Quick Answer

• What Help Desk is: a dedicated support workspace where every incoming message automatically becomes a ticket, with SLAs, custom reporting, and AI tooling on top.
• What you need: Service Hub Professional or Enterprise. Help Desk is not on Starter or the free tools.
• The catch: migrating a channel is one-way, cannot be stopped once started, and only Support can reverse it.
• The dated change:on September 23, 2026, HubSpot's Conversations API stops accepting comments on Help Desk threads as comments move to notes.

02. Help Desk vs the Conversations Inbox, Compared

Why it matters: the inbox and Help Desk are not two skins of the same tool. They organize the same email, chat, form, and calling channels around different objects. If your team thinks in terms of open conversations, the inbox fits. If it thinks in terms of issues that get tracked, prioritized, and reported on, Help Desk fits, and that shift is the whole point of moving.

03. What Actually Changes When You Migrate

When you move a channel, HubSpot keeps your existing channel settings, signatures, routing, and automation rather than resetting them to defaults. From that point on, new conversations in the channel land in Help Desk and each one gets a ticket created and associated automatically. Help Desk access and any SLAs you have configured apply to those new tickets.

You can also choose to bring historical conversations across. If a conversation already had a ticket, both move as-is. If it did not, HubSpot creates a ticket, backdates it to the conversation start date, maps its status to open or closed, and assigns it to the previous conversation owner, but only if that owner has Help Desk access. Owners without access leave their tickets unassigned.

Why it matters: the migration is not just a visual move. It mints tickets, applies SLAs, and can enroll those tickets into workflows. Walk in expecting a new object model, not a reorganized inbox.

04. What Most People Get Wrong

The mistake we see most often is treating the migration as reversible and cosmetic. It is neither. These are the traps worth knowing before you click migrate.

• The move is one-way. Once a channel is migrated, you cannot send it back to the inbox yourself. Reverting means opening a Support ticket, and the migration cannot be halted after it starts. Pick a quiet, low-volume channel to migrate first and confirm the result before touching your busiest one.
• Every message becomes a ticket. Channels connected to Help Desk auto-create a ticket for each incoming message. That reshapes your reporting and can enroll those tickets in any ticket-based workflow they match. Audit your workflows first so a migration does not quietly fire sequences or notifications you did not plan for.
• Ownership can land as unassigned. When historical conversations move over, the ticket owner is set to the current conversation owner only if that person has Help Desk access. If they do not, the ticket is left unassigned. Give every agent Help Desk access before migrating, or you will spend the first day re-routing orphaned tickets.
• You migrate one channel at a time. There is no bulk move. Each email, form, calling, or chatflow channel is migrated on its own, and WhatsApp and Facebook Messenger cannot be migrated at all; they have to be deleted from the inbox and reconnected directly to Help Desk. Plan the sequence rather than expecting a single switch.

Why it matters:none of these are hidden, but they are spread across HubSpot's documentation and easy to miss when you are focused on the new views. The teams that migrate smoothly are the ones that read the caveats first and rehearse on a safe channel.

05. The Dated Change: Comments Become Notes on Sept 23, 2026

HubSpot is replacing thread comments in Help Desk with notes, the same notes your team already uses on CRM records. Announced on March 19, 2026, the change goes live on September 23, 2026. From that date, the Conversations API returns a validation error if an integration tries to create a comment on a Help Desk thread, and integrations are expected to write to the CRM Notes API instead.

Why it matters: most Canadian SMBs will not touch the Conversations API directly, but plenty run third-party or in-house integrations that do. If yours logs internal notes as comments, it will start failing on that date unless it is updated to use notes.

06. A Pre-Migration Readiness Checklist

A clean migration is mostly about what you do before you click, not after. Run this list first.

• Confirm you are on Service Hub Professional or Enterprise. Help Desk is not on Starter or the free tools. If you are on Starter, the migration is really a tier upgrade decision first.
• Give every agent Help Desk access and set SLAs before you move. HubSpot recommends this explicitly. It prevents unassigned tickets and makes sure the SLA rules that apply to new Help Desk tickets are actually in place on day one.
• Audit ticket-based workflows. Because every migrated channel starts minting tickets, review re-enrollment and enrollment criteria so existing automation does not misfire on the flood of new tickets.
• Migrate a low-volume channel first, during a quiet window. The move is one-way and cannot be stopped mid-flight, so validate routing, ownership, and reporting on a safe channel before migrating your main support line.

Why it matters: the one-way nature of the move means a mistake is expensive to unwind. Ten minutes of preparation on access, SLAs, and workflows saves a day of cleanup on the other side. If your team is already stretched thin, this is exactly the kind of change worth scoping with a partner, which we cover in our guide on outgrowing in-house HubSpot management.

07. How AtlanticWorks Helps

As a HubSpot Solutions Partner, AtlanticWorks scopes whether a team should stay on the inbox or move to Help Desk, then runs the migration channel by channel: setting up SLAs, granting agent access, auditing ticket workflows, and mapping pipeline statuses so nothing lands unassigned. We also review any integrations that touch the Conversations API ahead of the September 2026 comments change. If you are standing up support on Service Hub alongside a store, our work on HubSpot Service Hub for Shopify customer success covers how the pieces fit together.

08. Key Takeaways

• Help Desk is Service Hub Professional and Enterprise only. If you are on Starter or the free tools, the migration is a tier decision before it is a workflow decision.
• Moving a channel to Help Desk is one-way. You cannot revert it yourself, and it cannot be stopped once started, so test on a low-volume channel first.
• Every message on a Help Desk channel auto-creates a ticket. That improves reporting but can trigger ticket-based workflows, so audit automation before you migrate.
• Ownership only carries over for agents who already have Help Desk access. Grant access to everyone first, or migrated tickets land unassigned.
• WhatsApp and Facebook Messenger cannot be migrated through the flow; delete and reconnect them. Fallback email addresses cannot move at all.
• A dated change is coming: on September 23, 2026 the Conversations API stops accepting comments on Help Desk threads as HubSpot moves comments to notes. Flag any integration that writes comments before then.
• The Canada-specific search volume for this topic is small, but the underlying question, when and how to move from the inbox to Help Desk, is a recurring one for Service Hub teams, which makes it a strong answer-engine target.