Neon data migration guides
This guide helps you choose the best migration method based on your database size, downtime tolerance, source database type, and technical requirements. Migration methods. Method Best For Database Siz...
This guide helps you choose the best migration method based on your database size, downtime tolerance, source database type, and technical requirements.
Migration methods
Section titled “Migration methods”| Method | Best For | Database Size | Downtime | Technical Skill | Key Benefit |
|---|---|---|---|---|---|
| Import Data Assistant | Quick Postgres migrations | Under 10GB | Minimal (minutes–hours) | Low | Easiest - fully automated |
| pg_dump/restore | Standard Postgres migrations | Any size | Required | Medium | Reliable and well-tested |
| pgcopydb | Large Postgres databases | 10GB+ | Required | Medium | Parallel processing - fast |
| Logical Replication | Production Postgres workloads | Any size | Near-zero | High | Minimal downtime |
| pgloader | Non-Postgres sources | Any size | Required | Medium | Handles MySQL, MSSQL, SQLite |
| AWS DMS | Multi-source or custom transformations | Any size | Minimal (minutes–hours) | High | Advanced transformation rules |
Region migration
Section titled “Region migration”If you need your Neon database in a different region, or a Postgres-compatible export from Neon, start with Region migration for paths and tradeoffs. For Neon-to-Neon moves, use Migrate to another Neon region. A project stays in one region; you create a new Neon project in the target region and migrate your data, or export. For a piped pg_dump | pg_restore between Neon projects, see Migrate data from another Neon project.
Provider-specific guides
Section titled “Provider-specific guides”For step-by-step instructions tailored to specific databases or providers, see MySQL, MSSQL, SQLite, Heroku, Supabase, PlanetScale, Turso, Render, Azure, Digital Ocean, Railway, Firebase, or another Neon project.
Logical replication guides
Section titled “Logical replication guides”For near-zero downtime Postgres database migrations using logical replication, see guides for AWS RDS, Google Cloud SQL, AlloyDB, Azure, Supabase, PostgreSQL, or Neon to Neon.
Other imports
Section titled “Other imports”- Import data from CSV: Import data from CSV files using psql
- Import sample data: Try Neon with sample datasets
- Migrate schema only: Migrate just the schema without data
Need help?
Section titled “Need help?”Join our Discord Server to ask questions or see what others are doing with Neon. For paid plan support options, see Support.