Replication scheduling is currently supported only at the integration level. This means that when Stitch runs a replication job, all selected tables will be replicated.

If you want to replicate data for tables on different schedules, you can create two integrations and configure the schedules to match your needs. This can be useful for reducing your row usage or simply replicating data only when you need it.

The method outlined in this tutorial can be used with all Replication Scheduling types.

Example use cases

  • Reducing your overall row usage
  • Reducing re-replication of tables using Full Table Replication
  • Replicating different data sets at different intervals


  • An integration that supports table selection. This tutorial is applicable only to database and SaaS integrations that support table selection.

  • An integration that supports multiple connections. Some integrations may only allow one connection at a time. For example: NetSuite only allows a user to have a single API session open at any given time.

Step 1: Create the first integration

In this step, you’ll create the first integration in your Stitch account. Refer to the database or SaaS documentation for instructions.

Step 2: Define the first integration's schedule

Next, define the integration’s replication schedule. You can use any of Stitch’s supported replication scheduling methods: Replication Frequency, Anchor Scheduling, or Advanced Scheduling.

When finished, save the integration.

Step 3: Set tables to replicate

After you’ve saved the first integration, you’ll be prompted to set tables (and columns, if supported) to replicate.

Select the tables and columns you want to replicate according to the schedule you defined in Step 2.

Step 4: Repeat steps 1-3

Lastly, repeat steps 1-3 to create a second integration, define its replication schedule, and set tables to replicate. This will allow you to select a different table or set of tables and replicate them on a schedule separate from the first integration.

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.