Said It Here

How to track historical data in CRM without a data warehouse

Native CRM sync tools often fail to support historical data objects like seasonal inventory trends or past metrics, forcing businesses to choose between external data warehouses or losing insights for platforms like Tableau Next. Without a way to capture metrics from day one—such as dead stock per season rather than just total sales—owners cannot recover past data for future decision-making.

Overview
People affected2 accounts across 2 forums
Workarounds found3 items attempted
Community agreement1 total upvotes

What people tried

Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.

Found another way around this?

Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.

  1. 1
    Reviewing what was left over from previous periods before restocking rather than just looking at past sales totals.
    Did this help you?
  2. 2
    standing up a separate data warehouse
    Did this help you?
  3. 3
    putting files on S3 and then reading them from there
    Did this help you?

In their words

Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.

r/smallbusiness1 person · September 2026

“lo que más me hubiera servido llevar desde el principio es cuánto se me quedaba en tallas muertas por temporada, nomás llevaba el total vendido y ya.”source ↗

MotherFeeling7013 · r/smallbusiness · 1 upvotes
r/salesforce1 person · September 2026

“I'm just learning that most History objects are not supported by the native CRM sync. What are people doing instead? (Besides throwing Data 360 in the trash)”source ↗

“I'd prefer to stay on-platform, as in not stand up a separate data warehouse or put files on S3 and then read them from there etc.”source ↗

“The ultimate goal is to use the data in Tableau Next.”source ↗

Material-Draw4587 · r/salesforce

Where this came up

People with this problem also raised