Sync data from
Amazon Redshift to Salesforce
Connect your data from Amazon Redshift to Salesforce with Hightouch. No APIs, no months-long implementations, and no CSV files. Just your data synced forever.
Trusted by data teams at
Integrate your data in 3 easy steps
Add your source and destination
Connect to 15+ data sources, like Amazon Redshift, and 140+ destinations, like Salesforce.
Define your model
Use SQL or select an existing dbt or Looker model.
Sync your data
Define how fields from your model map to Salesforce, and start syncing.
Model your Amazon Redshift data using any of these methods
dbt Model Selector
Sync directly with your dbt models saved in a git.
Query using looks. Hightouch turns your look into SQL and will pull from your source.
Create and Edit SQL from your browser. Hightouch supports SQL native to Amazon Redshift.
Select available tables and sheets from Amazon Redshift and sync using existing views without having to write SQL.
For less technical users, pass traits and audiences from Amazon Redshift using our visual segmentation builder.
Where can you sync your Amazon Redshift data in Salesforce
Represents an individual account, which is an organization or person involved with your business (such as customers, competitors, and partners). Use the
accountobject to query and manage accounts in your org.
Represents a contact, which is a person associated with an account. Use the
contactobject to manage to manage individual people who are associated with an account.
Represents a prospect or lead. Use the
leadobject to manage leads in your org.
Represents an opportunity, which is a sale or pending deal. Use the
opportunityobject to to manage information about a sale or pending deal.
Represents the association between a campaign and either a lead or a contact. Use the
campaignMemberobject to manage campaign members in your org.
Represents a business activity such as making a phone call. Use the
taskobject to manage to-do items for your org.
Represents a case, which is a customer issue or problem. Use the
caseobject to manage customer cases for your org.
Represents an item of commercial value, such as a product sold by your company or a competitor, that a customer has purchased. Use the
assetobject to manage assets for your org.
userin the organization. Use this object to query information about users and to provision and modify users in your organization. Unlike other objects, the records in the User table represent actual users—not data owned by users.
Custom Salesforce Objects
We support custom Salesforce objects to ensure our integration supports all your organization’s unique workstreams.
Does this integration support in-warehouse planning?
Yes, if you integerate Amazon Redshift and Salesforce using Hightouch, in-warehouse planning is supported.
Great, but what is in-warehouse planning?
Between every sync, Hightouch notices any and all changes in your data model. This allows you to only send updated results to your destination (in this case Salesforce). With the baseline setup, Hightouch picks out only the rows that need to be synced by querying every row in your data model before diffing using Hightouch’s infrastructure.
The issue here is this can be slow for large models.
Warehouse Planning allows Hightouch to do this diff directly in your warehouse. Read more on how this works here.
Why is it valuable to sync Amazon Redshift data to Salesforce?
Salesforce is the backbone of your sales org. It's where you manage all of your contacts, accounts, and deals. The problem is that most of your CRM data has to be manually input by individual sales reps, so it doesn't show you an accurate 360-degree view of your customer. You only have access to basic information and historical interactions.
All of your Salesforce data, in addition to the rich behavioral data captured through your app/website already, exists in Amazon Redshift. Most of the time, this includes core metrics your data team has defined around lifetime value, workspaces, subscriptions, playlists, average order value, last login date, etc. There's a high chance you're probably even consuming this data in a dashboard, and your sales reps can't answer key questions like:
- Which accounts have the highest lifetime value?
- Which users have the highest utilization in our product?
- When did user X last log in to the app?
- Which leads/accounts should I be prioritizing?
- Which accounts are at risk of churning?
- What is the average order value of account X?
Your sales team doesn't want to hop back and forth between your various SaaS tools to answer these questions. They want to take action in Salesforce, and that means enriching your CRM with data directly from your warehouse.
Why should you use reverse ETL to connect Amazon Redshift and Salesforce data?
Conventionally moving data from Snowflake to Salesforce meant downloading ad hoc CSV files and uploading them manually or forcing your data team to integrate with the Salesforce API and build and maintain custom pipelines. In reality, CSVs are not scalable, and in-house data pipelines and custom scripts break constantly.
Other point-to-point solutions create a weave complex web of pipelines to and from various SaaS applications and customer data platforms (CDPs), forcing you to pay for another layer of storage in addition to your data warehouses.
Reverse ETL solutions like Hightouch query against Snowflake and sync that data directly to Salesforce. You don't have to worry about CSVs or APIs. You can leverage your existing tables, data models, and audience segments. All you have to do is define your data and map it to the appropriate columns in Salesforce. You can schedule your syncs to run manually or even trigger them to run sequentially based on criteria that you define.
Hightouch automatically diffs data between syncs to ensure your only ever syncing the freshest data, and if any rows fail, Hightouch will automatically retry them later. A live debugger lets you analyze your API payload requests/responses and failed runs in real-time.
How to integrate Redshift and Salesforce
We've outlined the 5 most common options you have to sync your Redshift data to Salesforce. Using one of these options will allow your organization to move from only your data team having access to view and use data to having unblocked marketing and business teams.
Option 1: Reverse ETL (Hightouch)
Reverse ETL is often thought of as the solution to this last-mile-analytics problem. Reverse ETL tools like Hightouch run on top of Redshift and don’t actually ever store any of your data. With Hightouch all you have to do is define your data in Redshift using SQL or your own existing data models.
With Hightouch's native integrations, you can sync your data in Redshift directly to Salesforce giving you access to real-time data. You can even map your columns to any custom object, enabling you to focus on even more business outcomes. You can actually test this out yourself by following these steps.
Step 1: Connect to Your Data Source
Step 2: Connect Hightouch to your destination
Step 3: Create a data model or leverage an existing one
You can use SQL to define your data directly in the Hightouch UI or even leverage your existing data models.
Step 4: Choose Your Primary Key
With Hightouch you can map on any unique key, not just users and accounts.
Step 5: Create Your Sync
Once you have created your sync, you simply have to choose the appropriate columns and map them to the fields in your end destination.
Step 6: Schedule Your Sync
Once your sync is created you can run it manually, define a set interval, or schedule it to run after a dbt job is completed.
The first integration with Hightouch is completely free so you can actually get started today. If you want to learn more about Reverse ETL, download our guide.
Option 2: Manual CSV Files
Downloading and uploading CSV files is one of the easiest ways to move data from Redshift to Salesforce. Doing this is not the most efficient use of your time though because it's not a one-time event. Every time sales or marketing asks you for a specific data set you have to manually download it.
In addition to this, data stored in a CSV file becomes stale really quickly. Ideally want to have a continuous flow between Redshift and Salesforce so you don’t have to worry about whether or not your business teams have access to the data they need to do their jobs.
Option 3: Custom Integrations
Building an in-house data pipeline directly to Salesforce is another way to go about moving your data from Redshift to Salesforce, but this can be challenging to do as Salesforce and Redshift's APIs are constantly changing, which means you have to check for upstream or downstream changes on a regular basis to ensure your data is flowing properly.
Additionally building and maintaining your own data pipeline is not only time-consuming, but it's also extremely resource-intensive, and depending on the scale of data that you are trying to move it becomes even more challenging.
Option 4: iPaaS (Integration Platform as a Service)
Integration platforms like Tray or Workato let you build intuitive workflows to move data from one system to another, but these solutions are really designed to automate tasks and improve efficiency.
If your use case is simple solutions like this can be a great option, but as soon as any complexity gets thrown into the mix, you will find yourself buried in complex if/then statements with multiple dependencies in each individual step. Managing these workflows can be equally as challenging as maintaining your own in-house data pipeline.
Option 5: CDPs (Customer Data Platform)
For many years, CDPs have been the go-to solution to tackle the problem of democratizing the data that exists in your warehouse because they consolidate all of your customer data into another centralized platform. The problem is, CDPs don’t mesh with your existing technology stack because they create a second source of truth.
CDPs also own your data because it is no longer stored in your cloud environment. This can make things difficult from a compliance standpoint. Time-to-value is also not immediate because CDPs can easily take over a year to implement. They are also extremely rigid when it comes to object mappings. You can only map columns to objects like users and accounts. In reality, your business is usually much more complex.
Push lead info from your warehouse into Salesforce CRM to enable executives to go after the right accounts
Push product data to enable account managers to know what actions are being taken in the app
Reduce churn by syncing health scores and churn events to Salesforce CRM for account managers to track
Why sync data from
Amazon Redshift to Salesforce?
Salesforce is the single source of truth for your sales team, but it only shows one view of your customer. In reality, all of your product usage data, event data, and custom audiences live in Redshift. To truly have a 360-degree view of your customer, your sales team needs access to this information. With the proper data in their hands, your sales team can remove the guesswork and start targeting your highest value leads.
About Amazon Redshift
Amazon Redshift is a fully managed, petabyte-scale data warehouse service in the cloud. It is built on Amazon Web ServicesLearn more about Amazon Redshift
Salesforce is a cloud computing service as a software (SaaS) company that specializes in customer relationship management (CRM). Salesforce's services allow businesses to use cloud technology to better connect with customers, partners and potential customers.Learn more about Salesforce
Other Amazon Redshift Integrations
Other Salesforce integrations
Hightouch Playbooks: Best practices to leverage reverse ETL
Read more about Salesforce
Read more about Hightouch
What is Operational Analytics & Why You Should Use It
Operational Analytics shifts the focus from simply understanding data to taking action on it in the tools that run business processes. Instead of using dashboards to make decisions, Operational Analytics is focused on turning insights into action – automatically.Read
Activate data to any of your marketing and advertising tools
This might be one of the greatest inventions for technical marketers since the advent of legacy CDPs back in 2015.
Head of Marketing Technology
Your data is always secure
SOC 2 Type 2 compliant
Your data stays secure, available, and confidential. To see our report, .
If you’re in the EU, your data is only processed on EU data centers.
Healthcare companies like ThirtyMadison, Chapter Health, and Headway trust Hightouch.
To see our DPA (Data Processing Addendum), .
increase in return on ad spend
improvement in email engagement
lift in customer acquisition