A HubSpot Elite Solutions Partner built to help organizations unify strategy, systems, and execution. We design HubSpot systems that scale.

See how we've solved complex HubSpot challenges across migrations, integrations, CMS, automation, and optimization.

Join a team building smarter HubSpot systems. We value strategic thinkers who move proactively, care about quality, and want to do meaningful work.

Integration

HubSpot <> Redshift Integration

Powered by Commercient
Integration Assessment
Integration Assessment · Data Warehouse

Amazon Redshift × HubSpot

How an Amazon Redshift warehouse and HubSpot can exchange data in both directions: HubSpot records, engagements and events kept in Redshift tables the analytics team can query, and the scores, product usage and lifetime value computed in Redshift written back to the HubSpot records people act on.

Redshift Data APICOPY and UNLOAD via S3IAM roles and Secrets ManagerEventBridge and LambdaServerless or provisionedBoth directions
Platform ownerAmazon Web Services
Integration typeHubSpot connectors plus custom build on the Redshift Data API
Primary directionBoth: Redshift ↔ HubSpot
FeasibilityStrong fit
API accessOpen API
01 — Summary

Does Redshift integrate with HubSpot?

Many companies on AWS keep their customer analytics in Amazon Redshift: product events, billing, support and web data in one warehouse. HubSpot is where marketing, sales and service act on those customers. This assessment covers how the two share data.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. The Redshift Data API is documented publicly. The client's AWS admins create the IAM roles and database grants.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

Redshift exposes SQL over a secure HTTP endpoint and loads in bulk through S3, so HubSpot can act on what the warehouse computes, and the warehouse can keep a working copy of HubSpot.

Campaign Creators assessment

HubSpot has two native options, both on Data Hub Enterprise. Its Redshift for Data Studio connector brings Redshift tables into Data Studio datasets that feed reports, workflows and CRM records (Redshift → HubSpot). Data Out for Amazon Redshift, in beta, exports HubSpot objects, associations, property history and events to Redshift through an S3 bucket as full snapshots on a set schedule (HubSpot → Redshift). The custom case is narrower: incremental loads that keep history and land in one table per object, sensitive data properties the export leaves out, portals without Data Hub Enterprise, computed tables written to specific objects and custom objects under agreed write rules and associations, near-real-time triggers, several clusters or AWS accounts, and governance through Redshift's row-level security, dynamic data masking and Lake Formation. CC builds it on the Redshift Data API, COPY and UNLOAD, and HubSpot's CRM APIs.

Scorecard
API accessOpen, IAM-based
Public docsExtensive
Compute costPlan per run
Build complexityModerate

Ratings are CC judgments from AWS's public documentation and HubSpot's knowledge base. Cluster or workgroup setup, AWS accounts and the tables in scope are confirmed with the client's data team during discovery.

Strength

No database connections to manage

The Redshift Data API runs SQL over HTTPS and returns results asynchronously, signed with IAM or a Secrets Manager secret. Bulk data moves through S3 with COPY and UNLOAD.

Plan for

Redshift has no built-in change feed

Outbound reads rely on an updated-at column or a change table in each model. CC agrees that pattern with the data team so only changed rows go to HubSpot.

Gate

One writer per table and per field

HubSpot's Data Out export and its Data Studio connector may already cover some objects and fields. The client decides which process owns each one before the build starts.

02 — API modules

Which Redshift APIs does the integration use?

Seven parts of AWS matter to this integration. Two are HubSpot's own connectors to scope around; five carry the custom build.

Starting point

HubSpot's Redshift for Data Studio

Built by HubSpot · Data Hub Enterprise

HubSpot's connector brings Redshift tables into Data Studio datasets. Datasets can drive reports and workflows, and can create or update CRM records against a match key.

  • Direction: Redshift → HubSpot
  • Up to 200 columns per warehouse source
  • Joins and calculated fields use HubSpot Credits; a direct sync to the CRM does not
Scope decision

HubSpot's Data Out for Amazon Redshift

Built by HubSpot · Data Hub Enterprise · beta

Exports HubSpot objects, records, property history, associations and events to Redshift. HubSpot stages Parquet files in an S3 bucket the client chooses and loads them into a HubSpot-managed schema.

  • Direction: HubSpot → Redshift, full snapshot each run
  • Object data shares one table; no previous snapshots kept
  • Sensitive data not supported; one recurring sync per object
Core

Redshift Data API

ExecuteStatement · BatchExecuteStatement

Runs SQL over a secure HTTP endpoint with no persistent connection. Works with Serverless workgroups and provisioned clusters in a VPC.

  • Results up to 500 MB (gzip), kept 24 hours
  • BatchExecuteStatement runs as one transaction by default
  • Named parameters keep queries safe
Core

COPY and UNLOAD via S3

