Skip to main content
Version: 0.9.x

Setting Up Migration

Version control your database schema with migrations written in SeaQuery or SQL.

Migration Table

A table named seaql_migrations will be created in your database to keep track of the applied migrations. It will be created automatically when you run the migration.

Creating Migration Directory

First, install sea-orm-cli with cargo.

$ cargo install sea-orm-cli

Then, setup the migration directory by executing sea-orm-cli migrate init.

# Setup the migration directory in `./migration`
$ sea-orm-cli migrate init
Initializing migration directory...
Creating file `./migration/src/`
Creating file `./migration/src/`
Creating file `./migration/src/`
Creating file `./migration/Cargo.toml`
Creating file `./migration/`

# If you want to setup the migration directory in else where
$ sea-orm-cli migrate init -d ./other/migration/dir

You should have a migration directory with a structure like below.

├── Cargo.toml
└── src
├── # Migrator API, for integration
├── # A sample migration file
└── # Migrator CLI, for running manually

Workspace Structure

It is recommended to structure your cargo workspace as follows to share SeaORM entities between the app crate and the migration crate. Checkout the integration examples for demonstration.

Migration Crate

Import the sea-orm-migration and async-std crate.

async-std = { version = "^1", features = ["attributes", "tokio1"] }

version = "^0"
features = [
# Enable at least one `ASYNC_RUNTIME` and `DATABASE_DRIVER` feature if you want to run migration via CLI.
# View the list of supported features at
# e.g.
# "runtime-tokio-rustls", # `ASYNC_RUNTIME` feature
# "sqlx-postgres", # `DATABASE_DRIVER` feature

Let's write a migration. Detailed instructions in the next section.

use sea_orm_migration::prelude::*;

pub struct Migration;

impl MigrationTrait for Migration {
async fn up(&self, manager: &SchemaManager) -> Result<(), DbErr> {
// Replace the sample below with your own migration scripts

async fn down(&self, manager: &SchemaManager) -> Result<(), DbErr> {
// Replace the sample below with your own migration scripts

Entity Crate

Create an entity crate in your root workspace.

You don't have SeaORM entities defined?

You can create an entity crate without any entity files. Then, write the migration and run it to create tables in the database. Finally, generate SeaORM entities with sea-orm-cli and output the entity files to entity/src/entities folder.

After generating the entity files, you can re-export the generated entities by adding following lines in entity/src/

mod entities;
pub use entities::*;
├── Cargo.toml # Include SeaORM dependency
└── src
├── # Re-export SeaORM and entities
└── # Define the `post` entity

Specify SeaORM dependency.

sea-orm = { version = "^0" }

App Crate

This is where the application logic goes.

Create a workspace that contains app, entity and migration crates and import the entity crate into the app crate.

If we want to bundle the migration utility as part of your app, you'd also want to import the migration crate.

members = [".", "entity", "migration"]

entity = { path = "entity" }
migration = { path = "migration" } # depends on your needs

version = "^0"
features = [ ... ]

In your app, you can then run the migrator on startup.

use migration::{Migrator, MigratorTrait};

let connection = sea_orm::Database::connect(&database_url).await?;
Migrator::up(&connection, None).await?;