Migrating Scrivener Projects into Novelcrafter: How to Preserve Binder Structure and Character Lore

Transitioning from Scrivener to an AI-assisted novel writing platform is one of the most consequential workflow shifts a fiction author can make. For over two decades, Scrivener by Literature & Latte has served as the gold standard for long-form manuscript organization, offering an infinitely flexible Binder tree and corkboard planning. However, novelists looking to incorporate large language models into their drafting and brainstorming workflows quickly run into Scrivener's limitations: it has no native AI integration and no relational story bible capable of feeding context directly to a model.

Novelcrafter was designed specifically to fill that gap. It combines a distraction-free manuscript processor with a structured planning matrix and a relational story bible known as the Codex. The platform monitors character names and world terminology in real time, injecting relevant background lore into AI prompts exactly when needed.

The most common hesitation authors express when contemplating this switch is the fear of migration chaos:

• Will decades of nested Binder structure—organized into Parts, Acts, Chapters, and Scenes—flatten into an unmanageable wall of text?
• Will detailed character dossiers, magic system notes, and worldbuilding sheets trapped in Scrivener's Research folder disappear or require hundreds of hours of manual retyping?

Novelcrafter does not import raw, proprietary .scriv package files directly. However, by establishing a clear bridge between Scrivener's compile engine and Novelcrafter's import parser, novelists can migrate their manuscripts with zero structural loss. Furthermore, Novelcrafter's built-in Snippets and AI-assisted Extract to Codex tooling turn static research notes into dynamic, mention-aware story bible entries in minutes.

Architectural Mapping: Scrivener Binder vs. Novelcrafter

Before touching any export settings, novelists must understand how Scrivener's unstructured Binder corresponds to Novelcrafter's structured data model.

Scrivener treats everything in the Binder as a generic document or folder. You can place a character sketch inside a chapter folder, keep images next to scenes, and nest documents ten levels deep.

Novelcrafter enforces a purpose-built hierarchy designed for fiction: Act $\rightarrow$ Chapter $\rightarrow$ Scene. Everything related to worldbuilding lives in the Codex, where it can be referenced across chapters and automatically supplied to AI models like Claude, GPT-4, or open-source alternatives.

Part 1: Exporting the Manuscript from Scrivener

The single biggest mistake writers make when leaving Scrivener is compiling the entire project at once. Doing so dumps character profiles, deleted scenes, synopsis cards, and research notes into the main text, creating hours of cleanup.

Follow this four-step process to generate a clean, structurally tagged manuscript file.

Step 1: Binder Hygiene

Ensure your Scrivener project separates prose from research:

1. Place all actual manuscript text strictly inside the root Draft (or Manuscript) folder.
2. Confirm your hierarchy is consistent. The recommended pattern is:
   • Level 1 Folders: Acts / Parts
   • Level 2 Folders: Chapters
   • Level 3 Documents: Scenes
3. If your novel does not use Acts, your Level 1 Folders can represent Chapters, with child documents representing Scenes.
4. Keep all character sketches, location profiles, and world notes inside Scrivener's external Characters and Research folders.

Step 2: Configure Scrivener Compile

Open Scrivener's compile dialogue via File > Compile... (or Ctrl+Alt+E on Windows / Cmd+Option+E on macOS).

1. In the Compile For dropdown at the top, select either Microsoft Word (.docx) or MultiMarkdown (.md). Both formats work smoothly with Novelcrafter; Markdown is preferred for clean tag handling, while .docx is convenient for preserving italics and formatting.
2. In the left column, choose a standard format preset such as Manuscript (Times) or Default.
3. Right-click the preset and select Duplicate & Edit Format... to access Scrivener's Format Designer.

Step 3: Assign Section Layouts and Headings

In the Format Designer:

