Migrate from Neon
ArmorDB uses vanilla PostgreSQL 17, making migrations from other managed providers like Neon straightforward and reliable using standard tools.
1. Export from Neon
Use \`pg_dump\` to export your database schema and data. We recommend using the \`--no-owner\` and \`--no-acl\` flags to avoid permission conflicts on the target instance.
pg_dump --no-owner --no-acl \
-d "postgres://user:[email protected]/dbname" \
-f backup.sql2. Import to ArmorDB
Once you have your SQL file, import it into your newly provisioned ArmorDB instance. Ensure you have your mTLS certificates configured if connecting via the direct port.
psql "postgres://julian:[email protected]:6432/dbname" \
-f backup.sqlPro Tip: Use Pipe for Large DBs
For large databases, you can pipe the output directly to avoid local storage overhead:pg_dump $NEON_URL | psql $ARMORDB_URL
