Complete Migration Guide for the New Version
If you're already using Flova 1.0, this guide will help you quickly migrate to Flova 1.5.
1. Before you upgrade
- The original project is not overwritten. Importing creates a new project; importing again creates another copy. Later changes in the old version do not automatically sync to imported projects.
- Migration continues in the background. Closing the progress panel or working on another project does not interrupt it.
- If there is no eligible legacy data, Projects to migrate is empty. The homepage migration prompt appears only when eligible legacy data exists.
2. Import a legacy project
- Open Projects, then Projects to migrate, and click the source project card to start migration. The first import does not require confirming a project name.
- When importing the same project again, confirm Import project updates into the new version to create another copy. Check progress in the migration panel; you can close it while the task runs.
- When import is complete, select Open latest imported project and check the new copy.
3. Where to find your content
| Previously | In the new version |
|---|---|
| Storyboard, file area, characters, and shots | Find them by Groups and Sequences in List view; use its grid display to browse images, videos, and candidate resources |
| Freely arranged media | Compare side by side and organize relationships on Canvas |
| Generation descriptions and results | Inspect, edit, and compare in prompt drafts and resource previews |
| Timeline | Create one or more editing projects in Edits |
| Project chat and shared knowledge | Continue tasks in chat; put context needed across conversations in project documents or a Skill |
| Legacy Skill | The upgraded Skill folder, containing skill.md and reference documents |
4. Legacy Skills, old messages, and new conversations
- Legacy Skills need an upgrade. The new version supports multiple Skills in one project. Put reusable methods and boundaries in
skill.md; keep longer, task-specific material in reference documents. Other project content remains viewable during the upgrade, but the Agent temporarily cannot use the old Skill rules. Afterward, check them with a familiar task. - Old messages are for review. Earlier requirements, Prompts, and feedback remain viewable, but actions that depend on the old runtime state, such as returning to that moment or starting a new project from it, are unavailable.
- Start a new conversation to continue. A project can have several independent conversations. A new conversation does not inherit temporary chat history from others. Reference the media or documents you need, and keep long-term shared information in project documents or a Skill.