Migration of your services
Who this is for: anyone on a Jira Service Management Standard, Premium, or Enterprise plan who is using the older Services experience. If you're new to services, start with What are services?
This article describes the new Services experience in Jira Service Management, which uses Assets schemas as the underlying data model. It's relevant during the migration period only.
Free plan: services aren't available on the Free plan after 31 July 2026. Upgrade to a Standard, Premium, or Enterprise plan to keep using services.
Services in Jira Service Management are moving to a new experience built on Assets schemas. Your services and data come with you, the move is automatic, and for most teams there's nothing to do. This article explains what changes, what moves for you, and the few actions some teams need to take.
What's new
The new experience splits your services across two schemas: Software Registry for your software services and Business Portfolio for your business services. This separation gives you clearer management and governance, and each schema comes with ready-made object types and attributes so you can get started quickly. See Understand service types.
Beyond the new structure, you can now:
View and edit services from both Jira Service Management and Assets.
Add custom object types and attributes, which the older locked schema didn't allow.
Set permissions on each service schema.
Assign an Atlassian team as the owner or responder for a service.
Link repositories from GitHub, GitLab, and Azure DevOps, as well as Bitbucket.
You also get a clearer services home for tracking service health and a richer, more scalable visual service graph.
For more on why services are moving, see Services & Assets: one source of truth with two new purpose-built schemas in the Atlassian Community.
How the migration happens
We migrate customers in batches from the last week of July and finish rolling out to everyone by mid-August. Your data moves with no loss and your workflows keep running, so there's nothing you need to do while the move takes place. Expect a short downtime of around 30 minutes when you won't be able to create or edit services.
Once you're migrated, you'll see two new schemas in Assets, Software Registry and Business Portfolio, alongside your existing Services schema. All three co-exist until 31 January 2027, giving you six months to complete your move before the original Services schema is removed.
What moves automatically
You don't need to re-create or re-add any of the following - it all comes across for you:
Your service objects, moved automatically to either the Software Registry or Business Portfolio schema as relevant.
The attributes on those objects, including Owner teams, Repositories, and Tier.
The references and relationships between your services.
Anything linked to services through the Affected services field. This includes work items such as incidents and changes, as well as alerts and integrations.
Calls to the service registry APIs, which keep working through backward compatibility.
Actions some teams need to take
If your team references service objects from other places, you'll need to point those references at the new schemas. This depends on how your team uses services, so it won't apply to everyone. You might need to update:
Custom fields on work items that reference service objects.
Automation rules that use service objects.
Dashboards that use service objects.
References and relationships between service objects and objects in other Assets schemas.
External scripts that reference service objects. You'll need to update these yourself.
You don't have to track these down on your own. When your team has actions to complete, Jira Service Management guides you through them in the product. References outside Atlassian, such as external scripts, aren't tracked automatically, so you'll update those yourself.
Complete your move
When there are actions for your team, a Complete your move button appears on your services list. Starting and completing the move is mainly an admin task. Some individual actions, such as updating work items or moving relationships to non-service objects, can be completed by other roles too.
Select Complete your move to open the guided experience.
Work through each action that applies to you. The guide groups them by where the references live, such as work items, custom fields, automation rules, and dashboards.
For each one, select the link to choose the object and move it to the new schema. Atlassian references can be moved for you; references to anything outside Atlassian you'll move yourself.
As you finish each group of actions, it turns green so you can track your progress. When every action is done, the Complete your move button updates to show your move is complete.
Was this helpful?