Jira Cloud licensing & migration questions (merging two sites, external users)

[Long Luong]

I’m planning to consolidate our Jira Cloud setup and want to double-check a few things around licensing and migration.

Current situation:

• I have two separate Jira Cloud sites (e.g. project1.atlassian.net and project2.atlassian.net)

• I want to merge projects from both sites into one new Jira Cloud site

• The target site would use the Jira Standard plan

• Initially, we expect around 8 active users
  

Questions:

1. Is there a native way to migrate projects from one Jira Cloud site to another (cloud-to-cloud), including issues and attachments?

2. If we invite external users (contractors or partners) to access specific projects:

   • Do they always require a paid Jira seat, or

   • Is there any guest / view-only option in Jira Cloud similar to Confluence guests? 

I’d really appreciate hearing from anyone who has done a similar Jira Cloud consolidation or migration.

Thanks in advance!

[omar_blagui]

Hello @Long Luong,

• Jira Cloud supports native cloud-to-cloud project migrations using Atlassian's official tool. This method transfers projects, including issues and attachments, with detailed documentaion on supported and unsupported elements available here: Copy product data across sites.
• For External users like contractors or partners, options are limited. You can invite them to specific projects with browse only permissions via permission schemes, but this requires a paid jira license for each user. Alternatively, enable public anonymous access to make prjojects viewable by anyone online without license though this exposes data publicly and lacks user specific controls.
  

Kind regards,

[Jorge Cammarota]

Good afternoon! Here is the translation into English, maintaining the exact structure and meaning as requested:

Migrating projects from one Jira Cloud to another (Cloud ➜ Cloud)

Is there a native way? Partially, yes.

How? By using CSV export/import between Cloud sites:

Migrates issues and basic fields.

Does not migrate everything automatically (workflows, boards, automations, etc., need to be recreated).

Attachments do not go along by default; for that you need:

Marketplace App, or

Script via API, or

Manual process.

Official reference: https://support.atlassian.com/migration/docs/cloud-migration-methods-for-jira/

External users (contractors, partners)

In Jira Software Cloud (Standard):

Anyone who accesses Jira projects (even read-only) consumes a paid license.

There is no guest / free view-only like in Confluence.

The only unlicensed user model is the Jira Service Management customer (access via portal), which is a different product.