Docs › Screenwriting › The old Script Studio: what still works, and how to move a project across
The old Script Studio: what still works, and how to move a project across
Last updated September 9, 2026 · 5 min read
In one line: the work you already have in Script Studio is still there and still finishable. New screenplays are
.scriptfiles in the Writing Studio. This page draws the line between the two, and says exactly what happens if you move a project across.

Where things stand
Three things are true at once:
Script Studio (existing projects)
- Still opens, still edits, with no deadline
- Cannot create new projects
- Its AI coach has been switched off
Writing Studio (new screenplays)
- A screenplay is a
.scriptfile in the file tree — one episode per file - Taiwanese and Hollywood layouts, and preview-as-export, are all here
- AI can edit scenes and elements directly
The notice inside the app says the same thing: finish what you started in Script Studio — we will see you through it rather than dropping you halfway.
You have two options
- Finish where you are. Nothing to do. The scene board, the character bible and the planning tabs all still work; the AI is the only part that is gone.
- Copy a version into the Writing Studio. On the shelf, open that book's ⋯ menu → Copy as new Writing Studio book.
Copying is not moving. The original stays in Script Studio, complete.
What comes across, and what does not
Comes across
- Every episode → one
.scriptfile (grouped into season folders if you used seasons) - Characters, locations and storylines → one
.mdfile each - Series and season planning fields (logline, concept, outline) →
.md - The shape of the whole thing → one
.beatsbeat board - Notes — they travel, but as book-level notes (the new book has no season or episode to anchor them to)
- Images and other media
Does not come across
- Version history — the new book starts from a single initial version
- Comments
- Beta Reader reports
- AI conversations
A media file that is neither stored on this device nor reachable in the cloud at that moment is skipped. You are told how many were skipped, and the files in the original book are untouched.
After the copy
- It is a snapshot, not a link. The two books go their own way; later edits in the old one do not follow.
- The old book stays where it is. It is not deleted and it does not become read-only.
- The new book gets a suffix on its name by default. You can change that before copying.
A different thing that looks similar: the legacy-format prompt
If opening an old screenplay shows "this screenplay uses the legacy format" and turns the whole book read-only, that is an older data format, and it has nothing to do with this migration.
Upgrade and create a copy produces a new Script Studio book (with -copy on the name) and keeps the original as a backup. Open the new one, check nothing is missing, and only then decide whether to delete the backup. Details in the legacy-format prompt.
Related
- Where your old screenplays are
- The file tree — where a new screenplay file is created
- Features that have been removed
Open the app and do this with your own book. Free to start, no credit card.