Qlik Stitch: Data Loading Error "The data for this table would result in more than 1,600 columns"

[Mohammed_Messaoudi]

You may be experiencing the following data loading error when connecting the HubSpot Integration to a destination:

"The data for this table would result in more than 1,600 columns" 

Resolution

To resolve this issue and bring your integration back online, follow the steps below. This process applies to any affected table (for example, contacts, deals, companies tables)

1. Pause the Integration
   Start by pausing the HubSpot integration in Stitch to prevent new data from syncing during the fix.
2. Update Field Selection
   • Navigate to the affected table (for example: contacts, deals) in the Stitch UI.
   • Deselect the main properties field.
   • Manually select only the individual fields you need — these will be listed as properties_<field_name>
3. Drop the Affected Table in the destination( Redshift as an example)

   In your database, drop the oversized table to allow Stitch to recreate it with the updated schema.

4. Reset the Table in Stitch
   • Go to Tables to Replicate > [table_name].
   • Click on Table Settings.
   • Choose Reset Table, and confirm the prompt.

   This will trigger a rebuild of the table with the selected fields only.

5. Unpause the Integration

   Once everything is updated, unpause the integration to resume syncing.

Cause

This error message indicates that the data being replicated into your destination exceeds the 1600-column limit during loading imposed by the warehouse (e.g, Redshift) and it most commonly arises when Stitch attempts to de-nest complex fields like properties from HubSpot tables, such as: contacts, deals,companies

These properties fields act as containers for a large number of individual fields. When de-nested, they can generate a lot of columns, especially if:

• The top-level properties field is selected, and

• Individual properties_<field_name> fields are also selected

Even if you deselect some individual fields, selecting the main properties field overrides those exclusions, and all properties are still replicated. This can push your table schema past the 1600-column limit.

Environment

Talend Cloud