How to Move Your Manuscript From Scrivener or Word Into a New Writing App Without Losing Your Work

The easiest way to move your Scrivener or Word manuscript into a new app and format it for print depends on where it is going. Storyloft accepts .scriv projects, Atticus files and .docx files as direct uploads, so you can skip the export step there. For apps that only take Word files, compile or export a single, clean .docx file, standardize chapter titles with real Heading 1 styles, mark scene breaks consistently, and then import and verify the result against a short post-import checklist.

Over months or years of drafting, your workspace fills up with character notes, discarded prologues, and files named Novel_Final_REALLY_Final.docx. Moving a full-length book out of that environment into a new platform can feel like packing up a chaotic house. You want to make sure your italics survive the trip, your footnotes stay attached to the right sentences, and your chapter breaks do not vanish into a wall of solid text.

Whether you are exploring alternatives to Scrivener by author workflow or upgrading from a basic word processor, the bridge between your old draft and your new app is a well-prepared Microsoft Word file. Modern book writing and formatting software relies on the structural tags hidden inside a .docx file to understand where your scenes end and your front matter begins.

This step-by-step guide covers exactly how to export your work cleanly, strip out the manual formatting that confuses import engines, and verify that every word arrived safely on the other side.

Before You Start: Back Up and Freeze Edits

Before exporting or modifying styles in your manuscript, establish a clean cutoff point so you never lose work or confuse versions. Working in two apps at once creates drifting drafts where late corrections inevitably get lost.

First, create a dated backup copy of your entire project. In Scrivener, projects are essentially folders containing multiple sub-files and metadata. In addition to Scrivener’s automatic backups, you can export your entire Binder folder structure via File > Export > Files to save a copy of all folders, subfolders, and images on your drive. In Microsoft Word or Google Docs, save a read-only archive copy with a clear date stamp (such as BookTitle_Archive_2026-11-15.docx) before you begin cleaning up styles.

Next, create a separate migration working file. Perform all your style cleanup, Track Changes resolution, and comment removal in this duplicate file so your original working notes remain untouched.

Finally, freeze your edits. Stop drafting or revising in the old app once you generate your migration file. Before closing the old app, write down your exact chapter count and total manuscript word count. You will need these baseline numbers to verify that every scene arrived safely after importing.

Moving Into Storyloft

Storyloft accepts .scriv, Atticus and .docx uploads directly, so there is no compile or export step if you are coming from Scrivener, Atticus or Word. Upload the file and Storyloft rebuilds your manuscript as organized chapters. If you are uploading a Word file, real Heading 1 styles on your chapter titles help chapter detection, and the verification checklist below still applies, so compare your chapter count and word count against the baseline numbers you wrote down. For a shorter walkthrough, see our guide to moving a Scrivener or Atticus project into Storyloft.

Once your book is in, Storyloft tracks and organizes your chapters. When you are writing fiction, its World Builder parses your lore as you write, so you can track consistency and plot more closely. Read more about book writing software built around your whole manuscript.

Moving From Scrivener

Scrivener stores projects as separate files and folders inside a Binder, so many apps cannot open a .scriv project at all and need those pieces stitched together into a standard format first. Storyloft accepts .scriv uploads directly. If you are moving to an app that only takes Word files, compile to .docx using the steps below.

Compile to DOCX

Compiling is the main route out of Scrivener. As documented in Literature & Latte’s tutorial on compiling for Word, the Compile function stitches together all the files in your Draft or Manuscript folder from top to bottom into a single linear .docx file.

To compile your draft, open File > Compile to view the Compile Overview screen. At the top of the Compile window, set the “Compile for:” dropdown menu to Microsoft Word (.docx). In the left Formats sidebar, select a clean manuscript format such as Default or Manuscript (Times). In the right-hand Contents tab, verify that the dropdown is set to your full Draft or Manuscript folder and that the checkboxes next to every chapter and scene you want to move are ticked.

What to Do About Folders and Section Layouts

Whether your Binder uses single files for chapters or folders containing multiple scene files, Scrivener maps those items to Section Types and formats them using Section Layouts. To ensure your new app recognizes your chapters, click “Assign Section Layouts…” at the bottom of the center column in the Compile Overview screen. Assign a layout that outputs your folder titles or text titles as clearly marked headings.

If you have non-manuscript folders in your Binder (such as character sheets, research folders, and worldbuilding notes) that sit outside the Draft folder, Compile will not include them. To bring those out of Scrivener, select the folders in the Binder and choose File > Export > Files (Literature & Latte). Scrivener will reproduce the exact file and folder structure of the Binder on your hard drive.

Scene Breaks and Separators

When a chapter folder contains multiple scene documents, Scrivener inserts a separator between consecutive text files during Compile. Standard Manuscript compile formats typically insert a # character between scene files, while other formats insert an empty line.

