Database Migration Guardian
Inspect migration risk before applying it.
Investigate database changes and test migrations in the supported local environment.
Inspect migration risk before applying it.
Before changing the structure or content of a supported database.
Database changes can affect existing data in ways a schema diagram does not show. Migration checks make the intended change and supported safeguards explicit.
Select a supported local SQLite database, inspect the proposed SQL and test using the controlled workflow before a deliberate application.
How to get started.
From your first choice to the result. Here is how to use this feature in your own project.
- 01
Select the database and inspect its available structure and relationships.
- 02
Prepare the migration and use available test and backup steps.
- 03
Review results and recovery options before applying the real change.
How it could work for you.
Check a new column and whether existing rows remain usable.
How to assess the result
Current migration checks are not a universal guarantee for every database engine or production deployment.
Where to find it.
Top bar → Tools → Database Migration Guardian
Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.What is saved?
Migration checks, available schema information and supporting evidence are saved with the project.
What you need to know
Built-in migration tests target local SQLite databases. They do not universally protect every database or externally executed SQL command.