1. Navigate to the Section Layouts tab.
2. Ensure your Part/Act Folders output their title as Heading 1 (or # Title in Markdown).
3. Ensure your Chapter Folders output their title as Heading 2 (or ## Title in Markdown).
4. For Scenes, select a layout that outputs only the text content without adding redundant document titles (e.g., Text Section).

Step 4: Configure Scene Break Separators

Novelcrafter detects scene divisions using clean separators:

1. In the Format Designer, click the Separators tab.
2. Under the separation rules for text-to-text sections (Scene following Scene), set the separator to a custom string: ***.
3. Check the box to prevent Scrivener from inserting a separator after the final scene in a chapter.
4. Click Save and run the compile. You now have a clean file (manuscript.docx or manuscript.md) containing your story text with clear structural cues.

Part 2: Ingesting the Manuscript into Novelcrafter

Once your compiled file is ready, Novelcrafter handles the structural reconstruction.

Step 1: Launch Novelcrafter Import

1. Log into Novelcrafter and open your project dashboard.
2. Click Create Novel (or navigate to the left sidebar of an existing project and select Import).
3. Select your file format: .docx or .md.
4. Click Choose File and upload your compiled manuscript.

Step 2: Configure Ingestion Parameters

Novelcrafter prompts you with critical parsing options:

• Import As: Select Prose (your actual story text). Do not select Scene Summaries unless you are importing an outline.
• Scene Breaks: Set the scene break rule to match your compile settings (choose the *** delimiter or multi-line breaks).
• Heading Recognition: Novelcrafter reads Heading 1 as Acts and Heading 2 as Chapters. If your novel contains no Acts and uses Heading 1 for Chapters, Novelcrafter automatically nests scenes directly beneath chapters.

Step 3: The Verification Gatekeeper (Preview Import)

Before writing anything to your project database, Novelcrafter displays the Preview Import screen. Do not skip this screen.

Examine the preview pane carefully:

• Act and Chapter Count: Does the number of detected chapters match your Scrivener Binder count?
• Word Count: Does the total word count align with your Scrivener manuscript statistics (excluding research folders)?
• Scene Nesting: Are scenes properly grouped under their respective chapters rather than stacked into a single scene?

If you notice that chapters were missed, cancel the preview, verify your heading styles in Word or Markdown, and re-upload. If the preview matches your Scrivener outline, click Confirm Import.

Novelcrafter will instantly populate your Plan and Write views with your complete, navigable chapter tree.

Part 3: Migrating Character Lore and Research into the Codex

The manuscript is only half of a novelist's project. The true challenge lies in Scrivener's Characters and Research folders.

In Scrivener, character profiles are typically free-form text documents or filled-out character template sheets. In Novelcrafter, characters live in the Codex—a relational knowledge base. Each Codex entry contains specific functional fields:

• Entry Name: The canonical name of the character, location, or item.
• Aliases: Nicknames, honorifics, titles, or first/last name variants. Whenever an alias appears in your prose, Novelcrafter highlights it and feeds that character's context to the AI.
• Tags: Categories such as Protagonist, Villain, House Stark, or Magic User.
• Short Description: A concise 1–2 sentence summary injected directly into AI system prompts.
• Detailed Description: The comprehensive backstory, physical description, personality quirks, and character arc notes.

There are two primary methods to migrate your lore without manual re-entry.

Method A: The Snippets + Workshop "Extract to Codex" Pipeline (Recommended)

This workflow is the fastest and most reliable way to convert dozens of Scrivener character sheets into structured Codex entries:

1. Export Character Files from Scrivener:
   • Select your Characters folder in Scrivener's Binder.
   • Go to File > Export > Files... and export all character sheets as plain text or Markdown files, or compile that single folder into one continuous document.
2. Create a Snippet in Novelcrafter:
   • In Novelcrafter's left sidebar, click Snippets (the repository for scratchpads, research clippings, and raw reference materials).
   • Create a new snippet titled Imported Character Dossiers and paste your Scrivener character text into it.
3. Use Workshop Chat to Structure the Data:
   • Open the Workshop Chat in Novelcrafter.
   • Reference your snippet by typing @Imported Character Dossiers.
   • Submit the following prompt to your preferred model (e.g., Claude 3.5 Sonnet):

     "Please review the raw character notes in my referenced snippet. Reformat every character into a clean, structured entry following this exact pattern:

     Name: [Canonical Full Name]
     Aliases: [Comma-separated nicknames, titles, or variants]
     Tags: [Character archetype or faction]
     Short Description: [1-2 sentences capturing core identity and motivation]
     Details: [Physical description, key background, relationships]"

4. Execute One-Click Extraction:
   • When the AI outputs the structured list, hover over the response or click the action icon at the bottom of the chat message.
   • Select Extract to Codex.
   • Novelcrafter will parse the output, let you confirm the entity types (Characters, Locations, Lore), and generate all Codex cards automatically.

Method B: Entity Extraction from Imported Prose

If your Scrivener character files are disorganized or missing, you can let Novelcrafter extract lore directly from your newly imported manuscript:

1. Open Novelcrafter's Codex panel in the left sidebar.
2. Select the extraction tool to scan your manuscript text.
3. The AI scans your chapters, identifies recurring entity names (characters, recurring locations, distinctive weapons, magical artifacts), and generates suggested Codex entries.
4. You can accept suggestions with a single click and supplement them with Scrivener notes as you write.

Part 4: Post-Migration Optimization and Best Practices

Once your manuscript structure and Codex entries are populated, complete these four configuration steps to ensure your project runs smoothly:

1. Populate Aliases for Automatic Mention Tracking

Novelcrafter's standout feature is its real-time mention tracking. For this to work effectively:

• Open each major character card in the Codex.
• Ensure all realistic prose references are listed under Aliases. For instance, for Lord Edward of Winterfell, add Edward, Ned, Lord Edward, and The Warden.
• As you type in the Write view, Novelcrafter highlights these names automatically.

2. Respect the Token Budget: Short vs. Detailed Descriptions

A common beginner mistake is pasting an entire 5,000-word Scrivener character bio into the prompt context. This wastes context window tokens and degrades AI output quality.

• Place a distilled 20–40 word summary into the Short Description field. This summary is what Novelcrafter automatically includes when the character is mentioned in a scene.
• Place the full psychological breakdown, family tree, and character arc inside the main text body of the Codex entry. You can selectively reference this deeper lore during brainstorming sessions in the Workshop Chat.

3. Series Codex vs. Standalone Novel Codex

If your Scrivener project was part of an ongoing multi-book fantasy or sci-fi series:

• Novelcrafter supports Series Codexes.
• Rather than locking worldbuilding into one book, create a Series project and attach the Codex to it.
• When you create subsequent books in Novelcrafter, they automatically share the same characters, locations, and lore without needing another import.

4. Round-Tripping: Can You Go Back to Scrivener?

Some authors prefer to draft and brainstorm with AI in Novelcrafter, but return to Scrivener for final proofreading or offline archiving. Novelcrafter fully supports this round-trip:

1. In Novelcrafter, click Export at the bottom of the sidebar.
2. Export your prose as Markdown (.md) or Word (.docx), ensuring chapter headings are toggled on.
3. In Scrivener, create a target folder in your Binder, go to File > Import > Import and Split..., and select the file. Scrivener will split the document at each heading, restoring your Binder structure completely.

Summary Checklist

By separating the linear manuscript compile from the relational story bible ingestion, you can transition a multi-year Scrivener project into Novelcrafter in under an hour—preserving every branch of your binder tree while unlocking a modern AI-assisted fiction workflow.

References

• Need Help? - Novelcrafter Help
• The Codex Story Bible & World Builder - Novelcrafter
• Features - Novelcrafter
• Getting Started - Novelcrafter Help
• Documentation - Novelcrafter Help
• Why I love the Codex - Novelcrafter Blog
• Learn & Support - Literature & Latte