---
title: Imports
category: Imports
tags: imports, json, structure, setup, migration
contextKey: imports.overview
micro: Bring prepared project structure into PlotDirector.
quickTitle: What are Imports?
quickSummary: Imports let you bring prepared story structure into PlotDirector so books, chapters, scenes and related items can be created together.
screenshot:
---

# Overview

Imports allow you to bring prepared story structure into PlotDirector instead of entering every project, book, chapter and scene by hand. This is useful when you have planned elsewhere, generated a structured outline, or need to move a project from another format into the app.

The import page is intentionally practical. You can upload or paste a JSON package, preview the result, run checks, and then create a new project when the package looks safe. The goal is to reduce setup friction while still protecting your data from accidental messy imports.

Imports are best for structure and known planning information. They are not a replacement for revision judgement. After importing, you should still review the project as a writer.

# When Should I Use This?

Use imports when you already have a structured outline or data package. This might include books, chapters, scenes, characters, locations, plot lines, story assets, scene links or other supported planning details.

Imports are also useful for testing a large project shape quickly. A dry run can show whether the package is valid before anything is saved.

Do not use imports for small changes to an existing project if normal editing is simpler. The import flow is designed for bringing in a prepared package, not for everyday scene editing.

# How To Use It

Upload a JSON file or paste the package into the text area. Use validation and preview before importing. Read any warnings carefully. Warnings may not block the import, but they often point to names, aliases or links that deserve attention.

Use dry run when you want to check mapping and structure without saving data. If a duplicate project title is found, the importer can rename the new project so existing work is not overwritten.

After a successful import, open the created project and review the books, chapters, scenes, characters and related records.

# Example

You may have an outline with three books, thirty chapters and two hundred scenes. Entering that manually would be slow. An import package can create the structure, then you can use PlotDirector to refine scene summaries, metrics, relationships, locations and continuity.

# Writer Tip

Preview before committing. The most useful import is not the fastest one; it is the one that gives you a clean starting structure you trust.

# Common Mistakes

- Importing without checking whether scene order and chapter order are correct.
- Treating warnings as meaningless because the import can still continue.
- Expecting imports to solve story quality rather than structure setup.
- Re-importing the same material instead of editing the created project.

# Related Guides

- [Books](/Help/Article/books.overview)
- [Chapters](/Help/Article/chapters.overview)
- [Scenes](/Help/Article/scenes.overview)
- [Characters](/Help/Article/characters.overview)