If you want to customize the separator (for example, to *** or #), right-click your chosen format in the Compile sidebar, select “Duplicate & Edit Format”, and check the Separators tab (Literature & Latte). To keep the Word output clean and avoid unwanted Word Section Breaks, use the Default format or disable different headers and footers in your compile settings.

Footnotes, Comments, and Inline Annotations

Footnotes and Inspector comments require specific handling. Scrivener compiles footnotes and endnotes into genuine Word footnotes in your .docx file, which modern formatting apps will recognize and preserve.

Comments and inline annotations should usually be stripped out before importing so revision reminders do not accidentally merge into your book prose. In the right-hand side of the Compile window under the Options settings, Scrivener provides “Remove comments” and “Remove annotations” checkboxes. Tick both of these when compiling the clean .docx that you plan to import.

Snapshots

Snapshots are saved earlier states of individual Binder documents taken before major edits. Snapshots do not compile into a .docx file. When you use File > Export > Files, the Export dialog contains a Metadata tab where you can choose to save notes, metadata, and snapshots alongside your exported files.

Moving From Microsoft Word

Most import issues from Microsoft Word happen because a manuscript looks visually structured to a human reader while lacking the correct structural styles underneath.

Use Heading Styles

Typing a chapter title in 18-point bold font while leaving the paragraph style set to “Normal” causes book importers to treat the chapter title as regular body text. You must apply Word’s official Heading 1 style to every chapter and section title.

Select each chapter title (for example, “Chapter 1: The Glass Garden”) and apply Word’s Heading 1 style from the Style Gallery on the Home tab. Also apply Heading 1 to front and back matter titles such as Prologue, Epilogue, Dedication, and Acknowledgments. For nonfiction sections or chapter subtitles, apply Heading 2 rather than Heading 1, so the importer does not split a subsection into a completely new chapter.

Verify your structure by opening the View tab and checking the Navigation Pane box. Every Heading 1 and Heading 2 in your manuscript will appear in a clean sidebar list. If a line of dialogue appears in the Navigation Pane, it was accidentally given a heading style and should be switched back to Normal.

Remove Manual Formatting

Unresolved tracked changes and margin comments can cause deleted words to import as active prose. Accept or reject all changes and delete comments in your migration copy before saving.

Do not indent paragraphs by pressing the Tab key or typing five spaces. In ebook and print formatters, hard tabs convert into fixed wide gaps that conflict with automatic first-line paragraph indentation. Use Find and Replace (^t in Word) to strip leading tabs out of your file.

Similarly, remove stacked empty paragraph returns. Pressing Enter five times to push a chapter onto a new page creates empty paragraphs that turn into blank gaps on e-readers. Let your target app break chapters automatically based on your Heading 1 styles.

Scene Break Markers

Blank lines alone are easy for importers to strip or misread. Place three asterisks (***) or a pound sign (#) centered on its own line between scenes to guarantee your new app recognizes the break.

Moving From Google Docs

Google Docs uses a web-based document model, so exporting cleanly requires a quick check of your document settings before downloading.

Pages Mode and Document Outline

Google Docs supports a “Pageless” view that disables page breaks. If you use Insert > Break > Page break, make sure the document is set to standard Pages mode.

Open the left-hand Document Outline in Google Docs to confirm every chapter title is styled as Heading 1 and subheads are styled as Heading 2.

Cleanup and Download

Switch your document from Suggesting mode to Editing mode and accept or reject all pending suggestions. If you leave suggested deletions active, they may export inside the text of the .docx file.

If you have pasted text into Google Docs from emails or web notes, you may have soft line breaks (Shift+Enter) instead of true paragraph breaks (Enter). These can cause issues in formatting tools, so replace them with standard returns.

Finally, choose File > Download > Microsoft Word (.docx). Do not copy and paste a full-length book from a browser tab into a new app, as browser clipboards frequently drop footnote links and introduce messy inline HTML.

What Usually Breaks and How to Spot It

Even with careful preparation, minor formatting quirks can slip through. Here is what usually breaks during a manuscript migration and how to spot it immediately.

Merged chapters or missing chapter breaks: This happens when chapter titles in Word or Google Docs were styled as bold Normal text instead of Heading 1, or when Scrivener’s Section Layouts did not include folder titles. Check the chapter navigation sidebar immediately after import. If two chapters merged into one, apply Heading 1 in the source file and re-import.

Extra phantom chapters: A pull quote, an emphasized dialogue line, or a manual Table of Contents had Heading 1 applied in Word. Scan your new chapter list for strange titles or empty sections.

Vanished scene breaks: Scene breaks were marked only with a single blank line instead of *** or #. Visually scan multi-scene chapters to verify your scene spacing remained intact.

Double indents on first paragraphs: The author typed manual Tab characters at the start of every paragraph in Word, which then stacked on top of the new app’s automatic first-line paragraph indent. Look at the opening lines of Chapter 1. Strip manual tabs from the source file if you see a massive indent.

Broken line wraps: Text pasted from PDFs or old editors often contains hard line breaks at the end of every line. Some writing platforms require you to fix this manually. Conversely, automatic book formatting software that translates chapter hierarchies can handle this for you. Storyloft accepts .docx, .scriv and Atticus uploads and converts imported material into clean chapters, sections, paragraphs, quotations, notes, and front matter.

Post-Import Verification Checklist

Before you archive your old writing app and begin drafting your next chapter, run through this six-point verification checklist.

  1. Chapter Count and Order: Compare the chapter outline in your new app against your original Binder or Word Navigation Pane. Confirm that Front Matter, all numbered chapters, and Back Matter are in the correct order.

  2. Total Word Count: Check the total manuscript word count against your pre-migration baseline. Small differences of a few dozen words are normal if you stripped out inline comments. A discrepancy of 1,000 words or more means a scene file was left unchecked in Scrivener’s Compile list.

  3. Scene Breaks: Check at least three chapters that contain multiple scenes to confirm your scene break markers (*** or #) rendered cleanly.

  4. Italics and First Paragraphs: Open a chapter from the beginning, middle, and end of the book. Verify that italics carried over and that the first paragraph after each chapter heading is flush left without a double tab indent.

  5. Footnotes and Endnotes: Click several footnote anchors in the body text to confirm they link to the correct note text and that the numbering remains sequential.

  6. Embedded Images: If your manuscript includes maps or chapter ornaments, switch to your new app’s print preview to verify that images imported at high resolution and constrain properly to the page margins.

How to Keep Your Old Files as a Safety Net

Migrating to a new writing platform does not mean you have to delete your history. Keep a secure safety net by creating a folder named Archive_PreMigration in your local storage and cloud backup. Store your native .scriv project folder and the clean compiled .docx file inside it.

Rename your old Word document or Google Doc with ARCHIVED_DO_NOT_EDIT at the start of the filename. This ensures you never accidentally open the file six weeks later and type new scenes into an outdated draft.

Immediately after verifying your import in your new app, save a named version or baseline snapshot. If your new platform supports version control, labeling this snapshot as “Clean Import Baseline” gives you a permanent, safe restore point before you begin editing.

Frequently Asked Questions (FAQ)

What is replacing Scrivener for indie authors?

No single tool is replacing Scrivener for every writer; instead, indie authors are moving to modern cloud workspaces that match how they publish. While Scrivener pioneered the Binder and Corkboard for organizing long projects, indie authors are switching to alternatives that offer built-in formatting, AI assistance, or real-time cloud sync without a steep learning curve.

Authors are moving to platforms like Storyloft for a unified writing, editing, illustration, and publishing workspace. Storyloft combines a long-form manuscript editor, manuscript-aware AI, illustration generation, and live print PDF and EPUB formatting in one platform. Storyloft pricing is $39 per month, $398 per year, or $399 for lifetime access (view Storyloft pricing for full details). Other authors choose Atticus for standalone cross-platform formatting, Reedsy Studio for browser collaboration, or Dabble for simple cloud-synced plotting.

Can I import a .scriv folder directly into another writing app?

It depends on the app. Storyloft accepts .scriv projects, Atticus files and .docx files as direct uploads. Many other writing and formatting apps, such as Atticus, Reedsy Studio, and Dabble, import DOCX files, so for those you compile your Scrivener project to a .docx first. Compiling to a clean .docx remains the most predictable method if you are not sure what your next app accepts.

What happens to my Scrivener research folders and character notes when I compile?

Scrivener’s File > Compile only stitches together documents inside the Draft or Manuscript folder. To bring research folders, character sheets, and notes out of Scrivener, you must select your Research folder in the Binder and choose File > Export > Files. This action saves all folders, text files, and images directly to your computer.

Will my italics, bold text, and footnotes survive a DOCX migration?

Yes. When you export or save as .docx rather than plain text (.txt), character-level formatting like italics and bold text carry over into modern book apps. Word footnote and endnote anchors are also preserved, ensuring your citations remain linked to the correct passages in the text.

Why did my chapters merge into one giant chapter after importing?

Chapters merge when chapter titles in your Word or Google Docs file were formatted manually by making normal text bigger and bolder, instead of applying the actual Heading 1 paragraph style. Book importers rely on Heading 1 tags to know where to split the file. Apply Heading 1 to every chapter title in your source document and re-import.

Once I move my manuscript into Storyloft, do I need a separate app to format for print?

Storyloft formats your book for print and ebook inside the same workspace where you write and edit. You do not need a secondary formatting tool. The platform includes five standard KDP and IngramSpark trim size presets (including 5.5 x 8.5″ Digest and 6 x 9″ Trade) plus custom sizes. It automatically handles recto and verso mirrored margins, running headers, drop caps, and direct export to print-ready PDF and EPUB 3, allowing for a direct comparison between Scrivener’s binder workflow and a modern platform that manages the entire production cycle.

Leave a Reply

Your email address will not be published. Required fields are marked *