Copy Space Plugin 2000-Page Limit Issue During Migration in Confluence Data Center

[Khammampati Surendra]

Description:

We are currently migrating from ENT01 to WIKI in Confluence Data Center. Some spaces already exist in the target instance with the same space key.

To avoid conflicts, we are using the Copy Space plugin to copy all space content to a new space with a modified space key (e.g., _v1). However, we are encountering a 2000-page limit error while copying large spaces.

Our Questions:

1. Is there a way to increase the 2000-page limit in the Copy Space plugin?

2. What alternative solutions exist to handle duplicate space keys and migrate content effectively?

Any insights, workarounds, or recommended approaches would be greatly appreciated.

Thanks!

[Kristian Klima · Accepted solution]

Hello @Khammampati Surendra 

I have a wild idea but it should work.

You're gonna need an app - there might be other apps like the one I'm about to mention for Data Center but this is one is the one I know - Comala Publishing by Appfire.

It can synchronize your content between two spaces. In other words, it pushes content from space A to space B. Then, when you change something in space A, it syncs the changes to space B.

So... In your Source Confluence, you create a Space B and push your content to it. The point is that Space B would have a different space key from any other space that you might have. So you'd be migrating Space B.

So you'll go around space the space key problem.

Once the migratted content is in your Target Instance, courtesy of Space B, move the content whereever it needs to be. 

If you're still facing issues with 2000 pages limit in Target instance, I'm pretty sure you can sync space A to space B in increments. (I don't know if Comala Publishing has sync. space limit... but incremental syncs should get your around that).

Since space B is only temporary, you can keep deleting it from your target instance with each incremental migration (again, avoiding duplicate keys issue)

It sounds complicated but it's actually easy, you just need to plan the sequence of steps carefully - and make notes of increments.

If you try it on a small ad-hoc space just to get the hang of the idea, it will come to you naturally.

Edit: using this space B should allow you to use the native Confluence space export/import feature.

[Khammampati Surendra]

Hi @Kristian Klima 

Thank you for info

When I used it, only pages are syncing with Space B. Comments, likes, and other content are not syncing. Additionally, space tools such as space permissions and content tools are also not being transferred.

Do you have any alternative solution?

[Kristian Klima]

I see. 

Check the answers to your other questiosn, @Radek Dostál 's answer should work for this usecase too.

Changing space key - you can do this programmatically with regex search in pretty much any XML editor.