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

As Stitch currently allows only one destination per account, 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:

  • indicates that, as far as we know, this combo is always compatible.
  • 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.
  • 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.

For a comprehensive look at how Amazon S3 will load data - including what may cause data to be "rejected" - refer to the Amazon S3 Data Loading Guide.

No compatibility issues have been discovered between Amazon S3 and Stitch's integration offerings.

For a comprehensive look at how BigQuery will load data - including what may cause data to be "rejected" - refer to the BigQuery Data Loading Guide.

No compatibility issues have been discovered between BigQuery and Stitch's integration offerings.

For a comprehensive look at how data.world will load data - including what may cause data to be "rejected" - refer to the data.world Data Loading Guide.

No compatibility issues have been discovered between data.world and Stitch's integration offerings.

For a comprehensive look at how Azure SQL Data Warehouse will load data - including what may cause data to be "rejected" - refer to the Azure SQL Data Warehouse Data Loading Guide.

No compatibility issues have been discovered between Azure SQL Data Warehouse and Stitch's integration offerings.

For a comprehensive look at how Panoply will load data - including what may cause data to be "rejected" - refer to the Panoply Data Loading Guide.

Integration Level Reason for Incompatibility
MongoDB

As a result of the de-nesting Stitch performs on nested structures, deeply nested data in Mongo may result in tables that exceed Panoply’s 1,600 column limit.

For a comprehensive look at how PostgreSQL will load data - including what may cause data to be "rejected" - refer to the PostgreSQL Data Loading Guide.

Integration Level Reason for Incompatibility
HubSpot

Tables and columns created as a result of de-nesting nested data may have names that exceed PostgreSQL’s limit of 63 characters for tables and 59 characters for columns. PostgreSQL data warehouses will reject these tables and columns, meaning Stitch will be unable to load them.

Note: This is applicable to all versions of this integration.

Stripe (v27-02-2015)

Tables and columns created as a result of de-nesting nested data may have names that exceed PostgreSQL’s limit of 63 characters for tables and 59 characters for columns. PostgreSQL data warehouses will reject these tables and columns, meaning Stitch will be unable to load them.

Note: This is applicable to all versions of this integration.

For a comprehensive look at how Redshift will load data - including what may cause data to be "rejected" - refer to the Redshift Data Loading Guide.

Integration Level Reason for Incompatibility
MongoDB

As a result of the de-nesting Stitch performs on nested structures, deeply nested data in Mongo may result in tables that exceed Panoply’s 1,600 column limit.

For a comprehensive look at how Snowflake will load data - including what may cause data to be "rejected" - refer to the Snowflake Data Loading Guide.

No compatibility issues have been discovered between Snowflake and Stitch's integration offerings.


Full destination/integration compatibility matrix

For a comprehensive look at the compatibility of all Stitch's integrations and destinations, check out the matrix below.

Amazon S3
BigQuery
data.world
Azure SQL Data Warehouse
Panoply
PostgreSQL
Redshift
Snowflake
AdRoll
AfterShip
Amazon Aurora (MySQL) RDS
Amazon Microsoft SQL Server RDS
Amazon MySQL RDS
Amazon PostgreSQL RDS (v1.0)
Amazon S3 CSV
Amplitude
AppsFlyer
Autopilot
Bing Ads
Braintree
Branch
Bronto
Campaign Monitor
Close.io
Contentful
Customer.io
Delighted
Desk
Doorbell.io
DoubleClick Campaign Manager
Drip
Facebook Ads
FormKeep
Freshdesk
FullStory
GitHub
GitLab
Google AdWords
Google Analytics
Google Analytics (AdWords)
Google CloudSQL MySQL
Google CloudSQL PostgreSQL (v1.0)
Google ECommerce
Harvest (v2.0)
Harvest Forecast
Heroku (v1.0)
HubSpot
Import API
Intercom
Iterable
JIRA
Listrak
Magento
Mailjet
Mandrill
MariaDB
Marketo
Microsoft Azure
Microsoft SQL Server
Mixpanel
MongoDB
MySQL
NetSuite
Outbrain
Pardot
Particle.io
Pipedrive
PostgreSQL (v1.0)
Quick Base
QuickBooks
Recurly
Referral SaaSquatch
Salesforce
Segment
SendGrid
SendGrid Core
SendWithUs
Shippo
Shopify (v15-10-2015)
SparkPost
Square
Stitch Incoming Webhooks
Stripe (v27-02-2015)
Taboola
Trello
Urban Airship
UserVoice (v1.0)
Vero
Wootric
Xero
Yotpo
Zapier
Zendesk
Zendesk Chat (Zopim)
Zuora


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: destinations