Bulk load and export

HubSpot data lands in S3 as files and loads with COPY into a staging table, then merges into the target. Large outbound sets leave Redshift with UNLOAD to Parquet.

  • UNLOAD to CSV, JSON or Parquet
  • IAM_ROLE authorizes access to the bucket
  • MANIFEST lists every file written
Core

IAM roles and Secrets Manager

Temporary credentials · secret ARN

The integration signs in with an IAM role, using temporary credentials or a database user stored in Secrets Manager. No passwords pass through API calls.

  • redshift-serverless:GetCredentials for workgroups
  • GetClusterCredentialsWithIAM for clusters
  • Separate roles for read and write
Core

EventBridge and Lambda

Schedules and statement events

EventBridge starts each run on a schedule, and the Data API can emit an event when a statement finishes. Lambda functions run the steps between Redshift, S3 and HubSpot.

  • WithEvent sends FINISHED, FAILED or ABORTED
  • Events delivered on a guaranteed basis
  • Each step retried on its own
Governance

Governance controls

RLS · dynamic data masking · Lake Formation

Redshift limits what the integration's role can see before a row leaves the warehouse.

  • Row-level security limits which accounts sync
  • Dynamic data masking hides personal data at query time
  • Lake Formation governs shared data across accounts
03 — Framework

How does the Redshift HubSpot integration work?

A CC-built integration layer runs in the client's AWS account. Outbound from HubSpot, it pulls changed records, writes them to S3 and loads them into Redshift. Inbound to HubSpot, a scheduled run reads changed rows from agreed views, applies the write rules and updates HubSpot in batches.

Amazon Redshift
Model tables and viewsscores, usage, LTV, product events
Change columnsupdated-at watermark per model
S3 stagingCOPY in, UNLOAD out
GovernanceRLS, masking, IAM roles
CC integration layer
HubSpot extractorchanged records → S3 → COPY → MERGE
Change readerData API by watermark
Identity resolverHubSpot ID · email · domain · account key
Write ruleswhich object, which field, when
HubSpot writerbatch upserts, associations, replay
HubSpot
Contacts and companiesscores, usage, lifetime value
Deals and custom objectsproduct accounts, subscriptions
Associationslabelled links between records
Custom eventsproduct milestones on the timeline
Lists, workflows & reportssegments, alerts and views
Redshift → HubSpot (scores, usage and modeled records)HubSpot → Redshift (objects, engagements, associations and events, incremental)
Principle

HubSpot owns the customer record

Contacts, companies, deals and owners are created and edited in HubSpot. The warehouse adds computed fields to those records and never creates a second copy of a person.

Principle

The warehouse owns the math

Scores, lifetime value and usage rollups are computed in Redshift, where the data team can test and version them. HubSpot receives the result, not the raw events.

Principle

Runs in the client's AWS account

Credentials stay in Secrets Manager or IAM, data moves through the client's own S3 bucket, and the role sees only what the data team grants.

04 — Process

What does Redshift HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. HubSpot data lands in Redshift first, so the data team can key every score on HubSpot IDs.

1

Discovery & access

List the clusters or Serverless workgroups, AWS accounts, schemas and tables in scope, the HubSpot subscription, and whether HubSpot's Data Out or Data Studio connector is in use. Create IAM roles, the S3 staging bucket and secrets.

Gate to next phaseAccess confirmed and table inventory signed
2

Ownership & write rules

For every HubSpot field the warehouse feeds, agree the source column, the target object, when it may overwrite, and the match key. Agree which HubSpot data may land in Redshift.

Gate to next phaseSigned write-rule matrix and data approval
3

Landing design

Design one Redshift table per HubSpot object, engagement type and association, with history columns, plus the outbound views with updated-at columns, row-level security and masking.

Gate to next phaseSchema and permissions approved by the data team
4

HubSpot data model

Create the custom properties, the Product Account custom object, association labels and custom event definitions in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build

Build the extractor (HubSpot → S3 → COPY → MERGE), the change reader (views → HubSpot), the writer with an error replay queue, and the EventBridge schedules and Lambda steps.

Gate to next phaseBoth directions running in sandbox with clean reconciliation
6

Backfill

Load HubSpot history into Redshift through S3, then send the first full set of scores and usage values to HubSpot, paced under HubSpot's API limits.

Gate to next phaseRow counts reconcile in both directions within an agreed tolerance
7

Workflows, parallel run & launch

Build score-driven lists, alerts and views with notifications paused, run two weeks in parallel, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the Redshift HubSpot integration sync?

Redshift table and column names below are examples; the client's data team names the real tables in discovery. HubSpot names are HubSpot's documented properties or the rs_ custom properties in the schema below.

