Looker Migration
Whether you're moving to Looker or off it — we've done it 250+ times.
Migrating BI platforms is complex work. Business logic must be rebuilt, not just moved. We've managed migrations in both directions and know exactly where projects go wrong.
Technology partners
Migrating to Looker
Why Looker migrations require a specialist
LookML is not a lift-and-shift. Calculated fields in Tableau, DAX measures in Power BI, and SQL queries in Metabase don't map cleanly to LookML explores and measures — the underlying logic has to be rethought, not transcribed. Teams that try to migrate without that translation end up with a Looker model that technically functions but stays brittle, hard to maintain, and limited in self-service capability. We've built enough migrations from both directions to know what a well-translated model looks like — and what a poorly executed one costs six months later.
Platforms we migrate from
Tableau
Calculated fields and LOD expressions become LookML measures and dimension groups. Dashboard logic translates into explores with clear join paths. We audit every calculated field before touching the model.
Power BI
DAX measures map to LookML measures, but the relationship model in Power BI works differently from Looker's join/explore structure. We rethink the data model properly rather than forcing a direct translation.
Metabase
Metabase rarely has a documented data model beneath it. We build the LookML architecture from scratch based on your underlying warehouse schema — and most clients end up with better coverage than they had in Metabase.
Looker instance-to-instance
Version upgrades, Looker Original to Looker Core migrations, and instance consolidations. We handle the LookML translation, content migration, and access control reconfiguration.
Custom and legacy BI
Homegrown dashboards, Excel-based reporting, and custom SQL report environments. We start with a data model audit and build Looker on top of what's already working in your warehouse.
Our migration process
- 1
Migration audit
We inventory your existing dashboards, SQL logic, calculated fields, and data models. You get a clear scope: what exists, what's actively used, and what can be retired rather than migrated.
- 2
Architecture mapping
Before writing a line of LookML, we design the full model architecture — which explores to build, how joins should be structured, how your existing logic translates. You review and approve the blueprint first.
- 3
Parallel build
We build the new Looker environment while your existing tool stays live. Your team keeps working uninterrupted. We don't cut anything over until validation is complete.
- 4
Validation and UAT
Side-by-side metric reconciliation — Looker numbers matched against your existing tool before cutover. We surface discrepancies and resolve them before anyone is forced onto a new platform.
- 5
Training and cutover
We train your technical team on the LookML model and run end-user onboarding before the final go-live. Cutover is managed — not a hard switch with no safety net.
How long does a migration take?
Metabase migrations typically complete in 4–6 weeks. Tableau projects with 50+ dashboards run 12–20 weeks. Power BI migrations depend heavily on DAX complexity and model depth. Every engagement is scoped after an initial audit — contact us and we'll give you a realistic timeline based on what you actually have.
“Over the past six months, we have had the pleasure of working with Spencer and the Looker Pros team to migrate our Looker instance. They have been incredibly professional and provided expert guidance throughout the entire process. Their knowledge and support made a complex migration seamless and efficient. We highly recommend them to anyone looking for top-tier Looker expertise.”
Tsering Lama
Senior Manager, Data & Analytics, Cisco
Migrating off Looker
Google's platform restructuring and pricing changes have prompted many companies to re-evaluate whether Looker is the right long-term platform. We'll say clearly what most Looker consultants won't: Looker is the right choice for a specific set of use cases, and the wrong choice for others. We've helped companies exit cleanly when the math stopped making sense. Our goal is always an honest recommendation — not protecting revenue. If you're a good fit for Looker, we'll tell you. If you're not, we'll help you leave well.
When migrating off Looker makes sense
Pricing changed significantly and ROI no longer justifies the platform at your current scale
Your Looker team has shrunk; LookML capacity is gone and a simpler tool is now more appropriate
A platform consolidation — Microsoft stack, AWS, or other — makes a different BI tool a strategic priority
Looker Original → Core migration is too disruptive for the value it delivers at your usage level
Embedded analytics requirements changed; a different tool is now a better technical fit
Platforms we migrate to
Top recommendation
Omni
- Inherits Looker's semantic layer — queries stay governed and centralized
- Substantial LookML logic ports directly — your existing investment isn't thrown away
- Removes LookML development overhead — a better fit for smaller teams
For clients where Omni isn't the right fit, we'll tell you that too.
What a FROM-Looker migration involves
LookML logic must be translated, not exported. Dashboards must be rebuilt in the target tool. Data access controls must be reimplemented from scratch. A poorly managed exit creates technical debt in the new platform just as surely as a bad Looker implementation created it in LookML.
- 1Audit existing LookML and dashboard inventory
- 2Map logic to the target tool's data model
- 3Rebuild in parallel while Looker stays live
- 4Validate metrics side-by-side
- 5Cut over with minimal disruption
Most clients find the migration is the first time anyone has documented how their metrics actually work — that documentation stays with you regardless of which platform you land on.
How we work with you
Migration Audit
We scope your existing dashboards, SQL logic, and data models, then deliver a migration plan with a clear timeline. No commitment required — this is an honest assessment of what a migration actually involves.
Full Migration Management
End-to-end migration ownership from audit through go-live. Your existing tool stays live while we build the new environment in parallel. We don't cut over until metric reconciliation is complete.
Post-Migration Support
After go-live, we provide ongoing LookML support, model optimization, and developer training to ensure your team can own and extend the new environment without dependency on us.
Why work with Looker Pros
250+ implementations
We've managed migrations in both directions more than most firms have done total Looker projects. Pattern recognition from that volume means we see problems before they surface — not after cutover.
Former internal Looker leadership
We've seen how Looker was designed to be used. That perspective makes us unusually effective at translating existing business logic into LookML — or out of it — correctly.
Fortune 500 clients
Cisco, Walmart, HBO Max. Migrations at this scale involve tighter change management, more complex governance requirements, and more stakeholders watching go-live — we've done it repeatedly and know what enterprise migration actually demands.
North American team
No ticketing systems, no offshore relay. You communicate directly with the person doing the work, in your timezone, in Slack or Teams.
Frequently asked questions
- How long does a Looker migration typically take?
- It depends on scope. Metabase migrations with documented data models run 4–6 weeks. Tableau projects with 50+ dashboards typically take 12–20 weeks. Looker instance-to-instance migrations (Original to Core, or instance consolidation) range from 6–12 weeks depending on model complexity. We give you a specific estimate after the migration audit — not a range designed to anchor low.
- Do you migrate existing dashboards or rebuild them?
- Both, depending on the source tool. LookML-based content can often be migrated directly. Dashboards from Tableau, Power BI, or Metabase must be rebuilt in Looker — the underlying data models are different enough that a direct export produces unusable output. We audit all existing content first and tell you what gets migrated versus rebuilt before work starts.
- Can you migrate from Looker to Omni?
- Yes. Omni is the tool we recommend most often for clients moving off Looker. The semantic layer model is similar enough that substantial LookML logic can be ported directly. We handle the translation, dashboard rebuild, and access control reconfiguration.
- What happens to our data during the migration?
- Nothing — your data lives in your warehouse and stays there. BI migrations don't touch the underlying data. We're building a new presentation and semantic layer on top of the same source data your current tool uses. Cutover is a configuration change, not a data movement.
- Should we migrate to Looker Core or off Looker entirely?
- We'll give you an honest answer after understanding your situation. Looker Core is the right path for most existing Looker Original customers who have active LookML investment and a functioning data team. Moving off Looker makes sense in specific scenarios — significant pricing changes, team capacity changes, or a platform consolidation decision made at the organizational level. We don't push either answer; we help you think through the math.
- What does a migration engagement cost?
- Every migration is different — scope, source tool, number of dashboards, and model complexity all affect the price. We don't publish rates because a number without context isn't useful. Contact us for a free migration assessment and we'll give you a real number based on what you actually have.
Get a free migration assessment
Tell us where you are and where you want to go. We'll give you an honest evaluation and a migration roadmap — no commitment required.
Let's talk