How to Migrate from SeekWell to SaturnSQL

Last updated May 18, 2026 · By the SaturnSQL team

ThoughtSpot has announced that SeekWell will reached end of life on July 31, 2026. This guide walks through moving your SQL queries, schedules, and Google Sheets syncs to SaturnSQL. For most teams the migration takes under 30 minutes.

Not sure SaturnSQL is the right fit? Compare all SeekWell alternatives first, including ThoughtSpot Sync (the official path), Query Streams, Hex, and Mode. For the full timeline and data-deletion details, see the SeekWell shutdown overview.

Before you start: what carries over and what does not

SeekWell and SaturnSQL overlap on the core workflow but are not identical products. A few things to know going in:

• Carries over: SQL queries, database connections (Postgres, MySQL, SQL Server, Redshift, ClickHouse, BigQuery), scheduled runs, Google Sheets delivery, and Slack message delivery.
• Needs a different approach: SaturnSQL does not have Salesforce write-back. If that is critical, see ThoughtSpot Sync instead.
• Not currently supported: Snowflake as a data source. SaturnSQL is on the roadmap for it but not available today.

Step 1: Inventory your SeekWell queries and schedules

Before touching SaturnSQL, take stock of what you have in SeekWell. Make a simple list (a Google Sheet works well) with one row per query:

• Query name
• Database connection (Postgres, MySQL, etc.)
• Schedule (daily 9am, every Monday, etc.)
• Destination (which Google Sheet and tab, Slack channel, Excel file)
• Owner or recipients

This inventory is what you will check off as you move each item over. It is also useful for spotting duplicates or obsolete schedules that you can quietly retire instead of migrating.

Step 2: Copy your SQL out of SeekWell

SeekWell does not have a bulk export of saved queries, so the safe path is to copy each query’s SQL text out manually. For each saved query:

1. Open the query in SeekWell
2. Select all of the SQL text in the editor
3. Copy it and paste it into a local file named after the query (e.g. daily-revenue-by-region.sql)
4. Save the file in a folder you can find again

Step 3: Create your SaturnSQL account and connect your database

Sign up for SaturnSQL and connect your database. You will need the same connection details you used in SeekWell: host, port, database name, username, and password. SaturnSQL encrypts credentials at rest, so connection details are stored securely.

See the database connection guide if you need help with IP allowlisting, the SSH bastion guide for a database with no public endpoint, or read-only users.

Step 4: Recreate your queries in 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 the SQL and save with the same name you used in SeekWell
5. Run it once to confirm it returns the same results

Once saved, every query is available to the rest of your team through the shared query library, with folders and tags to keep things findable.

Step 5: Recreate schedules and Google Sheets syncs

This is the SeekWell-specific part. For each scheduled query in your inventory:

1. Open the saved query in SaturnSQL
2. Set the same cadence (daily, weekly, specific time) you had in SeekWell
3. Choose Google Sheets as the destination and connect the Google account that owns the target sheet
4. Pick the target spreadsheet and tab. Use the same sheet you were writing to from SeekWell so existing dashboards keep working
5. Run the schedule manually once and verify the data lands in the right cells

Step 6: Invite your team

Go to Settings > Team Members to invite your colleagues. They will 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.

What you get with SaturnSQL

SaturnSQL covers the core SeekWell workflow and adds team-collaboration features on top:

• Browser-based SQL editor — nothing to install, schema-aware autocomplete out of the box
• Scheduled queries to Google Sheets — the SeekWell core, kept self-serve
• Shared query library — queries are searchable across the team, not buried in individual accounts
• AI SQL assistant — on the Pro plan, generate and explain queries using your actual schema
• Multi-database support — PostgreSQL, MySQL/MariaDB, SQL Server, Amazon Redshift, and DynamoDB
• Encrypted credentials — database connection details encrypted at rest

Common questions