Revisions & Migrations

Version and evolve your schema

Relmic automatically tracks every change to your schema. Browse your revision history, create milestones for important versions, branch off with drafts, and generate migration scripts to safely evolve production databases.

Auto-save and revision history

Every time you make a change — adding a table, modifying a column, creating a relationship — Relmic saves a new revision automatically. You never need to manually save your work.

Open the Revisions panel to see your full history. Each revision shows a timestamp and a summary of what changed. Click any revision to preview the schema as it was at that point in time.

Free plans include 1 revision (current state only). Pro and above include unlimited revision history. View plans.

Milestones

Milestones are named snapshots of your schema at a specific point in time. Use them to mark important versions — for example, “v1.0 launch”, “after adding auth tables”, or “pre-migration”.

Creating a milestone

  1. Open the Revisions panel.
  2. Click Create Milestone.
  3. Give it a descriptive name.
  4. The milestone appears pinned in your revision timeline for easy access.

Drafts

Drafts let you experiment with schema changes without affecting the main revision timeline. Think of them as lightweight branches for your schema design.

How drafts work

  1. Create a draft from any revision or milestone.
  2. Make changes freely — the draft has its own isolated revision history.
  3. When satisfied, promote the draft to the main timeline.
  4. Or discard it if the experiment did not work out.

Drafts are useful for trying out alternative table structures, testing normalization strategies, or planning a migration before committing to it.

Visual diff

Relmic can compare any two revisions side by side and highlight the differences. The visual diff shows:

  • Added tables — highlighted in green
  • Removed tables — highlighted in red
  • Modified tables — highlighted in yellow, with a detailed breakdown of column changes
  • Added and removed relationships — connection lines color-coded by change type

This makes it easy to review schema changes before generating migration scripts, or to understand what changed between two milestones.

Migration script generation

Once you have identified the changes between two revisions using the visual diff, Relmic can generate the corresponding ALTER statements to migrate your database from one version to another.

How to generate migrations

  1. Open the Revisions panel.
  2. Select two revisions to compare (a “from” and “to” revision).
  3. Click Generate Migration.
  4. Relmic produces the SQL statements needed to transform the database.

Supported migration statements

  • ALTER TABLE ... ADD COLUMN
  • ALTER TABLE ... DROP COLUMN
  • ALTER TABLE ... ALTER COLUMN (type changes, default values)
  • ALTER TABLE ... ADD CONSTRAINT
  • CREATE TABLE (for new tables)
  • DROP TABLE (for removed tables)

Recommended workflow

Here is a typical workflow for evolving a production database with Relmic:

  1. Create a milestone for the current production schema.
  2. Create a draft to experiment with changes.
  3. Make changes in the draft — add tables, modify columns, adjust relationships.
  4. Use visual diff to review what changed.
  5. Generate migration scripts between the milestone and the draft.
  6. Review and test the migration SQL in a staging environment.
  7. Promote the draft to the main timeline and apply the migration to production.
PreviousReverse EngineeringNextCollaboration