Move to another parent or space

The Move to… popup

It is laid out like Confluence’s own Move dialog. The heading counts the pages that will go, Move 3 pages, above the line Choose a space, then the page to put them under. Their child pages move with them.

• Spaces, on the left. Every space you can see that has a home page is listed, except archived spaces. The one you are organizing comes first, tagged This space, and its pages show straight away while the rest load; the others follow, most recently updated first, with spaces that have no recent edits after them by name. Find a space narrows the list by name.
• Pages, on the right. The first row, Top level of Archive, puts the pages at the space’s top level. Below it come the space’s top-level pages and folders; the arrow beside one shows its child pages, a level at a time.
• Or search. Find a page in Archive finds pages and folders in the chosen space by title, 50 at a time, with Show more for the next 50. Search can lag a few seconds behind Confluence, so a page created moments ago may not turn up yet: browse to it instead.
• Rows you can’t choose. The pages you are moving are tagged Moving, since a page can’t go under itself, and the parent you are looking at is tagged Already here. Neither can be chosen or opened; to reach a page beneath Already here, search for it.

The footer reads back your choice — Moving to Old policies in Archive, or Moving to the top level of Archive — and says Choose a page to move them under. until you pick one. For another space it adds If a title is already used in Archive, you can rename it or leave it out. Move here works once a destination is chosen. Cancel closes the popup and changes nothing; clicking outside the popup doesn’t close it.

First or Last

Beside Put them, First puts the pages at the top of the new parent’s child pages, and Last, the default, at the bottom. Either way they arrive together, in the order they had in your list, and Unsaved changes says which: at the top or at the bottom.

To put them somewhere in between, move them within this space, then open the new parent — from the page tree, or by clicking its title in the list. The pages are there, marked Moving in, and you can drag them into place before you save; the move then reads placed where you put them. The app reminds you after each such move: Open How we work to put them exactly where you want.

For a move into another space, the organizer stays on the space you opened, so the pages land first or last. Once the move is saved, open that space in Page Order to arrange them.

Move to… in the ••• dialog

Opened with Organize Child Pages from a page’s ••• menu, the organizer is already a dialog, and it can’t open a popup on top of itself. There, Move to… drops down a smaller picker with the same choices:

• A space list beside the heading, Move 3 pages to.
• Find a page — type to search the chosen space. With nothing typed it browses: the arrow beside a page shows its child pages, the ‹ row above them goes back up a level, and the first row puts the pages straight into what you are looking at: Top level of Team Handbook, or Into How we work once you have opened a page.
• Put them First or Last, along the bottom, with the reminder Child pages move with them.

Choose First or Last before you click a destination. There is no Move here button: clicking a page stages the move at once. The pages you are moving and the parent you are in aren’t listed. Esc or a click outside closes the picker.

Moving to another space

Any space in the list can take the pages, but each move still has to be one Confluence lets you make there. The app acts as you, so a page Confluence won’t let you move into that space is reported when you save, and the rest still move (see Results).

When a title is already used there

Confluence keeps page titles unique within a space, whatever their capitals, and won’t move a page into a space that already has its title. So before the move is listed, the app checks each page’s title against the other space and finds a free title for each one that clashes (the panel reads Checking the pages…, then Finding free titles…). Then it asks, above the list:

This title is already used in Archive. Confluence won’t move a page there under the same title. Rename it and move, or leave it out?

Each clashing page is listed with its new title, “Weekly sync” → “Weekly sync (1)”, the first five in full and then and n more. With several, the question opens n titles are already used in Archive. Until you answer, you can’t tick, drag, sort, move or save.

• Rename and move — each page takes the first free numbered title: “Weekly sync (1)”, else “Weekly sync (2)”, and so on, as Confluence’s own Move suggests. Free means not used in either space, and not already given to another page in the same move. The rename happens when you save, just before the move, and makes a new version of the page, like any rename. Unsaved changes shows 1 renamed first (title taken there) on the move, and renamed to “Weekly sync (1)” beside the page.
• Leave it out (Leave them out for several) — the other pages still move, and the clashing ones stay where they are. The move notes 1 left out (title already used there); open it to read “Weekly sync” wasn’t moved: Archive already has a page with this title. If that leaves no page to move, nothing is listed and the panel says 1 page left out: Archive already has a page with the same title.

If none of “(1)” to “(100)” is free for a page, it is left out without asking.

Child pages move with the parent

Moving a page takes everything beneath it along, every level down, as Confluence’s own Move does. Each page you pick counts as one page move however much sits beneath it, and one save can send up to 1,000 pages to new parents. Past that, Save changes is switched off and the panel says That’s n pages moving to new parents. One save can move up to 1,000: cancel some with × and move them in a second save.

Pages with more than 1,000 pages beneath them

Confluence can’t move such a page at all, not even with its own Move, so the organizer marks it Too big to move out and Move to… leaves it behind:

• The popup counts only the pages that can go: tick three with one of them too big, and it reads Move 2 pages.
• When every ticked page is too big, Move to… is switched off; point at it to read Too big to move out: Confluence can’t move a page with more than 1,000 pages beneath it.
• A ticked page that is too big stays where it is, and the move notes 1 left out (too big to move); open it to read “Projects” wasn’t moved: it has n pages beneath it. Confluence can’t move a page with more than 1,000 pages beneath it, not even with its own Move. Move some of its child pages out first. The app counts again when you move, so a page that has only just grown past the limit is caught too.

Such a page can still be reordered within its own list (see Select and drag pages), and Limits has every ceiling in one place.

Changing your mind

• Move a page again and it goes to the new place instead: the earlier move is replaced, not added to.
• Move it back to where it came from and the move is cancelled.
• Press × on the move in Unsaved changes (Cancel this move) to cancel all of it: its pages go back to their old places.

Nothing reaches Confluence until you press Save changes; see Review and save.