There are no current plans to build the ability to migrate Atlassian accounts to Portal-only accounts.

Additional context:
Atlassian accounts are global by design and allow access to multiple sites. Atlassian accounts are purpose built to support internal service management use cases. It is not possible to consolidate customer data across multiple sites into a single site.

Portal-only accounts are site scoped by design and only allow access to a single site. Portal-only accounts are purpose built to support external service management use cases.

Our recommendation is to consider if your business is operating an "Internal" or "External" service management help desk and use the appropriate account for your end users.

Resources:

• Choosing the right account type
• Migrating Portal-only accounts to Atlassian accounts

Atlassian accounts with a "Customer" role

In scenarios where your "Internal" helpseekers only need access to JSM to raise support tickets - you are able to use the "Customer" role and an Atlassian account.

• Helpseekers with the "Customer" role are not billable for JSM (do not contribute to your JSM paid licence count)
• Helpseekers with the "Customer" role are not billable for Atlassian Guard (do not contribute to your Atlassian Guard paid licence count)

Note: If your helpseekers have access to other billable Atlassian products (e.g. Confluence, Bitbucket) they will be considered as a billable user for Atlassian Guard

Portal-only accounts

In scenarios where your "External" helpseekers only need access to JSM to raise support tickets - you should use a Portal-only account.

• Helpseekers with a "Portal-only account" can only access the specific JSM site you invite them to
• Helpseekers with a "Portal-only account" cannot access other Atlassian products on the same site.

These accounts are specifically designed to enable "External" service management - they should not be used for "Internal" service desks.