# Your project migration checklist

An original NarrativeForge worksheet · RumblePoint LLC · October 14, 2026

Use a copy. Keep the original until every requirement you depend on has been checked.

## Before you move

- [ ] Save a separate, recoverable source-project backup.
- [ ] Save a reference PDF or rendered manuscript of the same revision.
- [ ] Check supported inputs for your NarrativeForge edition.
- [ ] List your must-keep content, formatting and production metadata.

Source application / version:
Destination edition / version:
Source revision / backup location:

## A representative sample

Choose a chapter or scene with the hardest details in the project.

- [ ] Titles, scene order and chapter boundaries
- [ ] Paragraphs, emphasis, dialogue and scene breaks
- [ ] Screenplay element types and character cues
- [ ] Notes, special characters and unusual names
- [ ] Revision marks, scene numbers and locked pages, if applicable
- [ ] Research and metadata that need separate handling

A compiled manuscript is not a complete Scrivener project backup. A PDF can help
with visual comparison but does not replace the structured source document.

## A real working session

- [ ] Make a small revision and return to it.
- [ ] Check the required export or delivery format, if supported.
- [ ] For audio, review speaker assignments and pronunciation on a short passage.
- [ ] Record differences and decide which are acceptable.
- [ ] Keep the existing production workflow for unresolved requirements.

Observed difference | Acceptable? | Follow-up
--- | --- | ---
 | | 

## Ready for the full project?

Expand only after the sample meets your requirements. Repeat the review across the
complete work, keep the original, and maintain a recoverable backup.

Compatibility: https://www.narrativeforge.ai/compatibility
Help: https://www.narrativeforge.ai/support