Skip to content
Verkilo Docs
Esc

    Type to search all 32 pages.

    verkilo.com
    Browse the docs

    Importing from Scrivener

    Moving from Scrivener? Verkilo can import a Scrivener project and preserve the structure you’ve already built.

    3 min read Updated Mac · Windows · Linux

    Running the import#

    1. Open the Verkilo project you want to import into, or create a new one.
    2. Choose File ▸ Import ▸ Scrivener Project….
    3. Select your .scriv project in the picker, or a ZIP backup of one. On Windows and Linux, a project is a folder: select the .scrivx file inside it.
    4. Verkilo reads the project and shows you what it found — the project name and a Will create summary counting the sections, characters, locations, notebook entries, and tags it’s prepared to make.
    5. Set the Book name for the book these sections will land in.
    6. Choose what to bring across under Include (see below).
    7. If the dialog offers decisions worth reviewing, expand it and read them.
    8. Click Import.

    Nothing is written until you press Import, and the import runs as a single transaction — if it fails partway, your project is left exactly as it was.

    Choosing what comes across#

    Each Include switch can be flipped on or off before you commit, and the counts update as you do:

    • Research folder — the characters, places, and notes from Scrivener’s research area, mapped onto Verkilo’s Series Bible.
    • Loose documents — anything outside the draft folder, brought in as notebook entries.
    • Excluded from compile — documents you’d marked “do not compile” in Scrivener. They’re kept, and carry the same mark in Verkilo.
    • Labels as tags — your Scrivener labels, as tags.
    • Statuses as tags — your Scrivener statuses, as tags.
    • Trash — off by default, and usually best left there.
    • Document notes — the notes beside each document, into each section’s notes.
    • Comments and annotations — Scrivener’s linked comments and inline annotations, as comments on the text. An inline annotation leaves the prose and is pinned to the word just before it.
    • Footnotes — inline and linked footnotes, as notes in the same place in the text.
    • Snapshots — off by default. Each document’s snapshots, oldest first and with their Scrivener titles, into the section’s Version History. They make the project file bigger.

    On a character, place or notebook entry, comments and footnotes have nowhere to sit in the text, so each becomes a line under Notes in the entry.

    If the project has no manuscript folder, Verkilo says so and imports only the research and loose documents.

    Reviewing decisions#

    Some things don’t map one-to-one, and rather than guess quietly, Verkilo lists them. Expand decisions worth reviewing before importing to see what was renamed, converted, or skipped, and why. It’s worth a minute — it’s the fastest way to learn what to check first afterwards.

    After importing#

    1. Look through the sidebar and confirm the structure came across the way you expected. Reorder anything that didn’t. Front and back matter, such as a dedication or acknowledgments, lands on the book’s Front & back matter tab instead.
    2. Split any document that turned out to hold more than one scene: click at the break, right-click, and choose Split at Selection.
    3. Set Compile In on anything that shouldn’t be exported — see Books and sections.
    4. Connect your text to the Series Bible: tag scenes with their characters and locations to unlock the continuity tracking Verkilo is built for.

    Was this page helpful?