How to Migrate from PopSQL to SaturnSQL
Update · August 2026
The September 1 shutdown has been postponed
PopSQL is not shutting down on September 1, 2026 after all, and no data is being deleted. Tiger Data postponed the retirement with no new date, promising at least 90 days’ notice. There is no rush, but this guide still applies whenever you decide to move.
Worth remembering what was announced: until this reversal, PopSQL customers were told every saved query, connection and team setting would be permanently deleted and unrecoverable on September 1, 2026. That deadline was withdrawn roughly three weeks before it landed, which is reason enough to keep your own export.
PopSQL remains in limited support with no new features planned. This guide walks you through moving your queries, team, and workflows to SaturnSQL. The whole process takes about 15 minutes for most teams, which is worth doing at your own pace rather than inside a 90-day notice window.
Not sure SaturnSQL is the right fit? Compare all PopSQL alternatives first, or read the full PopSQL shutdown overview for the current status and what limited support means.
Also lost SeekWell? It reached end of life on July 31, 2026. See the SeekWell to SaturnSQL migration guide.
Google Sheets integration is significantly better than PopSQL’s.
A SaaS company migrating to SaturnSQL from PopSQL
How many queries are you moving?
Steps 1 and 3 below adapt to your choice.
Step 1: Export your queries from PopSQL
Moving a whole library? Use PopSQL’s GitHub two-way sync — it became free for all organizations in September 2025 and pushes every shared query, organized in the same folders, to a GitHub repository as .sql files, so you export your entire library in one step:
- Create an empty GitHub repository (for example
your-company/sql-queries) - In PopSQL, go to Settings and connect the GitHub repository
- PopSQL syncs your shared queries and folders into the repo as .sql files
- Clone or download the repo — you now have every query as a file on your computer
Note: GitHub Sync only covers shared team queries and their folders. For any personal queries you have not shared, open each in PopSQL, use the three-dot menu, and choose Download as .sql.
Keep your .sql files in folders that mirror your PopSQL structure so you can recreate the same organization in SaturnSQL.
With only a handful of queries, you don’t need to export any files. You’ll copy each query straight out of PopSQL and paste it into SaturnSQL in Step 3 — so you can skip ahead to creating your account below.
Want backups anyway? Open each query in PopSQL, click the three-dot menu, and choose Download as .sql to save a copy to your computer.
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. For the safest setup, connect with a read-only database user.
Step 3: Import your queries to SaturnSQL
SaturnSQL imports your queries in bulk, so you don’t have to recreate them one by one. Bring in the folder or .zip you exported from PopSQL in Step 1:
- In SaturnSQL, open the Saved Queries panel in the left sidebar and click Import queries (it’s also under Settings > Import queries)
- Choose Select a folder and pick your exported PopSQL folder, or Select .zip or .sql files to upload the archive from GitHub Sync
- Pick the database connection to attach the queries to, and optionally tick Share imported queries with my team
- Click Import
SaturnSQL recreates your PopSQL folder structure automatically, skips any queries you already have, and shows a summary of how many were imported. You can re-run the import as many times as you like.
For just a few queries, the quickest path is to copy each one straight out of PopSQL — no file export needed. For every query:
- Open the query in PopSQL and copy the SQL
- In SaturnSQL, create a new query
- Paste your SQL into the editor
- Save the query with a descriptive name
Have more than a handful after all? Switch to A big library above for the bulk import instead.
Once imported, 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, Oracle, Redshift, ClickHouse, BigQuery, 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 export all my PopSQL queries at once?
Yes. Use PopSQL’s free GitHub Sync to push your entire shared query library, folders and all, to a GitHub repository as .sql files in one step (see Step 1). Only shared team queries sync, so download any personal queries individually with Download as .sql. Then use SaturnSQL’s bulk Import queries feature to bring the whole folder or .zip in at once — it recreates your folders and skips duplicates automatically.
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 now?
Nothing. The September 1, 2026 shutdown was postponed, so your queries, connections, and integrations keep working and nothing is deleted. If a shutdown is announced later you get at least 90 days’ notice, but exporting your library now costs you nothing.
Does SaturnSQL support the same databases as PopSQL?
SaturnSQL supports PostgreSQL, MySQL/MariaDB, SQL Server, Oracle, Amazon Redshift, ClickHouse, BigQuery, and DynamoDB. If you were using PopSQL with Snowflake, SaturnSQL doesn’t support that yet. Check our alternatives comparison for options that support Snowflake.
Ready to migrate from PopSQL?
