I am struggling with some limitations of native Salesforce reporting and wondering if it's time to move to PowerBi or Tableau. We are a nonprofit working to reduce poverty in our community. One of the primary challenges is that we have a "lifetime" model, which means that people can engage in our services, disengage and then re-engage at a later date, as long as they are still in poverty (mix of federal guidelines and our own cost of living data). Each time a person engages with us, we create a new Intake and that Intake is then connected to other objects like trainings, employments, service plans, etc. So in effect each Intake (we call it Program Engagement) is like a chapter of a person's journey with us. This allows us to do some time based reporting as well as holistic outcomes. The challenge is that not everything is connected to a program engagement, as some things are more "evergreen" and not just tied to a specific point in time. For example we track referrals, and since people can come and go, the place they were referred by "today" may not be the place they get referred by 2 years from now. We can get a LOT of reporting via native reports, using report types, lookups, etc however, there are just times when the lifetime model creates some data/outcome "noise". So I am wondering if moving to PowerBi or Tableau would be the best long term solution, however, those solutions do come with a new learning curve, costs, etc. As we want to keep people in Salesforce as much as possible and not have some Dashboards in SF and then other dashboards in PowerBi, etc. So what are the pros/cons? Price is one, visibility is another, as not everyone needs to create Dashboards/reports but still need to view them. So....?
#Reports & Dashboards #Nonprofit #Systems Administrator
Khyati Mehta (InfinySkills) 
Forum Ambassador
Hello Heath,
Honestly, what you’re describing is exactly the kind of scenario where Salesforce native reporting starts to feel stretched. It works great for structured, object-based reporting, but once you get into a lifetime journey model with re-engagements, mixed time contexts, and loosely connected data, it creates noise that’s hard to cleanly model in standard reports. That’s usually the signal to at least consider something like Tableau or Power BI — not because Salesforce is failing, but because your data storytelling has become more complex than what report types and joins can comfortably handle.
That said, I wouldn’t jump tools immediately. External BI tools shine when you need cross-object, time-series, historical layering, and flexible data modeling — basically building a cleaner “analytics layer” on top of Salesforce. They’ll let you reshape your data and remove that noise.
A lot of orgs in your situation land on a hybrid approach — keep operational dashboards in Salesforce, and use Power BI/Tableau for impact reporting, leadership insights, and longitudinal analysis where your lifetime model really matters. So yes, it’s less about when to move completely and more about when to extend, and from what you described, you’re pretty close to that point. Hope this helps!
