Running Migration Plan fails with statusCode=502, xFailureCategory=FAILURE_ORIGIN_CONNECTIVITY 2026-

[Uwe Kühn]

• The exact error: 502, xFailureCategory=FAILURE_ORIGIN_CONNECTIVITY
• Migration ID: 14874fa5093b0855391663c512552d2417e868a3
• Cloud site ID: fce878fc-eba3-4987-8983-65c89a330c71
• Timestamp: 08-07-2026 17:14 CEST
• Migration plan name: Flightfact_Servicedesk
• Project: FLFA (FlightFacts), Jira Service Management, 7 issues, 0 KB attachments
• Migration stage: Testing
• Started: 08-07-2026 15:36 CEST
• Current status: Stuck on "Migration in progress" for multiple hours, no percentage or progress shown
• Error shown: "Communication error — Interaction with Cloud Migration Services failed" and later "Error communicating with server — Retry again in a few minutes"
• Logs/reports: Pre-migration report says "migration was run prior to release of this feature"; error log and post-migration report both show "Available after migration" — nothing logged
• Troubleshooting already done: confirmed application link to cloud site connects successfully (ruling out DNS/basic connectivity); no data or project has appeared on the destination cloud site

[Marc -Devoteam-]

Hi @Uwe Kühn 

Problem one, you have not whitelisted all IP related to Atlassian Cloud or,  the reason for this is that JCMA has lost connection to your on-prem host.

This is usually related that the connection has been terminated from the on-prem side, could be firewall ruling or some other restrictor on connection in your network

You need raise a migration issue with Atlassian Support as they are the only ones who can assist and analyse the failure.

[Arkadiusz Wroblewski]

Hello @Uwe Kühn 

What I can think of is that your firewall may be blocking something here.

IP addresses and domains for Atlassian cloud apps | Atlassian Support

But from my experience, troubleshooting this in the forum is usually a waste of time, because a lot depends on your specific setup and backend information that only Atlassian Support can see.

Check atlassian-jira.log around Failure Time Stamp and if you have Possibility, reach out to Support.

Here some things which you can also check Troubleshoot migration with Jira Cloud Migration Assistant | Atlassian Support

Best,

Arek🤠