Bulk-Moving All Child Pages to Another Parent with the WikiPakk Page Tree (Video)
The WikiPakk page tree can move all child pages of a parent page to another parent in one go. That comes in handy when cleaning up a site, or when a new home page takes over and all children of the old home page should move along, without touching every page by hand.
This video shows the whole flow: moving all child pages from one parent to another, setting alphabetical order, and moving child pages to the tree root.
Prefer to read, or want to jump to a specific part? Each section below links to the matching moment in the video.
AI Note
The step-by-step instructions were automatically generated from the video transcript.What bulk move is for
Moving multiple child pages of the same parent to another parent is useful when cleaning up, or when changing the home page and all children of the old home page should move over. WikiPakk is already installed on the demo site: there is the breadcrumb bar at the top and the page tree button. Expanding the tree shows a home page with three children: Standard Content, Special Content, and Info Center.
▶️ Watch from the start · start 0:00 · duration 0:47
Moving all child pages to a new parent
The goal: move everything under Special Content over to Standard Content. Go to the old parent page, click its three dot menu, and select Move all child pages. Choose the new parent, then click Move. The Move all child pages dialog shows how many child pages will be moved, and from where to where. Confirm with Move, and the pages move one by one to the new parent. After a moment a green message appears: All child pages were moved. Click Close, the tree reloads, and all former children of Special Content now sit under Standard Content.
▶️ Watch this part · start 0:47 · duration 1:16
Sorting alphabetically and moving back
The moved pages can be put in order right away: the three dot menu offers Set alphabetical order, which sorts the children alphabetically. Moving everything back works the same way: Move all child pages, choose the old parent in the dialog, click Move, wait for the pages to be moved, then Close. The nodes reload and Special Content has its child pages back, plus the pages that already lived under Standard Content: the move always takes all child pages of the parent, not just the ones that arrived in the first move.
▶️ Watch this part · start 2:03 · duration 0:44
Moving all child pages to the tree root
Sometimes child pages should become root pages. There is no parent node to select for that, so the three dot menu has a separate option: Move all child pages to tree root. The dialog is basically the same, asking to confirm the move to the tree root. It also gives a heads up when there are already lots of root nodes, because too many root nodes can make the tree slower over time; expanding the tree has to load all of them. A dozen new root pages are no issue; hundreds are where it starts to matter, and some customers have tried thousands, which makes little sense for usability. In those cases it is better to restructure the content and use the hierarchy the tree provides.
▶️ Watch this part · start 2:47 · duration 1:44
A virtual hierarchy on top of the Site Pages library
Important to know: the page tree is just a virtual hierarchy. SharePoint itself does not care; all pages always live in the Site Pages library, in this case pages from a Confluence migration. The tree puts a virtual hierarchy on top of that, so users can actually navigate a larger number of pages.
▶️ Watch this part · start 4:31 · duration 0:34