Thank you to everyone who has used the 1.0 version of Gyana. Your insights were the driving force behind the development and release of our 2.0. Sincerely, we could not have done it without you.

We've written this guide to cover everything we could think of, on how to move from 1.0 to 2.0. It's very important to us that this is a good experience for you, if you have any issues or concerns please don't hesitate to reach out to support.

Redeeming access to Gyana 2.0

Existing Gyana customers will get an email on the launch date with a link and information to create a new account, you can also access the redemption link directly via Gyana 2.0 will be available at

Getting used to Gyana 2.0

While Gyana 2.0 is designed with the same goal (no-code data analytics), you'll notice that we're using different words for the parts of the tool. Use this quick guide to get you oriented:

Gyana 2.0

Gyana 1.0










Insights + Reports

Here are the key differences to keep in mind:

  • Unlike organisations, you can be part of multiple teams. This is useful if you work in multiple organisations, or if you want a separate workspace for personal work.

  • Projects are a new feature, that enable you to group work for different clients or internal projects without the risk of mixing up things.

  • Integrations include a native Google Sheets importer that is quick and easy to use. We've also invested time into improving the setup workflow for data sources, especially connectors. There is no Excel importer - we recommend that you either export a CSV or convert to a Google Sheet.

  • Workflows are a more general, powerful version of tables. There is a special node for writing formulas if you need that kind of power, but otherwise it's all "point and click".

  • Dashboards have more types of visualisations, and you have freedom to move and reshape your widgets on a canvas (think DataStudio). If you want, you can get the feel of a report by changing the canvas dimensions to portrait, and using text widgets to write content. Dashboards can be shared as public (but unguessable) URLs. There is no PDF download available.

Moving your work across

Unfortunately, there is no way to automatically move work from Gyana 1.0 to Gyana 2.0. This isn't a decision we made lightly, but unfortunately technically it would have been close to impossible to do. We promise this is a "once in a product lifetime" event, future changes will be backwards compatible.

It's possible to export assets from any part of Gyana 1.0:

  • Use the Download to CSV button to export data or tables as a CSV file. You can then upload this into Gyana 2.0 as an integration, and continue your work.

  • Use the Download Chart PNG button to export a static image for any insight.

  • Use the Export to PDF button to export a static PDF for any report.

If you'd like help in understanding how to move an existing workflow from Gyana 1.0 to Gyana 2.0, we're always happy to discuss. Just reach out in the chat or any support channel.

AppSumo customers

If you purchased the tool through AppSumo, all your codes, stacking and extra rows will continue to be valid. You can manage this all on the "Billing" tab:

  • Enter your extra codes to stack your deal. We'll automatically work out what deal you were on, based on when you bought the codes.

  • If we gave you extra rows for any other reason, reach out to us in the chat.

Kindly note that any refunded codes will not be valid on Gyana 2.0. (We didn't really enforce this on Gyana 1.0.)

💡 Note that all AppSumo codes are applied to individual teams.

Gyana 1.0 End of Life

After the launch, Gyana 1.0 will move to a new home at You'll be able to use the tool with all existing features. We'll continue to respond to critical bugs and security issues. For other support, our recommendation is that you migrate to Gyana 2.0.

Gyana 1.0 will be available as is until 13/12/21, i.e. three months from launch date. On that date, Gyana 1.0 will go offline and will no longer be available. Your data will be deleted in accordance with our retention policies.

Did this answer your question?