EU, US and India data residency · a DPA you can sign

Trust Center →

After Halp: keep Slack ticketing, move it to FlowTux

Halp is gone as a product. If your team migrated with Atlassian’s tool, your tickets are now Jira Service Management requests. This page covers getting them out of JSM and keeping the file-from-Slack habit Halp taught your company.

Atlassian stopped selling Halp to new customers on May 9, 2023. Existing customers kept access until June 4, 2024; since then its features are only available in Jira Service Management Cloud, as Jira Service Management chat.

Getting your data out of Halp

Each line below was checked against Halp’s own documentation on 2026-11-16. Vendors change these pages; follow the source link before you rely on a number.

Status
No new Halp sales from May 9, 2023. Existing customers had access until June 4, 2024; after that, Halp’s functionality is only in Jira Service Management Cloud. Source: community.atlassian.com
Replacement
Halp was renamed Atlassian Assist, and its conversational ticketing became Jira Service Management chat, available on every JSM Cloud plan. Source: community.atlassian.com
Migration tool
Atlassian’s Halp migration tool: connect the cloud site to Halp, create a service project for each queue, invite agents, connect the queue, then migrate tickets into JSM. Source: support.atlassian.com

Not verified

We could not confirm these from Halp’s documentation. Check them in your own account.

  • Which ticket data Atlassian’s migration tool carried (open vs closed tickets, comments, attachments).
  • Whether Halp data that was never migrated is still retrievable.
  • Any CSV export of Halp tickets.

Field mapping

What each Halp field becomes in FlowTux. We confirm every row with you before loading.

HalpFlowTuxNotes
Halp queueRouting input for the same Slack channelsMigrated queues became JSM service projects.
Ticket filed by emoji or messageSlack ticket via the FlowTux shortcut or /flowtuxSame habit: file where the conversation is.
Halp formCategory, the starting taxonomy Tux AI triages againstForms tell you what each request type needed to ask.
RecipesTux AI triageKeyword rules are not ported.
Status, assignee, priorityStatus: Open, In Progress, Resolved, Closed; Owner: an Admin or Agent memberTaken from the JSM export if your tickets were migrated.
Thread replies / private repliesComment / Internal note, never shown to the requesterAs jsdPublic in JSM.

What carries over

  • Tickets Atlassian migrated into JSM, exported from there
  • The Slack intake habit: same channels, a FlowTux shortcut instead of an emoji
  • Forms, as the starting category list

What does not

  • Recipes, replaced by Tux AI triage
  • Halp data that was never migrated, if it is no longer reachable
  • JSM chat configuration

The Halp plan, step by step

  1. Find where your tickets wentIf someone ran Atlassian’s Halp migration tool, there is a JSM service project per Halp queue. If nobody did, check whether anything is still reachable before planning on history.
  2. Export from JSMFollow the Jira Service Management steps: search/jql with fields=*all, comments with jsdPublic, batches under 10,000 for CSV.
  3. Connect Slack to FlowTuxSettings > Integrations > Connect Slack, then add FlowTux to the channels Halp used to watch.
  4. Send the export; we map itWe turn Halp forms into categories and keep private replies internal.
  5. Run both for two weeksPin one message in each channel: new requests go to FlowTux, open ones finish in JSM. Then remove JSM chat from those channels.

Run both. Decide with data.

The risk in switching helpdesks is not the import. It is committing before you know whether the AI actually closes your tickets. So keep Halp running, send new tickets to FlowTux, and compare the two queues on live traffic for two weeks. If the numbers do not justify the move, you have lost two weeks and no data.

How long it takes

Time depends on the JSM export, not on Halp. The parallel run is two weeks.

Migration help is included: we do the import and the field mapping with you on a call, at no extra cost and on every plan. There is no self-serve importer, so nothing loads until you have seen the mapping.

Halp migration FAQ

Is Halp still available?

No. Atlassian stopped selling Halp on May 9, 2023 and existing customers kept access until June 4, 2024. Since then its features are only in Jira Service Management Cloud.

What replaced Halp?

Atlassian renamed Halp to Atlassian Assist and folded its conversational ticketing into Jira Service Management as Jira Service Management chat.

Where are our old Halp tickets?

If your team used Atlassian’s Halp migration tool, they are requests in a Jira Service Management project and export from there. If nobody migrated them, check with Atlassian whether anything is still reachable.

Do we need JSM to keep ticketing in Slack?

No. FlowTux files tickets from any Slack message with a shortcut or the /flowtux command, and posts status back to the thread.

Start with two weeks in parallel

Keep Halp running. Point one channel at FlowTux, send us the export, and compare the two queues on live traffic before anything is switched off.