DuneSQL Migration Update II

We hit day 60 of our 90 day DuneSQL Migration Plan, here's how it's going so far

Table of Contents
Share on twitter iconShare on linkedin iconShare on reddit icon

Update July 4th:

  • The Spellbook freeze was extended until July 5th
  • We moved the full deprecation date to 30th of July
  • Query edits & creation for both Spark and Postgres will be disabled on 15th of July


To focus all of our efforts on DuneSQL, we are progressively sunsetting both SparkSQL and Ethereum V1 (Postgres) to make DuneSQL the only query engine available on Dune.

So far, we have:

  • disabled all query creations for PostgreSQL queries
  • stopped ingesting data for all non Ethereum postgreSQL instances

on July 15th:

  • migrate Spellbook to DuneSQL
  • disable all creation and edits for SparkSQL queries (except for Spellbook contributors)
  • disable all edits for PostgresSQL queries

on July 30th:

  • disable all executions on Postgres & Spark
  • stop ingesting new data on Postgres & Spark


In our last migration update, we mentioned our investment in migration support to make the process as seamless as possible.

Our efforts are focused on:

  • Supporting migration efforts with powerful features to migrate your queries
  • Continuously improving DuneSQL’s stability and performance
  • Transitioning Spellbook from SparkSQL to DuneSQL

Here are key updates on those areas as we hit the 60 day mark of our 90 day sunsetting plan:

Supporting migration efforts

Harmonizer (the “Migrate to DuneSQL” feature) has made significant improvements and has been used to migrate over 50% of the top 50 dashboards on!

You can confidently use it to migrate your Ethereum V1 and SparkSQL queries. If you run into any issues don’t hesitate to reach out to us on Discord or send us your feedback!

Continuously improving DuneSQL

As mentioned in the last update, performance has largely been addressed in DuneSQL with the rollout of performance tiers, materialization of nft.trades/dex.trades, and improvements to the overall engine. You should be using DuneSQL for all your new queries.

We’ve also addressed the “too many stages” issue that was present for more complex queries by doubling the amount of stages on the large query engine (from 500 to 1000) before timing out. To further help with timeout issues of more advanced queries, we are rolling out materialized views in late July.

Transitioning to DuneSQL Spellbook 

Finally, we are ready to start the migration to a DuneSQL Spellbook. This will have no impact on the in-app experience. When querying spells from DuneSQL, you can continue to use spells like you do today.

For contributors to Spellbook, we will be freezing contributions to the following spells to facilitate their migration to DuneSQL Spellbook. The freeze of these spells will take place next week from June 22nd to June 28th.

  • nft.trades
  • dex.trades
  • labels

During the freeze these spells on SparkSQL Spellbook will be moved into maintenance mode (no new pull requests) and after they have been migrated, contributions will need to be made in DuneSQL.

For the remaining spells, we will start migrating them over the next few weeks, freezing individual spells as we migrate them. We will share updates on upcoming spells on both github and discord. Details on the Spellbook Migration will be posted in the github discussion section in the Spellbook Repo.

Thank you for your continued trust and support during this migration, we hope you’re loving the new capabilities DuneSQL has to offer. We appreciate your patience during this transition.

Don’t hesitate to reach out to us via for any questions or concerns.

The data must flow!

More details and FAQs are available in our docs.

Subscribe to our newsletter!

The revolution will not be reported quarterly.
Celebrating Dune wizards. Dashboards, stories, alpha dropped in your inbox weekly.