Redshift fieldHubSpot propertyObjectDirectionNotes
HubSpot → Redshift tables
hubspot.contactshs_object_id + agreed propertiesContactHS → RSMERGE on hs_object_id; lastmodifieddate drives incremental pulls.
hubspot.companieshs_object_id + agreed propertiesCompanyHS → RSSame pattern; domain kept for joins.
hubspot.dealsdealstage, amount, closedate, pipelineDealHS → RSOwner and pipeline names resolved to labels.
hubspot.line_itemsname, quantity, price, hs_product_idLine itemHS → RSJoined to deals by association.
hubspot.engagements_*calls, emails, meetings, notes, tasksEngagement objectsHS → RSOne table per type. Body text optional; governance decides.
hubspot.associationsfrom ID, to ID, association labelAll objects in scopeHS → RSLets SQL join contacts, companies and deals.
hubspot.property_historyproperty, value, timestamp, sourceContact, Company, DealHS → RSKept over time, unlike a snapshot export.
hubspot.sensitive_fieldssensitive data propertiesContactHS → RSOnly if approved; masked in Redshift by role.
Scores & metrics → HubSpot
account_scores.health_scorers_health_scoreCompanyRS → HSOverwrites each run. Owned by Redshift.
lead_scores.propensity_scorers_propensity_scoreContactRS → HSFeeds lists and lead routing.
ltv.predicted_ltvrs_predicted_ltvCompanyRS → HSCurrency.
product_usage.active_users_30drs_active_users_30dCompanyRS → HSRolled up per account in Redshift.
product_usage.last_active_atrs_last_active_atContactRS → HSWritten only when newer than the HubSpot value.
product_usage.plan_tierrs_plan_tierCompanyRS → HSDropdown values agreed in discovery.
score_runs.model_versionrs_model_versionCompanyRS → HSShows which model produced the score.
Modeled records & associations
product_accountsProduct AccountCustom objectRS → HSOne record per product account or workspace.
account_to_companyProduct Account ↔ CompanyAssociationRS → HSLabelled association.
user_to_accountContact ↔ Product AccountAssociationRS → HSRole on the account as the label.
subscriptionsSubscription custom object or DealCustom objectRS → HSChoice confirmed in discovery.
product_milestonesCustom event: Product milestoneContactRS → HSTimeline entry, e.g. first project created.
Identity & keys
hubspot_id columnhs_object_idContact, Company↔ BothWritten back to Redshift after create, so later runs match on ID.
emailemailContact↔ BothFallback match key.
domaindomainCompany↔ BothFallback match key for companies.
account_keyrs_account_keyCompanyRS → HSUnique property; the warehouse's account ID.
06 — Auth & API

How are authentication and API limits handled?

Redshift limits below come from AWS's Data API documentation. Values AWS does not publish as fixed numbers, such as cost per run, are confirmed with the client's data team.

TopicRedshiftHubSpot
Access modelIAM roles in the client's AWS account, created by the client's admins. Database grants, row-level security and masking decide what the role can see.Private app in the client portal, scoped per object. Custom objects and custom events need an Enterprise hub. HubSpot's Redshift connectors need Data Hub Enterprise; the custom build does not.
InterfacesRedshift Data API (REST, no persistent connection), COPY and UNLOAD through S3, EventBridge for schedules and statement events, Lambda for the steps.REST APIs: CRM objects, properties, associations, custom events, batch upserts.
AuthenticationTemporary IAM credentials (workgroup or cluster) or a database user in Secrets Manager referenced by secret ARN. IAM Identity Center is also supported.Private app access token or OAuth 2.0 public app, stored in Secrets Manager.
Query limitsResults up to 500 MB after gzip and kept 24 hours; statements up to 200 KB; queries up to 24 hours; 500 active queries per cluster or workgroup.Per-10-second burst and daily limits by subscription tier; batch endpoints take up to 100 records per call.
FreshnessRuns on an EventBridge schedule; the Data API can emit an event when each statement finishes. Change detection uses updated-at columns agreed with the data team.Writes are immediate. HubSpot changes are read by last-modified date.
Compute costServerless bills in RPU-hours per second while queries run, with a 60-second minimum; provisioned clusters bill while not paused. Cost per run confirmed with the data team.A direct warehouse-to-CRM sync in Data Studio uses no HubSpot Credits; joins and calculated fields there do.
Sensitive dataRow-level security, column-level security and dynamic data masking on the integration's role; S3 staging encrypted server-side.Sensitive data properties on Enterprise; field-level permissions by team.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

No built-in change feedHigh

Redshift does not publish row changes on its own. Each outbound model needs an updated-at column or a change table, agreed with the data team, or every run resends everything.

Overlap with HubSpot's own connectorsHigh

Data Out and the Data Studio connector may already cover some objects and fields, and Data Out allows each object in only one recurring sync. A signed ownership matrix gives every table and field one writer.

