TG Cloud Classic to Savanna Migration FAQ

TigerGraph Cloud Classic, also known as TG Cloud V3, on AWS will reach end of life on September 30, 2026.

TigerGraph is transitioning customers from TigerGraph Cloud Classic to TigerGraph Savanna, our next-generation cloud-native graph database platform.

Savanna is the future of TigerGraph Cloud and provides a modern foundation for operational graph workloads, analytics, AI, GraphRAG, MCP, and agent-based workflows.

Savanna is TigerGraph’s strategic cloud platform moving forward.

It provides a more modern architecture and introduces capabilities that are not available in TG Cloud Classic, including:

Moving customers to Savanna allows TigerGraph to focus innovation, support, and engineering investment on a single modern cloud platform.

TigerGraph Cloud Classic on AWS will reach end of life on September 30, 2026.

If you are currently running TG Cloud Classic on AWS, you will need to migrate to Savanna before that date.

TigerGraph will manage and execute your migration end-to-end.

TigerGraph will work with you to plan the migration, prepare the target Savanna environment, validate workloads in advance, execute the migration, and support you through verification and cutover.

No. There is no additional cost for migrating from TG Cloud Classic to Savanna.

TigerGraph will perform the migration as part of the transition to Savanna.

No. The migration will not impact your current pricing.

Your consumption rate will remain the same in Savanna based on your existing pricing agreement.

Any remaining TG Cloud Classic credits will be added to Savanna as part of the migration process.

Savanna does not use credits in the same way as TG Cloud Classic. Savanna uses dollars.

As part of the migration, your remaining TG Cloud Classic credits will be converted into dollar value based on the original credit purchase price.

TigerGraph’s goal is to perform your migration with minimal downtime and minimal disruption to your operations.

The exact downtime will depend on the size of your environment, data volume, workload complexity, and migration plan.

TigerGraph will work with you to define the migration window and validate the expected downtime before execution.

The migration process generally includes the following phases:

TigerGraph will manage the migration process, but you are responsible for validating and updating your applications, integrations, and workflows where needed.

Your responsibilities may include:

You are responsible for resolving any breaking changes as part of the migration.

TigerGraph will help identify known changes and provide guidance, but you are responsible for making any required updates to your applications, client code, integrations, queries, authentication flows, or operational processes.

Some applications may require changes.

For example, you may need to update connection endpoints, authentication flows, token-generation logic, API calls, or other integration points depending on how your applications currently interact with TG Cloud Classic.

TigerGraph will work with you during the planning phase to help identify potential changes before migration.

Yes. You may need to pause traffic during the agreed migration window.

This may include stopping user access, REST API calls, loading jobs, ingress operations, egress operations, and application traffic to the TG Cloud Classic environment.

This helps ensure a clean migration and consistent data state.

TigerGraph will coordinate the timing and required actions with you in advance.

TigerGraph will perform pre-migration and post-migration validation.

This may include:

You should validate that your applications, integrations, workloads, queries, and operational processes work as expected in Savanna.

This includes:

Yes. Where appropriate, TigerGraph may support a shadowing or parallel validation period.

During this phase, traffic can be mirrored or workloads can be tested against the new Savanna environment while the legacy TG Cloud Classic environment continues serving production traffic.

This allows you to observe behavior, compare results, validate latency, and identify issues before final cutover.

During cutover, production traffic is moved from TG Cloud Classic to Savanna.

Once you and TigerGraph confirm that the Savanna environment is operating as expected, the legacy TG Cloud Classic environment can be decommissioned according to the agreed plan.

Savanna provides several key capabilities, including:

Separation of compute and storage allows workloads to scale more flexibly.

You can run operational and analytical workloads in parallel and scale them independently based on demand.

This helps improve resource efficiency and gives you more flexibility in how you operate graph workloads.

Native vector storage enables AI use cases such as similarity search, semantic retrieval, and GraphRAG.

By combining graph relationships with vector data, you can build AI applications that use both semantic similarity and connected data context.

MCP and agent-based execution allow you to automate graph workflows.

Agents can help automate graph deployment, query execution, analysis workflows, and other graph operations through controlled, programmatic access.

Savanna provides programmatic control over graph creation, data loading, query execution, and management.

This allows you to integrate TigerGraph into CI/CD pipelines, enterprise workflows, internal platforms, and automated operational processes.

TigerGraph will work directly with you throughout the migration process.

Support includes:

If you have questions about migration planning or the migration process, contact your TigerGraph account team or TigerGraph Support.

You can also contact the Savanna migration team by emailing savanna-support@tigergraph.com.

TigerGraph will provide migration resources, documentation, and support contacts as part of the customer migration program.