Move notes between vaults
Move one note, a selection or a folder from one vault to another, with links, files and databases kept working, a clear warning about who can read them, and Undo.
A note lives in one vault: your own, a team's, or your organisation's (see Vaults). Move to vault… takes notes from one vault to another in one step.
Where to start a move
- One note: the note's ⋯ menu, Move to vault…; or press ⌘⇧U (Ctrl+Shift+U) with the note open; or type "move" in ⌘K and pick Move to vault….
- A row in the sidebar: right-click it (or its ⋯), Move to vault…, or focus it and press M. A folder moves with everything under it.
- Drag: while you drag a row in the sidebar, your other vaults appear above the tree. Drop the row on one to move it there (you still confirm).
- Many notes: select rows in the sidebar, then Move to vault… in the bar under the tree, or press ⌘⇧U.
Selecting rows
| Do | To |
|---|---|
| ⌘-click (Ctrl-click) or the row's checkbox | select or unselect one row |
| Shift-click | select every row from the last one you picked |
| Shift+↑ / Shift+↓ | extend the selection from the focused row |
| X | select or unselect the focused row |
| ⌘A (Ctrl+A) in the tree | select every row shown |
| Esc | clear the selection |
A selected folder takes everything under it, opened or not. The bar under the tree counts the notes.
The steps
- Pick the vault. Only vaults you can add notes to are listed: your own, your teams', and the org's if you manage the organisation. Type to filter, ↑↓ and Enter to choose.
- Pick a folder there, or the top level. Backspace on an empty search box goes back.
- Confirm. Notes checks the move first and tells you what will change, then Move (or Enter) does it in one request.
The result says how many notes moved and how many stayed, and has Undo.
Who can read the notes after a move
A move changes who can read the notes, and the confirm step says how:
- More people: moving from your own vault to a team's or the org's vault, or from a team's to the org's. The step names the new audience: "everyone in Acme" or "the Platform team".
- Fewer people: moving out of the org's vault or a team's vault into a smaller one. The step counts the people who lose access and names some of them.
- Another team: from one team's vault to another's, members of the first team who are not in the second lose access.
Organisation admins can open every team vault, so they never lose access to a team's notes.
What you need
You need to be able to change both vaults: the one the notes are in (to take them out) and the destination (to put them in). Your own vault is yours; a team's vault is its members' (and org admins'); the org's vault takes changes from people who manage the organisation. Notes checks this on the server for every note, whatever the page shows.
A note stays where it is, and the result says why, when:
| Reason | Meaning |
|---|---|
| no permission | you can read the note but not take it out of its vault |
| not found | the note is gone, is someone else's, or is in another organisation |
| locked | the page is locked; unlock it first |
| already there | it is in the destination already |
| name too long there | its new path would pass the 300-character limit |
Notes that can move, move together. Nothing is moved half-way: if the move fails, no note moves.
A vault from another organisation, or a team vault you are not in, is "not found".
Links and backlinks
[[Links]] keep pointing at the same notes.
- Inside one vault, a link names a note by its title, as in Obsidian.
- A link that now crosses from one vault to another is rewritten to name the note by its id, and keeps the text you
read:
[[Plan]]becomes[[note:0190…|Plan]]. It still shows as "Plan" and opens the same note. - A link that no longer crosses vaults goes back to a title link. Moving notes back restores the text they had.
- A link that would now mean a different note (the destination has its own "Plan") is rewritten to keep its target.
Backlinks update on both sides. Someone who cannot open the other vault sees a link to a note there as a missing link, and clicking it says the note is in a vault they can't open. They never see its title, text or backlinks from it.
Names already taken
If the destination folder has a note with the same name, both are kept and the moved one gets " (moved)" (then " (moved 2)" and so on). A moved folder whose name is taken there is renamed the same way, as a whole, so it does not mix with the folder already there. The confirm step says how many names change.
What moves with a note
| What | After the move |
|---|---|
| History, comments, the live document, links from Tasks, workspace references | keyed by the note, so they follow it |
| Files and images in the note | move into the destination vault; a file that a note left behind also shows is copied instead |
| An inline database the note shows | moves with it (its rows' folder goes into the same folder) |
| Databases inside a moved folder | move with the folder |
| Search and Ask | find the note in its new vault; meaning-based links and topics are computed again there |
| Suggestions waiting in the Inbox | follow the note to its new vault's Inbox |
| Favourites | stay in your list; they show when that vault is open |
| The sidebar's manual order | the note leaves its old folder's order; a moved folder keeps its own |
The change feed (workspace_change_list) |
a "deleted" entry in the old vault and a "created" one in the new |
Shares and published pages
- Per-note shares and channel shares only mean something in a personal vault: in a team's or the org's vault, the vault decides who reads. Moving a note out of your own vault removes them, and the confirm step counts them.
- Published pages stay published in your own vault and in the org's vault. A team vault's notes are not published, so moving a published note into one takes its public link down.
Undo puts removed shares and public links back with the notes.
Undo
The result's Undo moves the notes back to their old vaults and paths, and puts back the shares, public links and databases the move changed. Undo is open to the person who made the move, for a day. If someone took a note's old name in the meantime, the note comes back as " (moved)" beside it.
Agents
The globe_note_move tool moves notes or folders, globe_note_move_preview reports what a move would do (including who
loses access) without writing anything, and globe_note_move_undo undoes one. An agent should tell the person who will
be able to read the notes before moving them into a wider vault.
{"notes": ["<note id>", "<note id>"], "to": "org", "folder": "Projects"}{"folders": ["Drafts/Q3"], "from": "me", "to": "<team vault id>"}The result lists each moved note with its new path, url and reference (note:<id>), the notes that stayed and why,
and the move's id for Undo. The tools work inside workspace_batch_run too. Over HTTP: POST /globe/api/notes/move,
POST /globe/api/notes/move/preview and POST /globe/api/notes/move/undo with the same fields.