# Destination & Integration Compatibility

When selecting a destination, it’s important to first verify that all the data sources you want to connect to Stitch will be compatible.

We recommend verifying your integrations’ compatibility before connecting a destination. This will ensure that you can successfully connect and replicate data from all your sources.

## Degrees of incompatibility

The compatibility of any integration/destination combination falls into one of three categories: **always** compatible, **sometimes** compatible, and **never** compatible.

The matrices below use the following icons to indicate the degree of incompatibility for an integration/destination combo:

* the Warning 2 icon

  indicates that this combo is **sometimes** compatible - there may be compatibility issues, but they’re infrequent or parts of the integration may still be usable.
* the Remove icon

  indicates that this combo is **never** compatible. It’s unlikely that Stitch will be able to load data from this integration into the given destination.

## Incompatible integrations by destination type

Below you’ll find a list of integrations that may have full or partial incompatibility with any of Stitch’s destination offerings.

Refer to the [Destination data loading guides](https://help.qlik.com/en-US/stitch/replication/loading) for a comprehensive look at how destinations will load data, including what may cause data to be rejected.

| **Amazon S3**<br><br>([link](https://help.qlik.com/en-US/stitch/destinations/amazon-s3)) |  |  |  |
| --- | --- | --- | --- |
| No compatibility issues have been discovered between Amazon S3 and Stitch's integration offerings. |  |  |  |
| **Google BigQuery<br><br>v1**<br><br>([link](https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v1)) |  |  |  |
| No compatibility issues have been discovered between this version (v1) of the Google BigQuery destination and Stitch's integration offerings. |  |  |  |
| **Google BigQuery<br><br>v2**<br><br>([link](https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v2)) |  |  |  |
| No compatibility issues have been discovered between this version (v2) of the Google BigQuery destination and Stitch's integration offerings. |  |  |  |
| **data.world**<br><br>([link](https://help.qlik.com/en-US/stitch/destinations/data-world)) |  |  |  |
| No compatibility issues have been discovered between data.world and Stitch's integration offerings. |  |  |  |
| **Databricks Delta Lake (AWS)**<br><br>([link](https://help.qlik.com/en-US/stitch/destinations/databricks-delta)) |  |  |  |
| No compatibility issues have been discovered between Databricks Delta Lake (AWS) and Stitch's integration offerings. |  |  |  |
| **Microsoft Azure Synapse Analytics**<br><br>([link](https://help.qlik.com/en-US/stitch/destinations/microsoft-azure-synapse-analytics)) |  |  |  |
| No compatibility issues have been discovered between Microsoft Azure Synapse Analytics and Stitch's integration offerings. |  |  |  |
| **Microsoft SQL Server**<br><br>([link](https://help.qlik.com/en-US/stitch/destinations/microsoft-sql-server)) |  |  |  |
| No compatibility issues have been discovered between Microsoft SQL Server and Stitch's integration offerings. |  |  |  |
| **MySQL**<br><br>([link](https://help.qlik.com/en-US/stitch/destinations/mysql)) |  |  |  |
| No compatibility issues have been discovered between MySQL and Stitch's integration offerings. |  |  |  |
| **Panoply**<br><br>([link](https://help.qlik.com/en-US/stitch/destinations/panoply)) |  |  |  |
| **Integration** | **Version** | **Level** | **Reason** |
| MongoDB | ANY | the Warning 2 icon<br><br>This destination/integration combination is sometimes incompatible. | Flattening nested JSON structures may result in tables with columns that exceed Panoply’s 1,600 column limit. [Learn more](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures). |
| MongoDB Atlas | v1 | the Warning 2 icon<br><br>This destination/integration combination is sometimes incompatible. | Flattening nested JSON structures may result in tables with columns that exceed Panoply’s 1,600 column limit. [Learn more](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures). |
| **PostgreSQL**<br><br>([link](https://help.qlik.com/en-US/stitch/destinations/postgresql)) |  |  |  |
| **Integration** | **Version** | **Level** | **Reason** |
| HubSpot | ANY | the Warning 2 icon<br><br>This destination/integration combination is sometimes incompatible. | [Flattening nested JSON structures](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures) may result in tables and columns with names that exceed PostgreSQL’s character limit for object names:<br><br><ul> <li>63 characters characters for tables</li> <li>59 characters characters for columns</li></ul> |
| Stripe | ANY | the Warning 2 icon<br><br>This destination/integration combination is sometimes incompatible. | [Flattening nested JSON structures](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures) may result in tables and columns with names that exceed PostgreSQL’s character limit for object names:<br><br><ul> <li>63 characters characters for tables</li> <li>59 characters characters for columns</li></ul> |
| **Amazon Redshift**<br><br>([link](https://help.qlik.com/en-US/stitch/destinations/amazon-redshift)) |  |  |  |
| **Integration** | **Version** | **Level** | **Reason** |
| MongoDB | ANY | the Warning 2 icon<br><br>This destination/integration combination is sometimes incompatible. | Flattening nested JSON structures may result in tables with columns that exceed Amazon Redshift’s 1,600 column limit. [Learn more](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures). |
| MongoDB Atlas | v1 | the Warning 2 icon<br><br>This destination/integration combination is sometimes incompatible. | Flattening nested JSON structures may result in tables with columns that exceed Amazon Redshift’s 1,600 column limit. [Learn more](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures). |
| **Snowflake**<br><br>([link](https://help.qlik.com/en-US/stitch/destinations/snowflake)) |  |  |  |
| No compatibility issues have been discovered between Snowflake and Stitch's integration offerings. |  |  |  |