topic Can Qlik Replicate load multiple source tables (same schema) into one target table/folder? in Qlik Replicate

Can Qlik Replicate load multiple source tables (same schema) into one target table/folder?

gideeeh — Thu, 11 Dec 2025 07:20:30 GMT

Hi,

In my source system, there are several tables that share the exact same schema, for example something like:

table_A1
table_A2
table_A3

When I select them in a Replicate task, each table is written to its own target folder/table in S3.

Question:

Is there any supported method in Replicate to combine these tables so that all rows land in one target table or one S3 folder (i.e., a merged output)?
If this is not supported, could someone point me to the specific documentation or limitation that states Replicate does not allow merging multiple physical source tables into a single target object?

Thanks!

Re: Can Qlik Replicate load multiple source tables (same schema) into one target table/folder?

SachinB — Thu, 11 Dec 2025 08:03:16 GMT

Hello @gideeeh

Qlik Replicate does not support merging multiple physical source tables into a single target table or a single target folder. Each source table defined in the task is treated as an individual replication entity, and Replicate requires a one-to-one mapping between a source table and a target table

Because of this architectural design, Replicate cannot combine or union data from multiple source tables during replication.

You can find the limitation in the guide list.

Replicate-Setup-and-User-Guide

Regards,
Sachin B

Re: Can Qlik Replicate load multiple source tables (same schema) into one target table/folder?

john_wang — Thu, 11 Dec 2025 08:13:36 GMT

Hello @gideeeh ,

If you mean loading the tables during Full Load, then yes, there are ways to handle that. The simplest approach is to create a VIEW on the source side that combines those tables, and then load the view’s data into S3.

Hope this helps.

John.

Re: Can Qlik Replicate load multiple source tables (same schema) into one target table/folder?

Jon_Donker — Thu, 18 Dec 2025 22:10:27 GMT

If the target database is a RDMS; it might be possible to land the data into their individual tables on the destination and the build triggers off these tables to copy the action into a single "merged" table