Converting many spaces to Scroll Content Manager at once is not supported. Each space needs its own setup, checks, and system resources. This article explains the reasons.
1. Health checks must run per space
Before converting a space, admins must run a Health Check first (Space tools > Scroll add-ons > Health checks). This finds issues like:
-
Broken macro structure
-
Orphaned master pages
-
Invalid attributes
Health checks cannot run in bulk. Each space must be checked and fixed (automatically or manually) until it is fully green, before conversion can start.
2. The conversion wizard needs input for each space
The conversion wizard is interactive. For every space, you need to make choices such as:
-
Set a new target space key
-
Choose which versions or variants to convert
-
Configure page and context keys
-
Copying version restrictions
We also recommend against converting everything without review. Before you migrate, check which versions or variants are still relevant. This avoids copying old, unused history into the new space.
3. Conversion uses heavy resources
Converting a space is resource-intensive. It involves for example:
-
Copying page trees
-
Rewriting macros
-
Building lookup indexes
Running several conversions at the same time puts heavy load on Confluence Data Center. This can cause long Java garbage collection pauses, memory exhaustion, slow event queues, or stuck indexing tasks. To keep the system stable during the conversion process, spaces must be converted one at a time.