Move multiple pages to another parent page

[Helen Ross]

Hi guys,

I'm looking to move ~50-100 pages from one parent page to another. I don't want to move all pages that live under the original parent, but a large number of them. 

All of these suggestions I've found only work if you are moving everything to a new parent.

Does Confluence have anything native that allows you to multi-select pages to move? I know you can drag and drop 1 by 1 but damn that's really not feasible. 

Thanks!

[SMS]

Hi Helen,

I made a feature request for this before, that you can watch and follow:

• CONFSERVER-38965

Otherwise you could copy them over with something like Copy Page Tree and remove the ones you don't need, or try reordering them from the Reorder Page feature.

Kind Regards,
Shannon

[Thendralvanan Pommandu Venkatesan]

Hello Shannon, this is Thendralvanan here. Is the feature request complete? I have the same requirement to move specific pages from multiple confluence spaces to new space? is there any GUI or Rest API method to achieve it?

Additional questions?

I also would like to understand what core benefits are of creating Confluence space with JIRA integration.?

Can I integrate a JIRA site confluence space which are created separately? If I can do, will I get the same features as creating Confluence-JIRA together?

Can I integrate multiple JIRA sites to single confluence space?

[Stephen Deutsch]

If you're running Confluence Cloud, then I can recommend the following app: Bulk Action Tools

Unfortunately, I don't know of anything for Confluence Server yet.

[Pavel Matejek]

Two years later, the easiest way for me way was to ask ClaudeAI plugin in Chrome browser to do the move. Rovo was constantly giving errors when asked to do the same... Completed in less than 30 seconds on 20+ pages.

It used Confluence's REST API directly from browser tab, rather than clicking through the UI.

The mechanism: in Confluence, a page's position in the tree isn't a folder — it's an ancestors field on the page itself. So "moving" a page is just updating that field.

The steps:

1. Listed the children of the ZYX page via GET /wiki/rest/api/content/55555555/child/page, then filtered client-side for titles starting with WHATEVER- → 25 hits.
2. Checked the target page (123123123) to see what was already there, so you'd know the moved pages were joining 4 existing ones.
3. For each of the 25, two calls in a loop:
   • GET /wiki/rest/api/content/{id}?expand=version,space — to read the current version number, since Confluence uses optimistic locking and rejects a write without the correct next version.
   • PUT /wiki/rest/api/content/{id} with a body containing the same title and space, version: {number: current + 1}, and ancestors: [{id: "123123123"}]. That last field is the actual move; everything else is just what the API requires to accept the update.

[A Grise]

Not the best, but in the process of doing the same thing, I started out just clicking the "Move" for each child page, then selecting the new parent page to drop in under.  Tedious....very tedious.

Found another way to do it was by clicking on the "..." of the child page and selecting "View in Hierarchy".  In this manner, the file structure is displayed linearly and I could click and drag each child file to a new parent directory (located in a geographically-close folder).  May help, may not....but it's better than all of the 3-4 clicks and searching I had to do with the "Move" option

[A Grise]

another quick performance improvement:

(I have a bunch of old meeting notes from over a year ago I want to put into a "2023 Archive" folder)

1. Make a temporary folder in the parent folder ("2023 Archive")
2. Click the "..." and select "View in Hierarchy"
3. Click and drag the temp folder you created to the top of your parent folder so it is the first item in the hierarchy.  I placed mine right above the first 2023 Meeting note page (i.e. "2023-Jan-01 Meeting Notes")
4. Now I can quickly click and drag the child pages I want to move into the temp folder instead of dragging it all the way down to where the temp folder would, by default, be added to the hierarchy