• Products
  • Get started
  • Documentation
  • Resources

Migrating from Halp to Jira Service Management basics

Halp’s features will be exclusively available in Jira Service Management starting on June 4, 2024. Keep working on requests from Slack or Microsoft Teams as you are today by migrating to Jira Service Management.

Get to know your migration home

Visit your migration home to get an overview of your connected cloud sites and queue progress. Both queue and global admins can access migration home, but queue admins can only view information for their specific queues.

You can also get a quick snapshot of your billing information and access data export tools from migration home.

Understand the queue-by-queue migration approach

Our migration process allows you to migrate each queue individually rather than requiring you to migrate them all at once. This is helpful if you have multiple teams using Halp at your organization, with each team requiring its own migration timeline.

Global admins can migrate every queue, while queue admins can migrate their specific queues.

Overview of the migration process

The migration process automates many of the steps required to move your data from Halp to Jira Service Management. The migration process includes:

  1. Connecting your Atlassian cloud site to your Halp account

  2. Creating a service project and copying over Halp queue statuses, fields, and forms

  3. Inviting your agents

  4. Connecting your queue and your service project

  5. Migrating your tickets (optional)

  6. Setting up your service project to match Halp (optional)

We consider a queue fully migrated once it’s connected to your service project. Your Slack or Microsoft Teams setup will continue to function during and after the migration process. You’ll customize your setup from the chat section of your service project settings.

Still need help?

The Atlassian Community is here for you.