When should I use Alembic instead of South?

Managing SQLAlchemy database schema migrations with version-controlled upgrade and downgrade scripts. Production database migration workflows where rollback paths are a hard requirement. Teams using SQLAlchemy who need a first-class, battle-tested migration companion

When should I use South instead of Alembic?

Historical Django schema migrations for codebases running Django 1.6 or earlier. Maintaining very legacy Django projects that have not been upgraded in over a decade. Understanding Django migration history — South directly inspired the built-in migrations system

What are the main weaknesses of Alembic?

Tightly coupled to SQLAlchemy — not usable without it as the underlying ORM. Auto-generated migrations need manual review and often miss intent-level changes like renames. Merge conflicts in migration chains require careful manual resolution to avoid broken history

What are the main weaknesses of South?

Completely obsolete — Django's built-in migrations superseded South in Django 1.7 (2014). Not compatible with Django 2.x or any later version. No active maintenance or security updates; should be removed from any active codebase

Alembic vs South: Key Differences for Python Data Engineering

Database Migration Tools

Alembic

Database Migrations for SQLAlchemy

★ 4.7

MIT

pip install alembic

South

Legacy Django Migrations

★ 4.0

Apache-2.0

pip install South

Side-by-Side Comparison

Alembic

South

Alembic

South

Best For

✓Managing SQLAlchemy database schema migrations with version-controlled upgrade and downgrade scripts
✓Production database migration workflows where rollback paths are a hard requirement
✓Teams using SQLAlchemy who need a first-class, battle-tested migration companion

✓Historical Django schema migrations for codebases running Django 1.6 or earlier
✓Maintaining very legacy Django projects that have not been upgraded in over a decade
✓Understanding Django migration history — South directly inspired the built-in migrations system

Best For

✓Managing SQLAlchemy database schema migrations with version-controlled upgrade and downgrade scripts
✓Production database migration workflows where rollback paths are a hard requirement
✓Teams using SQLAlchemy who need a first-class, battle-tested migration companion

✓Historical Django schema migrations for codebases running Django 1.6 or earlier
✓Maintaining very legacy Django projects that have not been upgraded in over a decade
✓Understanding Django migration history — South directly inspired the built-in migrations system

Weaknesses

•Tightly coupled to SQLAlchemy — not usable without it as the underlying ORM
•Auto-generated migrations need manual review and often miss intent-level changes like renames
•Merge conflicts in migration chains require careful manual resolution to avoid broken history

•Completely obsolete — Django's built-in migrations superseded South in Django 1.7 (2014)
•Not compatible with Django 2.x or any later version
•No active maintenance or security updates; should be removed from any active codebase

Weaknesses

•Tightly coupled to SQLAlchemy — not usable without it as the underlying ORM
•Auto-generated migrations need manual review and often miss intent-level changes like renames
•Merge conflicts in migration chains require careful manual resolution to avoid broken history

•Completely obsolete — Django's built-in migrations superseded South in Django 1.7 (2014)
•Not compatible with Django 2.x or any later version
•No active maintenance or security updates; should be removed from any active codebase

License

MIT

Apache-2.0

License

MIT

Apache-2.0

Install

pip install alembic

pip install South

Install

pip install alembic

pip install South

Rating

★ 4.7

★ 4.0

Rating

★ 4.7

★ 4.0

Key Features

Alembic

1Auto-generates migration scripts by diffing SQLAlchemy models vs. database
2Supports upgrade and downgrade paths for schema rollback
3Branch and merge support for parallel development workflows
4Runs raw SQL in migrations for operations beyond ORM capabilities
5Integrates with CI/CD pipelines for automated schema deployment

South

1Pre-Django-1.7 migration framework providing schema and data migrations
2Supports forward and backward migration for rollback capability
3Auto-detection of model changes to generate migration files
4Data migrations to transform existing rows during schema changes
5Still works in Django 1.6 and older projects requiring long-term maintenance

How Python Data Engineers Use These Tools

Alembic

Alembic is the standard migration tool for SQLAlchemy-based Python projects. Engineers run `alembic revision --autogenerate` to create a migration script from model changes, review and edit the script, then apply it with `alembic upgrade head`. This ensures database schema changes are versioned, reviewed, and applied consistently across dev, staging, and production.

South

Engineers maintaining legacy Django projects running Django 1.6 or earlier use South to manage schema evolution. New projects should use Django's built-in migrations instead. For teams upgrading legacy codebases, South migrations can be converted to Django native migrations using the `manage.py migrate --run-syncdb` workflow.

More Database Migration Tools Comparisons

Database Migration Tools

Alembic vs Flyway

Database Migration Tools

Alembic vs Django Migrations

Database Migration Tools

Alembic vs Flask-Migrate

Database Migration Tools

Alembic vs yoyo-migrations

Database Migration Tools

Alembic vs SQLAlchemy-Migrate

Database Migration Tools

Django Migrations vs Flyway

Individual Tool Pages

View Alembic details →View South details →

Side-by-Side Comparison

Alembic

South

Alembic

South

Best For

✓Managing SQLAlchemy database schema migrations with version-controlled upgrade and downgrade scripts
✓Production database migration workflows where rollback paths are a hard requirement
✓Teams using SQLAlchemy who need a first-class, battle-tested migration companion

✓Historical Django schema migrations for codebases running Django 1.6 or earlier
✓Maintaining very legacy Django projects that have not been upgraded in over a decade
✓Understanding Django migration history — South directly inspired the built-in migrations system

Best For

✓Managing SQLAlchemy database schema migrations with version-controlled upgrade and downgrade scripts
✓Production database migration workflows where rollback paths are a hard requirement
✓Teams using SQLAlchemy who need a first-class, battle-tested migration companion

✓Historical Django schema migrations for codebases running Django 1.6 or earlier
✓Maintaining very legacy Django projects that have not been upgraded in over a decade
✓Understanding Django migration history — South directly inspired the built-in migrations system

Weaknesses

•Tightly coupled to SQLAlchemy — not usable without it as the underlying ORM
•Auto-generated migrations need manual review and often miss intent-level changes like renames
•Merge conflicts in migration chains require careful manual resolution to avoid broken history

•Completely obsolete — Django's built-in migrations superseded South in Django 1.7 (2014)
•Not compatible with Django 2.x or any later version
•No active maintenance or security updates; should be removed from any active codebase

Weaknesses

•Tightly coupled to SQLAlchemy — not usable without it as the underlying ORM
•Auto-generated migrations need manual review and often miss intent-level changes like renames
•Merge conflicts in migration chains require careful manual resolution to avoid broken history

•Completely obsolete — Django's built-in migrations superseded South in Django 1.7 (2014)
•Not compatible with Django 2.x or any later version
•No active maintenance or security updates; should be removed from any active codebase

License

MIT

Apache-2.0

License

MIT

Apache-2.0

Install

pip install alembic

pip install South

Install

pip install alembic

pip install South

Rating

★ 4.7

★ 4.0

Rating

★ 4.7

★ 4.0

Key Features

Alembic

1Auto-generates migration scripts by diffing SQLAlchemy models vs. database
2Supports upgrade and downgrade paths for schema rollback
3Branch and merge support for parallel development workflows
4Runs raw SQL in migrations for operations beyond ORM capabilities
5Integrates with CI/CD pipelines for automated schema deployment

South

1Pre-Django-1.7 migration framework providing schema and data migrations
2Supports forward and backward migration for rollback capability
3Auto-detection of model changes to generate migration files
4Data migrations to transform existing rows during schema changes
5Still works in Django 1.6 and older projects requiring long-term maintenance

How Python Data Engineers Use These Tools