I have not seen this happen before. However if I had to guess it seems like that the initial estimate for the amount of data to be imported might be inaccurate vs the actual data being imported. However I have not seen any other reports of this specific problem before. So I am curious to learn more about your instance and see if there is a specific problem with our migration process or perhaps if there is something special about your dataset being imported that might be a factor here.
Any other details you can provide here would be helpful as well. Do you have an existing support ticket on our https://getsupport.atlassian.com tracker for this issue?
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs