Migrating from a legacy reporting system to Looker has numerous advantages, with moving to the cloud, empowering your users with more agile access to their data, as well as granting a greater flexibility in how you deliver insights to your team. Looker is a true data platform, you can also use it to put the data where your users need it. Whether it is extending the platform with web actions, embedding visualizations in other tools, or providing a rich jumping off place for your users, Looker can turn your analysis into meaningful actions to enhance your business. Staying on your current system can reduce your team’s speed to insight, their time lost of switching between systems, and the friction of moving data between systems.
Analyzing your current system and your future needs is critical before starting the migration. Some factors to consider are:
Your Current Reporting Landscape - How much is being utilized? Do we need to migrate everything?
The Semantic Layer - Is your semantic layer answering all of your users’ questions? How can we add value - by adding data or broadening access?
User Workflows - How are your users using your system? Are they exporting to Excel to do their own analysis or are they using other tools in their workflow?
Now that we have determined the scope, the use cases, and the new capabilities in Looker we want to exploit, we need to start the actual migration.
Code Migration - We offer a Legacy to Looker Migration Service that accelerates the migration by programmatically converting your Legacy Semantic Layers to LookML. This conversion includes retaining formatting, data types, SQL definitions, and your custom views. By extracting the semantic layer programmatically, you can focus on meeting your user needs and not re-typing code.
Semantic Layer vs Explores - Traditionally, Legacy Semantic Layers are monolithic in nature. With Looker, the larger an explore, the harder it is for an analyst to find the fields that they need. After identifying your users’ needs, you need to break your semantic layers into digestible models and explores for each of your user groups. A measured approach to this migration can truly enhance your users’ experience, by speeding up the process of accessing their insights.
Report Migrations – Legacy systems often have a different report for every question, even if it’s just a top line answer. With Looker, you can build your semantic layer and analytics, so your users can answer questions quickly and don’t have to look over a wide table to find the answers. Here is where our analysis comes into play. By understanding what your users are asking, you don’t have to migrate every report, thus reducing costs and maintenance.
Reduce Technical Debt- When migrating your underlying semantic layer to LookML, it also make sense to reduce your technical debt by simplifying the code when possible using extends in the explores. This is to ensure that you are not repeating code and migrating any reports that are superfluous or haven't been used. Use this opportunity to ensure that your Looker deployment is lean and mean.
If part of your transformation also includes switching databases, we can help you convert that code to your new database with our Evove offering. Find out more here .
Workflow Enhancements - While you are making a shift in solutioning, it makes sense to examine your workflows as well. Looker's capabilities allow you to integrate embedded analytics in other tools, use web actions to start a new workflow from your insights, or even create alerts when something needs attention. This simplification turns your reporting into action-inducing analysis, increasing your users’ effectiveness.
Extends, Derived Tables, and Performance Tuning - You also want to make sure that your system hums when you roll it out to your users. Maximize your Looker deployment by using persisting derived tables (PDTs), extends in explores, and caching often used data to ensure that your users can make their insights fast and hassle-free.
The cost of migrating from one system to another has often been a reason to maintain the status quo. At Trianz, we help you reduce that cost by shortening your time to production with our Legacy to Looker Migration service, reduce your technical debt, and maximize the capabilities of your Looker Instance.
Ready to start your migration? Reach out to us at email@example.com
Director of Analytics Solutioning at Trianz
With over a decade of experience in the analytics space, Andrew has had great success helping clients migrate to the newest technologies and making the best of them.
Contact Us Today
Data warehouses and data lakes both store massive amounts of data. However, there are several key differences. Understanding what they are, as well as the pros and cons of each, will help you make the right decision for your business.Explore
A voracious appetite for data is quickly becoming one of the defining traits of modern corporations. Companies of all sizes are racing to find ways to harvest relevant data, hire data scientists and implement business intelligence tools that will help them understand their clients and markets.Explore
In Part I, we examined the on-premise and cloud upgrade options available for SQL Server 2008 as it reaches EOL. For scenarios where memory management challenges or database operations have proved difficult, Snowflake is also a strong option, which is increasingly the default choice for many data warehouse and data lake offerings.Explore
Connect with usx