dFlow’s dashboard and data model now centre on Applications, Environments, and Services.

Legacy Projects are still part of the story until your organisation finishes moving. Mixed states are normal during rollout, not an edge case.

Start here

What we are not hiding

• Navigation differs between the Applications hub and the legacy Projects hub; teammates may need explicit links or bookmarks.
• Old project URLs redirect to an Application, not always to the same Service screen you used before.
• Bulk migration and follow-up data cleanup are real database operations on self-hosted installs; rollback is backup restore, not a magic undo.
• Some Services can sit in a transitional shape on disk until service ownership normalisation runs; operators have the details in the repo.

Orientation in the new docs

The sidebar follows IA.md in the docs package: Introduction and Core Concepts first, then Applications, Environments, Services, and the rest. How dFlow is structured under Core Concepts in the sidebar links into this migration section on purpose.

Related

• Welcome to dFlow: entry point with legacy note.
• Troubleshooting overview: when behaviour does not match expectations after a move.