As of , Stitch supports replicating the data types listed in the table below.

If a data type is not present in the table, it means that Stitch does not currently support replication for that data type. Syncing columns with unsupported data types may lead to issues with replication.

Data Type Supported Integrations Notes
ARRAY PostgreSQL Integrations This data type will be stored as a STRING in your data warehouse.
BIGINT All Integrations
BIT All Integrations
CHAR All Integrations
DATE All Integrations
DECIMAL All Integrations
DOUBLE All Integrations
FLOAT All Integrations
HSTORE PostgreSQL Integrations This data type will be stored as a STRING in your data warehouse.
INTEGER All Integrations
JSON PostgreSQL Integrations This data type will be stored as a STRING in your data warehouse.
JSONB PostgreSQL Integrations This data type will be stored as a STRING in your data warehouse.
LONGVARCHAR All Integrations
LONGNVARCHAR All Integrations
NCHAR All Integrations
NVARCHAR All Integrations
NUMERIC All Integrations
REAL All Integrations
SMALLINT All Integrations
TIME All Integrations
TIMESTAMP All Integrations
TINYINT All Integrations Under certain circumstances, Stitch may store this data type as BIT(1)/boolean. Click the link in the Data Type column for more details.
UUID PostgreSQL Integrations This data type will be stored as a STRING in your data warehouse.
VARBINARY All Integrations
VARCHAR All Integrations

Columns with Mixed Data Types

Occasionally Stitch will encounter a column that contains more than one data type. As Stitch requires that there be only one data type per column to properly type and store your data, columns containing multiple data types may be “split” to ensure all values are correctly typed.

For example: an order_confirmed column is synced and typed as BOOLEAN. In a subsequent sync, Stitch detects VARCHAR values in this column.

As a result, Stitch will create an additional column to accommodate the VARCHAR values. The new column name will be the original name appended with the data type: order_confirmed__string

How columns are named depends on the type of destination being used to warehouse data. Refer to the Mixed Data Types guide for more info.


Syncing Unsupported Data Types

Columns containing data types that aren’t supported may prevent an entire table from replicating.

If you determine a non-replicating column contains an unsupported data type, you’ll need to unsync it to allow the table to successfully replicate.


‘Not Supported’ Status for Columns

If a column you want to sync has a Status of Not Supported, the root cause may be an unsupported data type or insufficient user permissions.



Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.

Tags: replication