How to Migrate from PopSQL to SaturnSQL

Deadline: September 1, 2026

PopSQL will permanently delete all data after this date. Export your queries before then.

PopSQL has announced it is moving to limited support and will shut down on September 1, 2026. This guide walks you through moving your queries, team, and workflows to SaturnSQL. The whole process takes about 15 minutes for most teams.

Not sure SaturnSQL is the right fit? Compare all PopSQL alternatives first.

Step 1: Export your queries from PopSQL

In PopSQL, you can download individual SQL queries as .sql files. For each query you want to keep:

  1. Open the query in PopSQL
  2. Click the menu icon (three dots) on the query
  3. Select Download as .sql
  4. Save the file to your computer

Repeat this for each query you want to migrate. We recommend creating a folder on your computer to keep all your exported .sql files organized.

Tip: If you have many queries, work through them by folder in PopSQL. This helps you recreate the same organization structure in SaturnSQL.

Step 2: Create your SaturnSQL account

Sign up for SaturnSQL and connect your database. The setup takes just a few minutes — you'll need your database connection details (host, port, database name, username, and password). These are the same credentials you used in PopSQL.

SaturnSQL encrypts all database credentials at rest, so your connection details are stored securely. See our database connection guide if you need help.

Step 3: Import your queries to SaturnSQL

For each .sql file you exported:

  1. Open the .sql file in a text editor
  2. Copy the SQL content
  3. In SaturnSQL, create a new query
  4. Paste your SQL into the editor
  5. Save the query with a descriptive name

Once saved, your queries are available to your entire team. You can organize them into folders and add tags to make them easy to find.

Step 4: Invite your team

Go to Settings > Team Members to invite your colleagues. They'll get access to all shared queries and database connections. SaturnSQL supports role-based access, so you can control who can edit queries vs. who can only view and run them.

Step 5: Set up scheduled queries

If you were using PopSQL's scheduled queries or dashboard features, you can recreate those in SaturnSQL. Set any query to run on a daily or weekly schedule and push results automatically to Google Sheets, making it easy to keep reports up to date.

What you get with SaturnSQL

SaturnSQL offers the collaborative SQL editing features you relied on in PopSQL, plus:

  • Multi-database support — Connect to PostgreSQL, MySQL, SQL Server, and DynamoDB
  • AI-powered SQL assistance — Generate queries from natural language
  • Schema-aware autocomplete — Write queries faster with intelligent suggestions
  • Shared query library — Build a searchable repository of your team's SQL knowledge
  • Scheduled queries — Automate reports to Google Sheets
  • Encrypted credentials — Database connection details encrypted at rest

Common questions

Can I import all my PopSQL queries at once?

PopSQL only supports exporting queries individually as .sql files. You'll need to export and import each query separately. For large libraries, we recommend working through them by folder to keep things organized.

Will my database connections transfer?

Database connections don't transfer between tools. You'll need to re-enter your connection details in SaturnSQL. The credentials are the same ones you used in PopSQL (host, port, database, username, password).

What happens to my PopSQL data after September 1, 2026?

According to PopSQL's announcement, all data will be permanently deleted and cannot be recovered. Make sure to export your queries before the deadline.

Does SaturnSQL support the same databases as PopSQL?

SaturnSQL supports PostgreSQL, MySQL/MariaDB, SQL Server, Amazon Redshift, and DynamoDB. If you were using PopSQL with BigQuery or Snowflake, SaturnSQL doesn't support those yet. Check our alternatives comparison for options that support those databases.

Ready to migrate from PopSQL?