Importing existing pages to a new Graph

[Juan_Gutierrez]

I am going from having 4 graphs to only 2, how can I import the pages already created in a graph? thanks!

[Didac]

As far as I can see, the utility of merging graphs has not yet been developed.

But, Logseq runs in a browser, the database disappears each time you leave the app and it’s rebuilded from your files each time you execute it.

So, you can just move those files from one graph"s directory to the other one. But you have to take care with some files with the same name, such as journal files, contents.md file, etc.

But if you just move/copy files from one pages directory to an other graph pages directory and there are no files with the same name, I think there will be no conflicts.

Backup your files, do some tests in an other directory and lets see what happens.

At least that’s what I would do.

[Juan_Gutierrez]

Many thanks @Didac this is helpful for me

[Didac]

Check this out:

[Partial Done] Add tabbed windows to desktop client / Multiple instances of Logseq

There are two things you can do: Query multiple graphs at the same time using logseq-query. Create a new graph and symlinks /pages folders from other graphs as subfolders like /pages/project. You just need to be sure not to use different files with the same name across all the graphs. Or if you really need to do so, you can place disambiguous files from various graphs in a subfolder of /pages and then symlink only that to the main graph.

[Didac]

@Juan_Gutierrez And this:

Partial (one-way only) merge of graphs

I would like to take notes on different devices (mobile, different laptops) and merge them to my main machine. I don’t want all notes to show up on all devices. The use-case is to have Logseq on shared systems and see all the notes on my personal PC, but not the other way around. Contributing back (editing block that are marked as from a shared system syncs them back to that system) could be useful, but is not essential.

[codekiln]

Just chiming in here to leave some breadcrumbs for anyone else in this position. Today I #Learned that [[Logseq/Highlights]] are stored in pages that start with hls__. I sync’d the Ableton namespace to another garden, and when I brought over ableton_manual_1683387803000_0.edn and ableton_manual_1683387803000_0.pdf in the [[Logseq/Asset]] folder, it wasn’t enough to make the [[Logseq/Block/ID]] show up in the corresponding page. I actually had to also sync pages/hls__ableton_manual_1683387803000_0.md to the new namespace.