Documentation and guides for configuring and managing data replication for your Stitch integrations.
Learn how Stitch extracts, prepares, and loads your data during the replicaiton process.
After you connect an integration and Stitch performs a structure sync, the next thing you’ll do is select tables and columns to replicate. In this guide, we’ll walk you through how to set objects for database and SaaS integrations to replicate.
By default, a historical replication job for most SaaS integrations will go back one year. While the Start Date setting allows you to define historical data loads, it can also reset an integration’s Replication Keys when you need to re-replicate data.
Replicating a database view is almost the same as replicating a database table. In this guide, we’ll cover the database integrations that support views and the additional steps required to replicate a database view.
What happens when you add a brand-new column in a data source or you want to sync additional columns on an already-syncing table? How will your row count be impacted? In this guide, we cover how Stitch handles new columns, what you can expect for existing rows, and how to backfill data.
A full roll-up of the data types Stitch supports for replication.
Create a replication schedule for your integration’s using Stitch’s Replication Frequency and Anchor Time features.
Replication Methods tell Stitch how to replicate data during a replication job. In this guide, we’ll explain the methods Stitch uses, how they work for database and SaaS integrations, and how to define Replication Methods for your database integration tables.
Replication Keys are columns that Stitch uses to identify new and updated data for replication. These columns are one of the most important components of Stitch, as they enable Stitch to correctly capture new and updated data. In this guide, we’ll walk you through what a Replication Key is, what its requirements are, and how to choose the best column for the job.
Replication Keys for Mongo integrations have their own set of quirks and gotchas, owing to how Mongo itself is designed. In this guide, we’ll explain what to watch out for and how to choose the best field for the job.
It can be difficult to be patient when all you want is your data. In the Integration Details page for every integration, you can check out that integration’s Replication Stats. This section will give you a better idea of where your data is in the replication process.
Extraction logs provide detail about the extraction portion of the replication process for a given integration.
Loading reports provide detail about the loading protion of the replication process for a given integration.