Manage Projects

Projects are the top-level unit of work in DBModeler. A project contains the diagram, engine configuration, versions, integration settings, and optional custom SQL scripts.

Project list overview

The project list is the entry point when no project is currently open.

From this view you can:

• create a project
• filter the list by name, description, or engine
• open a project
• duplicate a project
• delete a project

Projects also show metadata such as the database engine, storage badge, and last updated timestamp.

Create a project

Use the create dialog to define the initial setup.

Required setup

• project name
• database engine

Common optional setup

• description
• default schema
• table engine, when supported by the engine
• default ID type and generation strategy

Choose the engine carefully. It drives type suggestions, export behavior, and engine-specific validation.

Open a project

Selecting Open loads the project into the editor.

If the project is a cloud-backed stub, DBModeler hydrates it from the connected provider before activation.

Deep links also work through the client-side project route format:

/p/<projectId>

If the route points to a valid local project, the app opens that project directly.

Duplicate a project

Use duplication when you want a safe copy before making large schema changes.

The duplicate flow gives the new project its own identity and keeps the original intact. This is useful for branch-like experimentation even though formal versioning stays linear inside each project.

Move a project to cloud storage

DBModeler can move a browser-stored project into a supported cloud provider.

Use this when you want:

• a provider-backed project file
• sync behavior across browser sessions
• conflict detection and merge handling

The move flow creates a cloud document for the project. It is not a merge into an existing remote project file.

Delete a project

Deleting removes the persisted project from browser storage.

Use duplication or versioning before deletion if you need a recovery point. Deletion is intended to be final from the UI point of view.

Recommended workflow

For most teams and solo users, the safest order is:

1. create the project with the correct engine
2. model the first schema version
3. create a version checkpoint
4. duplicate before risky restructuring
5. move to cloud or connect Git when the base workflow is stable

Next: Create Tables and Fields