Keep the Scrivener binder, or compile a copy WriteIDE can import.

Compile from Scrivener to Word, Markdown, or plain text. WriteIDE detects chapter and scene structure from headings and breaks, then lets you review the split.

Choose Track a story written elsewhere to keep the binder, corkboard, and compile system you already use. WriteIDE sits beside Scrivener as the continuity ledger.

Levels, HP, inventory, classes, skill charges, and quests are database records tied to scenes, not numbers you retype in a status document.

The imported copy is saved in WriteIDE’s local data. Importing does not upload the Scrivener project, and WriteIDE does not need an account.

Binder order, status labels, keywords, snapshots, and custom metadata do not come across. Only the compiled manuscript text can be imported.

WriteIDE has outline, board, and export tools of its own. It does not claim Scrivener compile depth, iOS, or a one-click binder takeover.

A later compile needs a separate import or manual update. WriteIDE 0.7.3 does not watch the .scriv package or merge later edits automatically.

Include the chapter headings you want WriteIDE to treat as structure. Binder labels alone are not enough.

Open the desktop app on the same computer that holds the compile.

Choose Bring a manuscript on the project library or in New Project if you want the prose in WriteIDE. Choose Track a story written elsewhere if you will keep drafting in Scrivener.

After reviewing the split, open your first imported scene. For tracker-only, establish the chapter baseline, record one change in Story Overview, then inspect the character at that scene. A tracker import with fewer than two detected chapters offers a skeleton.