Space import to cloud failed. Batch import exceeded timeout

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Learn what to do when Confluence spaces fail to migrate because of batch import timeouts.

Overview

When migrating spaces from Confluence On-Premise to Cloud with the Confluence Cloud Migration Assistant (CCMA), spaces fail with the error "Import to cloud failed."

In the application log atlassian-confluence.log, you can see the same error message:

1 ERROR Step failed, taskName: Migrate space <spacekey> | stepType: CONFLUENCE_IMPORT | message: Import to cloud failed. Message: Batch import exceeded timeout

This error is commonly caused by network hiccups or when Atlassian's services experience outages or maintenance.

Solution

Due to the temporary nature of this issue, retrying the migration with the failed space is enough.

  1. Create a new migration plan.

  2. Scope the spaces that failed in the previous plan.

  3. Run the new migration plan.

If the error persists, reach out to Atlassian support.

Updated on April 17, 2025

Still need help?

The Atlassian Community is here for you.