MOVE now limited to 100 pages...so how do we work?

[Rita Nygren]

TL;dr:  MOVE now has a 100 page limitation, which makes shifting large hierarchies of pages difficult.  Anyone got a workaround or can we get the full function back?

This past weekend, I did a migration of spaces from a legacy cloud instance to our primary instance - we've been regularly compiling all these, it's my 4th in the past 12 months.  Because all the users already exist in the primary instance, and most of the legacy instances have some obsolete spaces, I've not been using the migration tools, but instead export/import of spaces - which has worked fine for what I need, but if there's a a space with the same key as the destination instance, I have to MOVE all the pages to a newly created page on the source.

And MOVE will no longer allow you to grab the top level of the hierarchy and shift it to a new location, keeping the hierarchy under it intact.

This means I have to break apart spaces to re-key them, then once migrated, break apart any space that needs to be attached to a destination space.  A teammate was trying to merge some large hierarchy of pages to a different space and so far hasn't succeeded because he can't figure out where to break it apart.  Doing this deconstruction/reconstruction is an absolute time suck, along with all the human error possibilities.

Can we somehow get this functionality back?  Has anyone else come across this and have a workaround?

[Adam Shackleford]

I/we are facing the same challenge. Anyone have a work around beside dragging and dropping each entry into another space?

[Kristian Klima]

@Adam Shackleford See my reply elsewhere in this thread (not sure where exactly it will slot it :) )

[Kristian Klima]

Hi @Rita Nygren 

There's a Copy Page Tree app which I'm using for the exact same purpose as you want to.

Also: Copy Pages for Confluence 

Completely free but I have no experience with but also works cross space, so worth giving it a try.

[Mike Westcott]

@Kristian Klima There is a downside to this alternative - copying pages to a new space will create new page IDs, and will break previously referenced incoming links to the copied content.  Content owners should be aware of that, and the fact that they'll lose page version history when using this workaround.

[Rita Nygren]

For anyone following this - Atlassian tells us they've upped the limit to 500 pages. 

[Haddon Fisher]

I am not seeing this...do we have to request it specially?

[Rita Nygren]

If it doesn't just work at 499 pages, perhaps?  We honestly made a nuisance of ourselves with support. 

Note that it stopped giving us the 100 page limit error, but still appeared to fail, but in actuality kept doing the work behind the scenes - we have to wait 5-1 minutes and then check where the pages actually are.  Support is still worried about page collisions, so please use warily.

[Haddon Fisher]

Support was able to do this for us!

I ended up moving a big chunk of content manually while they were trying to do it, and started getting the '100 page limit' error even trying to move less than 100 pages. I eventually was able to move it once I got down to ~65, but I have anecdotal reports of it happening as low as 26. 

Is our instance haunted or is anyone else seeing this too?

[Kristian Klima]

@Rita Nygren 

You can also look into apps that 'publish' or 'sync' content from one space to another.

• Comala Publishing
• Space Sync for Confluence
  This one is bi-directional which offers extra options in terms of preserving history and links (as @Mike Westcott rightly pointed out).

I'm not sure what your exact use case / desired state is but it's worth exploring as many options as you can, especially if you want to manipulate Confluence content on a large scale (and/or repeatedly).

Confluence apps ecosystem is really great - not only there's an app for pretty much anything,  you can test them for free for a couple of weeks and you're billed per month so even if this is a one-off use, test it, deploy it, pay the bill for a month or two, uninstall when not needed anymore.

[Rita Nygren]

I can't say I'm interested in a large chunk of monthly subscription for something the app used to do last year.  I'm sure those apps are great for their other functions (that I don't need).

The flexibility and easy of re-shuffling data was part of the selling point for this tool, and between the MOVE limitation and the new requirement that you need to be Admin on both source and destination make this that much harder.

[David Saint-Germain]

You can't even reorder pages in the page tree if they have more than 100 child pages. Why?
This is a simple metadata tag that specifies the order in the existing hierarchy. There should be no updating of links to do in this instance. The parent does not change. 

This seems like lazy programming to reuse a single purpose API.
As what said before, you can't just break a functionality that everyone is using, not provide a workaround and expect people to go about their business. This is a complete lack of consideration for your customer base.