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 TG 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.

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

Customers currently running on TG Cloud Classic on AWS will need to migrate to Savanna before that date.

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

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

No. There is no additional cost for the migration 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, remaining TG Cloud Classic credits will be converted into dollar value based on the original credit purchase price.

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

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

TigerGraph will work with each customer 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 customers are responsible for validating and updating their applications, integrations, and workflows where needed.

Customer responsibilities may include:

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

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

Some applications may require changes.

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

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

Yes, customers 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 timing and required actions with the customer in advance.

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

This may include:

Customers should validate that their 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 customers 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 the customer 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.

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

This helps improve resource efficiency and gives teams more flexibility in how they 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, customers can build AI applications that use both semantic similarity and connected data context.

MCP and agent-based execution allow teams 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 TigerGraph to be integrated into CI/CD pipelines, enterprise workflows, internal platforms, and automated operational processes.

TigerGraph will work directly with customers throughout the migration process.

Support will include:

Customers should contact their TigerGraph account team or TigerGraph Support for migration planning and questions.

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