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.
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.
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.
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.
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.
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.
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.
Seven parts of AWS matter to this integration. Two are HubSpot's own connectors to scope around; five carry the custom build.
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.
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.
Runs SQL over a secure HTTP endpoint with no persistent connection. Works with Serverless workgroups and provisioned clusters in a VPC.
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.
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.
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.
Redshift limits what the integration's role can see before a row leaves the warehouse.
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.
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.
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.
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.
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.
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.
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.
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.
Create the custom properties, the Product Account custom object, association labels and custom event definitions in a HubSpot sandbox.
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.
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.
Build score-driven lists, alerts and views with notifications paused, run two weeks in parallel, then switch on.
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 field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| HubSpot → Redshift tables | ||||
| hubspot.contacts | hs_object_id + agreed properties | Contact | HS → RS | MERGE on hs_object_id; lastmodifieddate drives incremental pulls. |
| hubspot.companies | hs_object_id + agreed properties | Company | HS → RS | Same pattern; domain kept for joins. |
| hubspot.deals | dealstage, amount, closedate, pipeline | Deal | HS → RS | Owner and pipeline names resolved to labels. |
| hubspot.line_items | name, quantity, price, hs_product_id | Line item | HS → RS | Joined to deals by association. |
| hubspot.engagements_* | calls, emails, meetings, notes, tasks | Engagement objects | HS → RS | One table per type. Body text optional; governance decides. |
| hubspot.associations | from ID, to ID, association label | All objects in scope | HS → RS | Lets SQL join contacts, companies and deals. |
| hubspot.property_history | property, value, timestamp, source | Contact, Company, Deal | HS → RS | Kept over time, unlike a snapshot export. |
| hubspot.sensitive_fields | sensitive data properties | Contact | HS → RS | Only if approved; masked in Redshift by role. |
| Scores & metrics → HubSpot | ||||
| account_scores.health_score | rs_health_score | Company | RS → HS | Overwrites each run. Owned by Redshift. |
| lead_scores.propensity_score | rs_propensity_score | Contact | RS → HS | Feeds lists and lead routing. |
| ltv.predicted_ltv | rs_predicted_ltv | Company | RS → HS | Currency. |
| product_usage.active_users_30d | rs_active_users_30d | Company | RS → HS | Rolled up per account in Redshift. |
| product_usage.last_active_at | rs_last_active_at | Contact | RS → HS | Written only when newer than the HubSpot value. |
| product_usage.plan_tier | rs_plan_tier | Company | RS → HS | Dropdown values agreed in discovery. |
| score_runs.model_version | rs_model_version | Company | RS → HS | Shows which model produced the score. |
| Modeled records & associations | ||||
| product_accounts | Product Account | Custom object | RS → HS | One record per product account or workspace. |
| account_to_company | Product Account ↔ Company | Association | RS → HS | Labelled association. |
| user_to_account | Contact ↔ Product Account | Association | RS → HS | Role on the account as the label. |
| subscriptions | Subscription custom object or Deal | Custom object | RS → HS | Choice confirmed in discovery. |
| product_milestones | Custom event: Product milestone | Contact | RS → HS | Timeline entry, e.g. first project created. |
| Identity & keys | ||||
| hubspot_id column | hs_object_id | Contact, Company | ↔ Both | Written back to Redshift after create, so later runs match on ID. |
| Contact | ↔ Both | Fallback match key. | ||
| domain | domain | Company | ↔ Both | Fallback match key for companies. |
| account_key | rs_account_key | Company | RS → HS | Unique property; the warehouse's account ID. |
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.
| Topic | Redshift | HubSpot |
|---|---|---|
| Access model | IAM 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. |
| Interfaces | Redshift 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. |
| Authentication | Temporary 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 limits | Results 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. |
| Freshness | Runs 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 cost | Serverless 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 data | Row-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. |
Severity reflects impact on the SOW, not technical difficulty alone.
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.
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.
Scoring every record every night can mean hundreds of thousands of updates. The integration sends only values that changed, in batches of 100.
Serverless bills while queries run and provisioned clusters bill while running. CC batches reads and agrees the run frequency in the SOW.
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.
Each cluster, workgroup or account needs its own role and configuration. Only production writes to the live HubSpot portal.
Account health and buying propensity sit on the company and contact record, so owners see risk and intent without opening a dashboard.
Active users, last activity and plan tier trigger onboarding, expansion and save plays in HubSpot workflows.
HubSpot engagements, pipeline and history join billing and product data in Redshift, so the data team can measure what actually drives revenue.
Key product events appear on the contact timeline as custom events, next to emails, meetings and deals.
Lists built from rs_ properties stay current as the models rerun, with no manual exports.
Predicted lifetime value lands in HubSpot reports beside original source and campaign data.
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.
All custom properties use the rs_ prefix in a Redshift property group. Values are computed in the warehouse; HubSpot stores the result.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| rs_account_key | Warehouse Account Key | Company | Single-line text | Warehouse account ID; unique |
| rs_health_score | Health Score | Company | Number | Account health model |
| rs_propensity_score | Propensity Score | Contact | Number | Buying propensity model |
| rs_predicted_ltv | Predicted LTV | Company | Number (currency) | Lifetime value model |
| rs_active_users_30d | Active Users (30 days) | Company | Number | Distinct active users, rolled up |
| rs_last_active_at | Last Product Activity | Contact | Date and time picker | Latest product event |
| rs_plan_tier | Plan Tier | Company | Dropdown | Current product plan |
| rs_usage_trend | Usage Trend | Company | Dropdown | Rising, flat or falling |
| rs_model_version | Score Model Version | Company | Single-line text | Model that produced the scores |
| rs_last_synced | Last Warehouse Sync | Company | Date and time picker | Set on each successful write |
| rs_product_account_id | Product Account ID | Product Account | Single-line text | Product account key; unique |
| rs_seats | Seats | Product Account | Number | Licensed seats on the account |
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.
Based on public documentation from AWS and HubSpot. Cluster or workgroup setup, AWS accounts and table names are confirmed with the client's data team during discovery.
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.
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.
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.
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.
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.