Import & Migration
Migrate your data to SerenDB from various sources including other PostgreSQL databases, cloud providers, and different database systems.
Migration Overview
SerenDB provides multiple pathways to migrate your data, whether you're moving from another PostgreSQL provider, a different database system, or importing data from files.
Migration Methods
Quick Import Tools
Import Data Assistant
An interactive tool that guides you through the data import process with automatic optimization and validation.
CSV Import
Import data directly from CSV files into your SerenDB tables.
Sample Data
Load sample datasets for testing and development purposes.
PostgreSQL Utilities
pg_dump & pg_restore
The standard PostgreSQL tools for database backup and restore. Perfect for one-time migrations of any size.
pgcopydb
A fast and efficient tool for copying entire PostgreSQL databases, including schema and data.
Migration Sources
Cloud Providers
AWS RDS: Migrate from Amazon RDS for PostgreSQL
Azure Database: Move from Azure Database for PostgreSQL
Google Cloud SQL: Transfer from Cloud SQL
AlloyDB: Migrate from Google's AlloyDB
Database Platforms
Supabase: Migrate projects from Supabase
Heroku Postgres: Move from Heroku's PostgreSQL
Render: Transfer from Render databases
Digital Ocean: Migrate from Digital Ocean databases
Other Databases
MySQL: Convert and migrate from MySQL databases
Microsoft SQL Server: Migrate from MSSQL
SQLite: Import SQLite databases
Firebase: Move from Firebase Firestore
Migration Services
AWS DMS: Use AWS Database Migration Service for continuous replication
Logical Replication
For minimal downtime migrations or ongoing synchronization, SerenDB supports logical replication from:
PostgreSQL (any version 10+)
AWS RDS for PostgreSQL
Azure Database for PostgreSQL
Google Cloud SQL
AlloyDB
Supabase
Other SerenDB projects
See the Guides section for detailed logical replication tutorials.
Migration Strategies
Full Database Migration
Copy your entire database including schema, data, indexes, and constraints.
Schema-Only Migration
Migrate just your database schema for testing or development purposes.
Incremental Migration
Use logical replication to sync data continuously while you transition.
Self-Migration
Move between SerenDB projects for reorganization or testing purposes.
Planning Your Migration
Assess your source: Understand your current database size, structure, and dependencies
Choose a method: Select the appropriate migration tool based on your needs
Test the migration: Always test with a subset of data first
Plan for downtime: Estimate and minimize application downtime
Verify data integrity: Confirm all data migrated correctly
Update connection strings: Point your applications to the new database
Best Practices
Test thoroughly: Use SerenDB branches to test migrations
Check compatibility: Review PostgreSQL version compatibility
Optimize before migrating: Clean up unused data and optimize schemas
Monitor performance: Use SerenDB's monitoring tools during migration
Have a rollback plan: Keep your source database available until migration is confirmed
Getting Help
For complex migrations or assistance with your specific use case, consult the detailed guides or contact SerenDB support.
Last updated