What are the best practices for migrating my site's data to the Atlassian suite of tools.

[Jhon Wesley]

I'm interested in migrating my site's data to the Atlassian suite of tools, but I'm not sure where to begin. Can someone provide a step-by-step guide to the migration process, including how to prepare my data, transfer it to the Atlassian tools, and ensure that it is organized and accessible once it's been migrated? Additionally, are there any tools or resources available on the community website to help me with this process, such as migration templates or data transfer plugins? Finally, are there any common issues or roadblocks that I should be aware of when migrating data to Atlassian tools, and how can I troubleshoot them if they arise?

[Nic Brough -Adaptavist- · Accepted solution]

No, you can get separate licences. 

You can tell different systems about different numbers of users - for example, if you have groups Jira, Conf and Bb, and tell the three systems to use their "can log in" group as those, then yes, you could do 2000 Jira, 2000 Confluence and 250 Bitbucket.

[Greg Bishop]

Thank you for explaining the "how to", currently people around here think everything has to be the same, but that just didn't make sense to me.

[Nic Brough -Adaptavist-]

It can be a bit more simple - if, for example, you always know Jira and Confluence systems are always going to have the same set of login users, you could do something like create group "jac-login", and use that in both for the login group.  Adding a user to that one group then lets them into both systems.

I prefer to keep them simple, clear and separate myself.

[Mikael Sandberg · Accepted solution]

No, each product does not have to have the same amount of licenses, in my environment we have half the licenses for Bitbucket compared to Jira/Confluence.

[Greg Bishop]

Awesome, thank you for the quick response!