Move in easily. Leave just as easily.
Standard pg_dump and pg_restore in both directions, with the exact commands for your version — and a one-click export whenever you want your data.
- Standard PostgreSQL tools
- Help from our engineers
- No lock-in
# 1. Export from your current provider pg_dump --format=custom --no-owner --no-acl \ --dbname "$SOURCE_DATABASE_URL" --file app.dump # 2. Restore into Balta over the direct endpoint pg_restore --no-owner --no-acl --jobs 4 \ --dbname "$BALTA_DIRECT_URL" app.dump
Three steps to Balta.
- 01Export
Dump your existing database with pg_dump, in PostgreSQL’s custom format.
- 02Create
Create a Balta service on the plan and PostgreSQL version you need.
- 03Restore
Load your data with pg_restore over the direct endpoint, then point your application at your new connection string.
Compatibility
Standard PostgreSQL, end to end.
Your tables, indexes, views, functions and data move across as they are. A small number of things need attention before you start — mostly objects that depended on superuser on your old platform. Our compatibility notes list them, with what to do about each.
| Check | Why it matters |
|---|---|
| PostgreSQL version | Restore into the same major version or newer |
| Extensions | Confirm each one is in the supported catalogue |
| Object ownership | Restore with --no-owner, so objects belong to your role |
| Superuser-only objects | These are listed in the compatibility notes |
Portability
Your data is always yours.
pg_dump works against your service whenever it’s running. Your dashboard can also produce a complete export and email you a download link — available even if your account is suspended, and on the day you cancel.
No proprietary storage, no forked protocol, no extension you can only get here. Leaving Balta takes the same two commands as arriving.
A complete export in PostgreSQL's custom format, ready for pg_restore.
Example view with sample data.