Large nightly pushes hit HubSpot limitsMedium

Scoring every record every night can mean hundreds of thousands of updates. The integration sends only values that changed, in batches of 100.

Warehouse cost per runMedium

Serverless bills while queries run and provisioned clusters bill while running. CC batches reads and agrees the run frequency in the SOW.

IAM, bucket and network setup needs an adminMedium

Roles, the staging bucket, secrets and any VPC rules are set by the client's AWS admins. Make them a client-owned dependency in the SOW, with a date.

Several clusters or AWS accountsLow

Each cluster, workgroup or account needs its own role and configuration. Only production writes to the live HubSpot portal.

Opportunities in HubSpot

Health and propensity scores where reps workHigh value

Account health and buying propensity sit on the company and contact record, so owners see risk and intent without opening a dashboard.

Product usage in workflowsHigh value

Active users, last activity and plan tier trigger onboarding, expansion and save plays in HubSpot workflows.

Full-funnel analysis in RedshiftHigh value

HubSpot engagements, pipeline and history join billing and product data in Redshift, so the data team can measure what actually drives revenue.

Product milestones on the timelineMedium value

Key product events appear on the contact timeline as custom events, next to emails, meetings and deals.

Model-driven segmentsMedium value

Lists built from rs_ properties stay current as the models rerun, with no manual exports.

Lifetime value by source and campaignMedium value

Predicted lifetime value lands in HubSpot reports beside original source and campaign data.

Rollout order

Start with HubSpot's connectors, then build what they leave out.

Both directions share one identity map. Where the portal has Data Hub Enterprise, HubSpot's own connectors carry what they cover, and the custom build adds the rest without a second writer.

  1. Decide which objects HubSpot's Data Out export carries and which the custom build carries incrementally.
  2. Land HubSpot objects, engagements and associations in Redshift, keyed on HubSpot IDs.
  3. Write the first computed table, usually account health or product usage, to company records.
  4. Add product accounts, associations and milestone events once the first scores are trusted.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the rs_ prefix in a Redshift property group. Values are computed in the warehouse; HubSpot stores the result.

Internal nameLabelObjectTypeSource / logic
rs_account_keyWarehouse Account KeyCompanySingle-line textWarehouse account ID; unique
rs_health_scoreHealth ScoreCompanyNumberAccount health model
rs_propensity_scorePropensity ScoreContactNumberBuying propensity model
rs_predicted_ltvPredicted LTVCompanyNumber (currency)Lifetime value model
rs_active_users_30dActive Users (30 days)CompanyNumberDistinct active users, rolled up
rs_last_active_atLast Product ActivityContactDate and time pickerLatest product event
rs_plan_tierPlan TierCompanyDropdownCurrent product plan
rs_usage_trendUsage TrendCompanyDropdownRising, flat or falling
rs_model_versionScore Model VersionCompanySingle-line textModel that produced the scores
rs_last_syncedLast Warehouse SyncCompanyDate and time pickerSet on each successful write
rs_product_account_idProduct Account IDProduct AccountSingle-line textProduct account key; unique
rs_seatsSeatsProduct AccountNumberLicensed seats on the account
09 — Scope builder

Interactive scope builder

Choose the data and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
Redshift × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Redshift HubSpot integration FAQ

Does Redshift integrate with HubSpot?

Yes. On Data Hub Enterprise, HubSpot's Redshift for Data Studio connector brings Redshift tables into HubSpot, and Data Out for Amazon Redshift (in beta) exports HubSpot data to Redshift through S3. Campaign Creators covers what those don't with a custom build on the Redshift Data API, COPY and UNLOAD, and HubSpot's CRM APIs.

What data syncs between Redshift and HubSpot?

HubSpot records, associations, engagements and events land in Redshift tables the analytics team can query, with history kept. Scores, product usage and lifetime value computed in Redshift are written back to HubSpot contacts, companies, deals and custom objects under agreed write rules.

Which system owns which data?

Each table and each field has one writer. The client decides which objects HubSpot's own connectors cover and which the custom build covers, and every value written to HubSpot follows a signed write rule so warehouse data never overwrites a rep's edit unless agreed.

What does setting up the Redshift HubSpot integration involve?

Seven phases, each closed by a client sign-off: discovery and access, ownership and write rules, landing design for the Redshift tables, the HubSpot data model, the build, a backfill, and a parallel run before workflows are switched on.

How long does the integration take and what does it cost?

Timeline and cost depend on the tables and objects in scope, how many flows HubSpot's connectors already cover, and the cluster or workgroup setup. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.

Ready to Get More From HubSpot?

Whether you’re implementing HubSpot, optimizing what you already have, connecting systems, or scaling your customer experience, we’ll help you figure out the right next step.