Docs/Import/From NeonDB

Migrate from NeonDB

Switch from NeonDB's serverless model to PhoenixDB's always-on databases.

Why Switch from NeonDB?

NeonDB's scale-to-zero causes cold start delays. PhoenixDB is always on.

No CU-hour billing. Simple flat monthly pricing.

No autoscaling fluctuations. Steady, reliable performance.

In the Neon Console, go to your project and copy the connection string:

postgresql://user:password@ep-xxx-xxx-123456.us-east-2.aws.neon.tech/neondb?sslmode=require

If you haven't already, create a new database in your PhoenixDB dashboard:

Use pg_dump with your NeonDB connection string:

pg_dump -Fc -v \
  "postgresql://user:password@ep-xxx-xxx-123456.us-east-2.aws.neon.tech/neondb?sslmode=require" \
  > neon_backup.dump

Restore the dump to your PhoenixDB database:

pg_restore -v --no-owner --no-acl \
  -h abc123.server1.phoenixdb.space \
  -U postgres -d mydb neon_backup.dump

--no-owner

Skip original ownership (Neon uses different roles)

--no-acl

Skip access privileges from Neon

Replace your NeonDB connection string with your PhoenixDB connection string:

Before (NeonDB):

DATABASE_URL="postgresql://user:pass@ep-xxx.neon.tech/neondb?sslmode=require"

After (PhoenixDB):

DATABASE_URL="postgresql://postgres:pass@abc123.phoenixdb.space:5432/mydb?sslmode=require"

NeonDB extensions (like pgvector) are supported if you installed them on PhoenixDB
Branching features don't carry over (PhoenixDB uses a different model)
Database roles: PhoenixDB uses "postgres" as the main user

Test your application with the new PhoenixDB connection before disabling NeonDB. Keep NeonDB running until you've verified everything works.