Skip to content
PostRoll Help

Importing content

Most people arrive with a world already written somewhere else. Bringing it across should take one pass, and you should be able to see exactly what will happen before anything is added.

Where to start

Section titled “Where to start”

Open your world and choose Import pages… from the sidebar’s + menu, or go straight to /app/worlds/<your world>/import.

What you can import

Section titled “What you can import”
Source What comes across
Obsidian A whole vault: folders, [[wikilinks]], YAML frontmatter and attachments.
Notion A “Markdown & CSV” export: pages, sub-pages, images, and databases as tables.
Google Docs A document downloaded as Word or HTML, formatting intact.
Microsoft Word A .docx, with its embedded images.
LibreOffice An .odt.
Markdown One or more .md files.
World Anvil A world export: articles, timelines and their events, maps with their pins, and images.
LegendKeeper A project export: pages, maps with pins, timelines and boards.
PostRoll world bundle A whole world you exported from PostRoll — everything, exactly as it was.

Maps, timelines and boards

Section titled “Maps, timelines and boards”

World Anvil and LegendKeeper hold more than writing, and it comes across too:

  • Maps become world-map scenes with their pins in place. Neither export includes the map artwork itself, so the review step asks you to pick an image — the pins are the part that would be painful to recreate, and they land correctly once you choose one.
  • Timelines become timelines, with their events in order.
  • Boards (LegendKeeper) become boards. This one is a best approximation: sticky notes, text, shapes, frames and drawings map onto our equivalents, and anything without a counterpart is left out rather than faked.

Getting your export out

Section titled “Getting your export out”

The fiddly part of moving is usually finding the export button in the app you’re leaving, so the wizard walks you through it per source. In short:

  1. Obsidian — find your vault folder and compress it into a .zip.

  2. Notion — open the page or workspace, choose ••• → Export, pick Markdown & CSV, and turn on Include subpages.

  3. Google Docs — File → Download → Microsoft Word (.docx).

  4. World Anvil — open your world’s settings and choose Export world. You’ll get a .zip.

  5. LegendKeeper — open your project settings, choose Export, and pick the JSON format.

The review step

Section titled “The review step”

Nothing is written to your world until you confirm. Before that you’ll see:

  • How many pages, folders, images and links are coming.
  • A list of every page, with a checkbox on each — untick anything you don’t want. Unticking a folder leaves out everything inside it.
  • Anything worth a look — images that were referenced but missing, links that couldn’t be matched, and notes about what a format simply doesn’t carry.

Then Import, and you’ll get a plain summary of what landed.

Large imports — a vault, a Notion workspace, a World Anvil world — run in the background, so you can close the tab and come back. Single documents are converted right there in the page, because waiting on a queue for one Word document would be slower than doing it.

Section titled “Links between your pages”

Obsidian [[wikilinks]] and Notion’s internal links become real PostRoll links, so your world stays joined up rather than arriving as a pile of documents. Aliases are kept, so [[The Salt Crown|the crown]] still reads “the crown”.

Two cases don’t resolve, and both are reported rather than guessed at:

  • The target isn’t in this import — the text is kept, without the link.
  • More than one page has that name — e.g. a Notes in two folders. Rather than pick one at random and quietly point at the wrong page, the link is left as text for you to set.

Images

Section titled “Images”

Images inside your vault, archive or document are uploaded to your asset library as the import runs, and the pages point at them. Both ![[map.png]] and ![](attachments/map.png) work, and an image referenced twice is only stored once.

If an image is referenced but isn’t actually in the file, it’s listed in the review step and left out rather than stored broken.

What doesn’t come across

Section titled “What doesn’t come across”

Some things aren’t in the export files at all, so no importer can recover them:

  • Notion — database views, filters, formulas, rollups, comments and page history. A database arrives as a table of its values.
  • Obsidian — plugin-specific syntax, canvases and graph settings. Embedded notes (![[Some Note]]) become links, since PostRoll has no transclusion.
  • World Anvil — map artwork (pick an image in the review step), manuscripts, and the styling from custom article templates. The writing in those templates does come across, as headings.
  • LegendKeeper — map artwork, and board elements with no counterpart here.

If your import is bigger than your plan

Section titled “If your import is bigger than your plan”

A Starter plan holds 20 wiki pages and 1 GB of storage, and a real vault will pass that easily. This is handled openly rather than as an error at the end:

  • You’re told before you confirm. The review step does the arithmetic and says so plainly — “Your plan allows 20 wiki pages and you have 3. Of these 900 pages, 17 would be imported before the limit is reached.”
  • The plan that would fit is named. If an upgrade would let the whole import through, there’s a See plans button right there with the right plan already chosen. If no plan would fit — a genuinely enormous image library — nothing is suggested, because pointing you at an upgrade that still wouldn’t finish would be worse than saying nothing.
  • It doesn’t stop you. You may well want 17 pages now and to upgrade later. The button stays enabled.
  • What arrived is real and safe. If an import stops at the limit, the pages that landed are proper pages — not half-written drafts.
  • You can always undo it. A stopped import is undoable exactly like a finished one.

If an import does stop at a limit, the same See plans button appears next to it in your import history, beside Undo.

Running out of storage behaves the same way, with one difference: your writing still comes across in full, and only the images stop. Free up space or upgrade, then run the same import again to bring the pictures over.

Undoing an import

Section titled “Undoing an import”

Every import records exactly what it created, so Undo removes precisely those pages, folders, maps, timelines, boards and images — and nothing else. A page you wrote by hand a minute later is untouched.

Find it in the import history at the bottom of the import page. Two things worth knowing:

  • If you’ve edited any of the imported pages since, you’ll be warned and shown which ones before anything is removed.
  • Imports that stopped part-way can be undone too. That’s usually what you want after hitting a plan limit: undo, upgrade, and run it once cleanly.

Backing up or moving a whole world

Section titled “Backing up or moving a whole world”

Export this world on the import page downloads a .postroll bundle — everything in the world, including its maps, boards, timelines and the images they use, in one file.

It isn’t behind a paid plan, and it never will be. Being able to take your world out is what makes putting it in a reasonable thing to do.

To restore one: create a new, empty world, open its import page, and upload the bundle there.

Your characters and people aren’t in the bundle, on purpose. They belong to you rather than to a setting, so a world you send to someone else doesn’t take your character roster with it.

Adding to the page you’re on

Section titled “Adding to the page you’re on”

The import icon in the editor’s header still adds a single file’s contents into the page you’re currently editing, after what’s already there. Use the import workspace when you want to create pages rather than extend one.

Section titled “Related”