8 posts tagged with "Data Integration"

A Salesforce Google Sheets integration can send CRM data to a spreadsheet for reporting and return reviewed changes to Salesforce. The safest design does not let both systems overwrite the same fields whenever they want. It keeps a stable Salesforce ID on every row, limits which fields Sheets can change, and orders the two sync directions so an outbound refresh cannot erase an unprocessed edit.

This guide compares the main connector, automation, and API approaches. It then shows how to build a scheduled two-way Salesforce and Google Sheets workflow with Supaflow using separate outbound and writeback pipelines.

Moving the AWS Cost and Usage Report to Snowflake answers a question that Cost Explorer cannot answer alone: does the revenue from each customer justify the cloud cost required to serve them?

The practical architecture is straightforward. Export AWS Cost and Usage Report 2.0 (CUR 2.0) to Amazon S3 as Parquet, load the files into Snowflake, sync revenue data from Stripe, and add customer and segment context from Salesforce. A shared customer identity model then turns three disconnected systems into customer-level cost, revenue, and margin analysis.

AWS Data Exports -> S3 Parquet ---\
                                    \
Stripe ------------------------------> Supaflow -> Snowflake -> dbt -> Margin dashboard
                                    /
Salesforce ------------------------/

This guide explains the pipeline, the allocation decisions that matter, and the Snowflake model needed to calculate gross margin without hiding shared or unattributed costs.

In other words, moving AWS billing data to Snowflake is the data-engineering foundation for cloud unit economics and customer profitability analysis.

How much does a data pipeline cost?

The honest answer is not a universal monthly range. It depends on what the vendor meters. The same pipeline can look inexpensive under one pricing model and become the largest line item in your data stack under another.

A tool may charge for distinct rows that changed, every event loaded, gigabytes moved, reserved capacity, or the compute time required to finish the work. Before comparing prices, you have to translate each quote into the same workload.

Here is one real example. A Supaflow workspace moved 26.3 million rows across 453 jobs using 26.98 credits. At the current Professional list price of $3 per credit, that was $80.95. Fivetran's 2026 Pricing Estimator returned $1,908.86 per month when we entered the same row count as Monthly Active Rows (MAR).

The usage screen rounds the credit total and cost independently. It displays 26.98 credits to two decimal places, while the $80.95 estimate is calculated from the underlying unrounded daily credit values. Multiplying only the displayed credit total would produce $80.94 because that calculation starts from an already rounded number.

That does not mean every 26-million-row pipeline will have the same result. It shows why the billing unit matters more than the headline price.

Oracle OTM analytics should answer four questions quickly: What are we spending? Are shipments on time? Are we using capacity well? Where is performance getting worse?

The difficult part is rarely drawing the dashboard. It is agreeing on the calculation behind each number and mapping that definition to the right Oracle Transportation Management data.

This guide defines 12 practical OTM KPIs, the formulas behind them, and the shipment, cost, stop, and location data needed to calculate them in a warehouse or BI tool. To move that source data into your analytics platform, start with the Supaflow Oracle Transportation Management connector.

Salesforce Marketing Cloud Engagement stores useful analytics data across Data Extensions, subscribers, sends, journeys, and system Data Views such as _Sent, _Open, and _Click. Moving that data into Snowflake gives marketing, revenue, and data teams one place to analyze engagement alongside CRM, product, and transaction data.

The timing matters. Salesforce keeps only the most recent 180 days in Automation Studio Data Views. If you need a durable history, start exporting before older engagement records age out.

This guide shows how to export Salesforce Marketing Cloud data with Supaflow's SFMC-to-Snowflake connector, including the Installed Package permissions, the connector settings visible in the app, the objects to select, and the checks to run after the first load.

You want to try Supaflow against a SQL Server that runs on your own machine -- a developer install on your laptop or a server on your office network. There is no public IP, no port forwarding, and no VPN between that database and the cloud. A Supaflow-hosted Agent needs to reach the database over the network, so localhost in the datasource form will not work for this test.

A TCP tunnel is the fastest way to prove connectivity during a proof of concept (POC). This guide shows two temporary options: ngrok, the popular managed tunneling service, and bore, a minimal open-source alternative that needs no account. Both give you a public host and port that forward straight to your local SQL Server, and both plug into the Supaflow datasource form the same way.

For production pipelines, deploy a self-hosted Docker Agent on a stable host inside the same private network as SQL Server. The agent connects to SQL Server over the local network and polls Supaflow over outbound HTTPS, so the database port stays private. This removes the tunnel relay and changing public endpoint from the data path and gives long-running pipelines a predictable network path.

For a while, we used a simple line: why pay 5x more for Fivetran?

It was a good line. Easy to understand. Easy to remember.

Then we ran the numbers on a real high-volume Supaflow workspace and realized we were underselling it.

The difference was not 5x. It was more than 20x.

In one real Supaflow workspace, over a seven-day usage window from June 13 to June 19, 2026, we ran 453 jobs and moved 26,297,690 rows across 11,102 objects (individual tables and streams) and a broad source and destination test matrix. Supaflow used 26.98 credits to do it.

This was not a neat one-connector benchmark. The workspace had 30 source connections and 9 destination connections, including HubSpot, Salesforce, Oracle Transportation Management, PostgreSQL, SQL Server, Salesforce Marketing Cloud, SAP SuccessFactors, Google Analytics 4, Google Ads, Shopify, Stripe, SFTP file feeds, and Airtable. Those jobs loaded into Snowflake, S3 Data Lake, PostgreSQL, and SQL Server, and even pushed data back out through reverse ETL into Salesforce and Salesforce Marketing Cloud.

We also did not give the system ideal conditions. We ran the matrix concurrently to put real pressure on it: source APIs, destination writes, object-level orchestration, schema work, resets, full resyncs, and many jobs competing for runtime at once.

That is why I trust the result more. It is closer to a busy customer account than a polished demo where one fast source writes to one fast destination in isolation.

At the current Professional list price of $3 per credit, that workload is $80.95 in Supaflow usage.

Then we entered the same row count, 26,297,690, into Fivetran's 2026 Pricing Estimator as a Salesforce connection on the Standard plan for a 1-200 person company.

The estimate came back at $1,908.86 per month.

That is not 5x. It is more than 20x lower.

Oracle Transportation Management integration is one of the more deceptive data engineering problems in the logistics stack. OTM exposes a well-documented REST API and sync looks straightforward on paper -- until you run it against real data and discover that the metadata catalog returns 400 on half the tables you need, "empty" timestamps arrive as literal 0, and sync-mode responses silently truncate at 1 MB.

This guide walks through how OTM data integration actually works in production: the objects that matter, the five quirks that break naive pipelines, the right way to handle incremental sync with OTM's server-side clock, and how to move OTM data into Snowflake or any cloud warehouse reliably.