JIRA - migration from server to other server - issue with mixed data base

[sebastien curdy]

Hi here is our issue,

Our current JIRA server is hosted on a server by an IT provider (let's call it IT1). Our company is migrating to a new IT provider (IT2).

We need to migrate our JIRA server and all data from IT1 server to IT2 server.

The problem is IT1 is also using JIRA as a tool and has mixed their data with ours (i.e.user group, users and server domain...).

A simple solution could be to make a copy of the virtual server and then delete IT1 data using the Web client. Questions are whether this will work and data gets permanently deleted?

How do we backup all our projects and backlogs etc... in a secure way so it can easily be retrieved?

Does Atlassian have some scripts/tools to do this?  We assumed this issue has been  known from other companies. 

Does anyone have a suggestion or could steer us to the right solution?

[sebastien curdy · Accepted solution]

Thank you very for both your suggested answer, I'll submit then to both IT parties.

@Rene C_ _Atlassian Support_, to answer your question, what I meant by mixed data is that IT1 and us share the same database containing JIRA project, backlogs and user groups. One cannot dissociate one from accessing the other . Hence, the cloning of the data base would imply that IT2 would get access to both ours and theirs. Since IT2 has not signed yet an NDA regarding the confidentiality of IT1 data, the process is entirely on hold.

[Rene C_ _Atlassian Support_]

That being the case, I believe the suggestion from my colleague @Andy Heinzer would fit better for your scenario.

[Rene C_ _Atlassian Support_ · Accepted solution]

Hello! I suggest giving it a look at our documentation page Migrating Jira applications to another server which will give you the steps to take the information from the server on IT1 and take it to an installation on any other server. 

When you mention mixed data, I'm unsure what it means, but the XML Backup form Jira only backs up the information from the default Jira tables as well as the add-on tables.

[Andy Heinzer]

Hi @sebastien curdy

In cases like this, we actually recommend following the guide: Splitting JIRA applications.   It explains a set of steps you can take in order to separate the specific data needed by one organization and then delete everything else in a cloned instance.  This way you can then create another XML backup of this limited data and provide it to the other organization.

There is a note on that page that:

This process requires two separate server licenses.

However for the sake of doing this, you could create an evaluation license on https://my.atlassian.com temporarily in order to complete this process.

I hope this helps.

Andy