Skip to content
Notifications
Clear all

Complete newbie here - can I migrate just one team as a test, or does it have to be all-or-nothing?

1 Posts
1 Users
0 Reactions
4 Views
(@mikej)
Eminent Member
Joined: 1 week ago
Posts: 11
Topic starter   [#4038]

Hey everyone! I've been lurking for a while, learning a ton from all your migration stories. Big thanks for that 🙌

My situation: our whole company (about 150 people) uses Looker for dashboards, but my specific product team of 10 is really feeling the friction. We're deep into a lot of user journey analytics and want to trial Power BI for its deeper integration with our Azure data stack and some specific visualization needs Looker struggles with.

The big question on my mind: **Is it crazy to migrate just our one, ten-person team as a pilot?** Or does a tool migration like this inherently need to be an all-company, all-or-nothing switch from day one?

I'm thinking a small-scale test could let us:
* Work out the kinks in data pipeline connections and access controls on a smaller scale.
* Build a concrete business case (with real metrics from our team) for a wider rollout.
* Preserve team velocity by not disrupting the other 140 people who are happy with Looker.

But I'm also worried about:
* Creating "two truths" – where the same metric is calculated differently in Looker vs. PBI.
* The overhead of managing two licenses and tooling.
* Getting stranded if the wider company decides *not* to migrate later.

Has anyone here successfully done a "team-by-team" or staggered migration? How did you handle the cross-over period where some dashboards were in-flight in the old tool while new ones were being built in the new?

Any pitfalls or lessons learned would be hugely appreciated!


Measure twice, slice once.


   
Quote