When should I use South instead of SQLAlchemy-Migrate?

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

When should I use SQLAlchemy-Migrate instead of South?

Maintaining legacy SQLAlchemy migration codebases that predate Alembic. Simple single-branch migration chains in older Python 2-era projects. Understanding historical SQLAlchemy migration patterns before Alembic became standard

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

What are the main weaknesses of SQLAlchemy-Migrate?

Officially deprecated — Alembic is the designated successor from the same author. No longer actively maintained; security and Python 3 compatibility issues may arise. Not recommended for any new project under any circumstances

South vs SQLAlchemy-Migrate: Key Differences for Python Data Engineering

Database Migration Tools

South

Legacy Django Migrations

★ 4.0

Apache-2.0

pip install South

SQLAlchemy-Migrate

Schema Versioning for SQLAlchemy

★ 4.2

MIT

pip install sqlalchemy-migrate

Side-by-Side Comparison

South

SQLAlchemy-Migrate

South

SQLAlchemy-Migrate

Best For

✓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

✓Maintaining legacy SQLAlchemy migration codebases that predate Alembic
✓Simple single-branch migration chains in older Python 2-era projects
✓Understanding historical SQLAlchemy migration patterns before Alembic became standard

Best For

✓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

✓Maintaining legacy SQLAlchemy migration codebases that predate Alembic
✓Simple single-branch migration chains in older Python 2-era projects
✓Understanding historical SQLAlchemy migration patterns before Alembic became standard

Weaknesses

•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

•Officially deprecated — Alembic is the designated successor from the same author
•No longer actively maintained; security and Python 3 compatibility issues may arise
•Not recommended for any new project under any circumstances

Weaknesses

•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

•Officially deprecated — Alembic is the designated successor from the same author
•No longer actively maintained; security and Python 3 compatibility issues may arise
•Not recommended for any new project under any circumstances

License

Apache-2.0

MIT

License

Apache-2.0

MIT

Install

pip install South

pip install sqlalchemy-migrate

Install

pip install South

pip install sqlalchemy-migrate

Rating

★ 4.0

★ 4.2

Rating

★ 4.0

★ 4.2

Key Features

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

SQLAlchemy-Migrate

1Version-controlled database schema migrations for SQLAlchemy-managed databases
2Change scripts written in Python using SQLAlchemy expressions
3Migration repository pattern tracking applied and unapplied schema versions
4Supports upgrade and downgrade operations for safe rollbacks
5Compatible with PostgreSQL, MySQL, SQLite, and Oracle databases

How Python Data Engineers Use These Tools

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.

SQLAlchemy-Migrate

Python data engineers use sqlalchemy-migrate to manage schema evolution for SQLAlchemy-backed operational databases and metadata stores in data platforms. Migration scripts written in Python allow schema changes to be version-controlled alongside application code. It is used in data engineering teams that manage their own PostgreSQL or MySQL databases for pipeline configuration, lineage metadata, and data catalogue storage.

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

Alembic vs South

Individual Tool Pages

View South details →View SQLAlchemy-Migrate details →

Side-by-Side Comparison

South

SQLAlchemy-Migrate

South

SQLAlchemy-Migrate

Best For

✓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

✓Maintaining legacy SQLAlchemy migration codebases that predate Alembic
✓Simple single-branch migration chains in older Python 2-era projects
✓Understanding historical SQLAlchemy migration patterns before Alembic became standard

Best For

✓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

✓Maintaining legacy SQLAlchemy migration codebases that predate Alembic
✓Simple single-branch migration chains in older Python 2-era projects
✓Understanding historical SQLAlchemy migration patterns before Alembic became standard

Weaknesses

•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

•Officially deprecated — Alembic is the designated successor from the same author
•No longer actively maintained; security and Python 3 compatibility issues may arise
•Not recommended for any new project under any circumstances

Weaknesses

•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

•Officially deprecated — Alembic is the designated successor from the same author
•No longer actively maintained; security and Python 3 compatibility issues may arise
•Not recommended for any new project under any circumstances

License

Apache-2.0

MIT

License

Apache-2.0

MIT

Install

pip install South

pip install sqlalchemy-migrate

Install

pip install South

pip install sqlalchemy-migrate

Rating

★ 4.0

★ 4.2

Rating

★ 4.0

★ 4.2

Key Features

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

SQLAlchemy-Migrate

1Version-controlled database schema migrations for SQLAlchemy-managed databases
2Change scripts written in Python using SQLAlchemy expressions
3Migration repository pattern tracking applied and unapplied schema versions
4Supports upgrade and downgrade operations for safe rollbacks
5Compatible with PostgreSQL, MySQL, SQLite, and Oracle databases

How Python Data Engineers Use These Tools