---
title: "Compatibility between TigerGraph 2 and TigerGraph 3.0"
description: "lists the compatibility issues between TigerGraph 2 and TigerGraph 3, for users who plan to migrate"
component: "home"
version: "master"
module: "compatibility"
html_url: "/home/compatibility/changes-from-tg2-to-tg3"
canonical_url: "https://www.tigergraph.com/docs/home/compatibility/changes-from-tg2-to-tg3"
markdown_url: "https://www.tigergraph.com/docs/home/compatibility/changes-from-tg2-to-tg3.md"
---

[View as HTML](https://www.tigergraph.com/docs/home/compatibility/changes-from-tg2-to-tg3)

# Compatibility between TigerGraph 2 and TigerGraph 3.0

Major revisions (e.g., from TigerGraph 2 to TigerGraph 3) are the opportunity to deliver significant improvements. While we make every effort to maintain backward compatibility, in selected cases APIs have changed or deprecated features have been dropped, in order to advance the overall product.

**Data migration**: A tool is available to migrate the data in TigerGraph 2.6 to TigerGraph 3.0\. Please contact TigerGraph Support for assistance.

**Query and API compatibility**:

* Some gadmin syntax has changed. Notably. `gadmin set config` is now `gadmin config set`. Please see [Managing with gadmin](https://www.tigergraph.com/docs/tigergraph-server/4.3/system-management/management-with-gadmin.md).
* Some features which were previously deprecated have been dropped. Please see [V3.0 Removal of Previously Deprecated Features](https://www.tigergraph.com/docs/home/compatibility/changes-from-tg2-to-tg3.md#_v3_0_removal_of_previously_deprecated_features) for a detailed list.

## V3.0 Removal of Previously Deprecated Features

TigerGraph 2.x contained some features which were labeled as deprecated. These features are no longer necessary because they have been superseded already by improved approaches for using the TigerGraph platform.

The new approaches were developed because they use more consistent grammar, are more extensible, or offer higher performance. Therefore, TigerGraph 3.0 and above has streamlined the product by removing support for some of these deprecated features, listed below:

#### Data Types

| Deprecated type | Alternate approach |
| --- | --- |
| `REAL` | Use `FLOAT` or `DOUBLE` |
| `INT_SET` | Use `SET<INT>` |
| `INT_LIST` | Use `LIST<INT>` |
| `STRING_SET_COMPRESS` | Use `SET<STRING COMPRESS>` |
| `STRING_LIST_CONPRESS` | Use `LIST<STRING COMPRESS>` |
| `UINT_SET` | Use `SET<INT>` |
| `UINT32_UINT32_KV_LIST` | Use `MAP<UINT, UINT>` |
| `INT32_INT32_KV_LIST` | Use `MAP<INT, INT>` |
| `UINT32_UDT_KV_LIST` | Use `MAP<UINT, UDT_type>`, where `UDT_type` is a user-defined tuple type |
| `INT32_UDT_KV_LIST` | Use `MAP<INT, UDT_type>`, where `UDT_type` is a user-defined tuple type |

#### Syntax for Control Flow Statements

| Deprecated statement | Alternate statement |
| --- | --- |
| `FOREACH …​ DO …​ DONE` | `FOREACH…​ DO…​ END` |
| FOREACH (condition) {     body } | FOREACH condition DO     body END |
| IF (condition) {     body1 } else {     body2 } | IF condition THEN     body1 ELSE     body2 END |
| WHILE (condition) {     body } | WHILE condition DO     body END |

#### Vertex set variable declaration

See [Vertex Set Variable Declaration and Assignment](https://www.tigergraph.com/docs/gsql-ref/4.3/querying/declaration-and-assignment-statements.md#_vertex_set_variables)

If a vertex type is specified, the vertex type must be within parentheses.

| Deprecated Statement | Alternate Statement |
| --- | --- |
| `MySet Person = …​` | `MySet (Person) = …​` |

#### Query, Job, and Token Management

| Deprecated operation | Header 2 |
| --- | --- |
| `CREATE JOB` | Job types need to be specified: * `CREATE LOADING JOB` * `CREATE SCHEMA_CHANGE JOB` * `CREATE GLOBAL SCHEMA_CHANGE JOB` |
| `RUN JOB` | Job types need to be specified: * `RUN LOADING JOB` * `RUN SCHEMA_CHANGE JOB` * `RUN GLOBAL SCHEMA_CHANGE JOB` |
| `CREATE / SHOW/ REFRESH TOKEN` | To create a token, use the [REST endpoint GET /requesttoken](https://www.tigergraph.com/docs/tigergraph-server/3.10/API/built-in-endpoints.md#_request_a_token). |
| `offline2online` | The offline loading job mode was discontinued in v2.0\. Do not write loading jobs using this syntax. |

#### Output

See [PRINT Statement](https://www.tigergraph.com/docs/gsql-ref/4.3/querying/output-statements-and-file-objects.md#_print_statement_api_v2)

| Deprecated Syntax | Alternate Syntax |
| --- | --- |
| JSON API v1 | v2 has been the default JSON format since TigerGraph 1.1\. No alternate JSON version will be available. |
| `PRINT …​ TO_CSV [filepath]` | Define a file object, then `PRINT …​ TO_CSV [file_object]` |

#### Built-in Queries

| Deprecated statement | Alternate statement |
| --- | --- |
| `SELECT count() FROM …​` | * `SELECT approx_count(*) FROM …​`      * May not include all the latest data updates * `SELECT count(*) FROM …​`      * exact, but slower than `approx_count(*)` |

---

See also [Compatibility among TigerGraph 3 versions](https://www.tigergraph.com/docs/home/compatibility/changes-among-tg3.md)
