Problem Definition

Before a Cloud-to-Cloud Migration,in your Source Instance, if you add an issue to Sprint A -> Move to Sprint B -> Move to Sprint C
Then you delete Sprint B

Now, when you migrate to the Destination instance, there will be no historical data from that issue moving from A to B.
So, the Sprint Report in the cloud will show that issue in Sprint A and Sprint C (only the reports, not the real sprints), where it should be showing only in the Sprint C report.

Suggested Solution

Those historical data are preserved in the server even if the Sprint is deleted.
This data needs to be migrated in order to generate accurate reports.

Why this is important

This issue creates inconsistent data in the reports, and they could lose their credibility because of that.

Current Workarounds

There is no workaround at this point.