After I migrate Confluence to cloud, there will be 3 types of links in JIRA that no longer resolve

[Maggie Stearns]

I am preparing for a migration of my Confluence server to cloud.
A migration of my JIRA server to cloud is not yet in scope.

After I migrate Confluence to cloud, there will be three types of links in my JIRA issues that no longer resolve (as described here: https://confluence.atlassian.com/confkb/the-differences-between-various-url-formats-for-a-confluence-page-278692715.html\)
1. Regular links (aka "pretty links" that contain space and page name)
2. Links that contain pageID
3. Tiny links

My engineering community has declared this to be a gating issue for a migration of Confluence to cloud.

I have seen this unresolved problem:
https://jira.atlassian.com/browse/CONFSERVER-27049

I am wondering if there are other customers or special solutions teams who might have already solved this. Any pointers would be greatly appreciated.

-Thank you

Maggie Stearns

[Jimmy Van]

Hi Maggie,

Great question. While there are open JAC tickets, we do have a number of scripts to fix your regular/pretty links, links referred to by ID and to fix tiny links :)

Please see 

After a successful Server to Cloud Migration, URL links are broken in the new Cloud instance

for more details and what's in scope.

---

To proceed, please raise a support ticket for the migrations team:

What can we help you with? > Migration support

and then when picking "Where are you in your migration?" > Select "Post-migration".

We'll then need the 3 pieces of information mentioned in the knowledge base article above:

• Previous Base URL of Jira Server
• Previous Base URL of Confluence Server
• Mapping of Page IDs from Confluence Server which can be fetched via this database query: 

SELECT c.title,
       c.contentid,
       s.spacekey
FROM content c
JOIN spaces s ON s.spaceid=c.spaceid
WHERE c.contenttype='PAGE'
  AND c.prevver IS NULL
  AND c.content_status='current'
  AND c.title !=''
  AND c.title IS NOT NULL ;

 in csv format.

Cheers,
Jimmy

[Maggie Stearns]

Just checking that you are seeing that our JIRA server is staying as a server with the same base URL. 

[Jimmy Van]

Hi Maggie,

Thanks for clarifying. Our scripts should work if we can get the correct information (various SQL queries), but please note this will be best efforts only. We always find gaps, for example, an old Jira issue refers to a Confluence page which has since moved space, been renamed (new page title) or been deleted.

As with all database fixes, we strongly encourage you to test in a non-production environment. When applying the changes to production, we expect database backups and rollback procedures to be in place, complying with local change management procedures.

Regards,
Jimmy

[Maggie Stearns]

The scripts that you can provide will be run by me on my JIRA server database?