How to migrate self-hosted jira with msSQL v6.1 to atlassia confluence. we are using it as end user?

[Udaykiran.Komati]

Hello every one.

we have 2 instances of Jira 1. self-hosted (windows os, MSQL db) version 6.1  and 2. confluence which maintaining by the atlassian. we need export the enitre self hosted jira projects and data to the confluence. 

if any body have idea please suggest us.

[Nic Brough -Adaptavist-]

This can't be done.  Confluence and Jira are two totally different systems.  The data for one is nonsense for the other.

Please could you explain what you're actually trying to do?  Change the hosts for each of the two systems?

[Udaykiran.Komati]

Hi Champion,

again rephrasing my issue. 

Thanks for your quick response.

we have hosted jira instance on our windows server with MSSQL (jira version is 6.1)  its license  also expired in 2015. also we have another license  from atlassian and we are using a end url (as services ) we don't have any access to the servers (don't version as well) . so please suggest how to migrate the data of self-hosted instance to atlassian service.

[Nic Brough -Adaptavist-]

I think what you mean is that you have a Server Jira install, and a Cloud Confluence.

You can NOT "migrate" a Jira into a Confluence, they are totally different systems, with totally different data.  But if you want to stop hosting Jira, you can

• Buy a Jira Cloud (in the same atlassian account that owns your Confluence)
• Upgrade your current server Jira to 7.7
• Export the 7.7 Jira to xml and import it into your Cloud account

This is not a simple task though, you may struggle with users etc, so you might want to engage an expert.

[Udaykiran.Komati]

small correction form my side it is not confluence, we are using jira software as services. we have only a url .

[Nic Brough -Adaptavist-]

So this is not a move of Jira from Server to Cloud, but a merge now?

[Udaykiran.Komati]

yes it is kind of migration of old projects to the cloud jira. if we export the old projects to cloud is there any chance to conflict the existing projects.

[Nic Brough -Adaptavist-]

Very much so.  Merging on to Cloud is fraught with issues, depending on what route you want to take.

If you want a full proper merge (keeping history etc), you'll need to download your cloud data, upgrade the server, merge them on server then export the merged data and use it to overwrite your whole Cloud system.

A lesser merge would be less painful - importing some of the issue data into pre-prepared Cloud projects.