To change dataviz tool, 4 options : from “ As Is” to “ Self BI”

To switch data visualization tools, 4 options  : From  " As Is"  to  " Self BI"

Migrating from one data visualization solution to another is an ambitious challenge for a company. But how can this be achieved successfully when the source platform has a considerable history, with all the inherent complexity that entails?   We have identified four main approaches, each with its advantages and limitations, depending on business needs, technical constraints and the long-term vision of the company concerned. (We made a parallel that seems relevant to us, with the challenges of a "real" move in "real life"  😊 ).

Option #1: The  " Big Bang" , the radical transformation driven by the entire team.

A "Big Bang" migration is like moving into a completely redesigned, ultra-modern house. Keeping Grandma's old furniture or outdated decor is out of the question: everything is rethought, from the furniture to the living spaces. The key players  are the residents  who define their needs in the new home: "We want a bright space, a certain number of rooms, etc."  Data analysts  act as architects  , designing functional (and stylish) spaces.  Data engineers are the electricians or plumbers  who ensure everything (the data flows) works smoothly. Finally, the  business decision-makers  approve or reject the choices.

Advantage :  A complete overhaul to align business needs with modern tools from the outset.  Inconvenience :  The objectives are sometimes contradictory between stakeholders with a significant risk of getting bogged down: many "Big Bang" type migrations fail.

Option #2: An "As Is" migration a copy-paste of the platform into the target

An "As Is" migration is a bit like moving from one house to another without changing a single piece of furniture, painting, or curtain. You take everything with you: your sofa and its cushions, your picture frames, and even that stack of magazines on the coffee table 😊. In your new "home," everything is recreated exactly as it was: no new furniture, no fresh paint, no changes to the layout. However, the underlying technical infrastructure (roof, plumbing, electricity, etc.) is no longer the same. From a data visualization perspective, this means that all reports are migrated as is, without redesign or optimization. The data remains unchanged, and the semantic layer is adapted to the target technology. The design and structure of the dashboards are faithfully reproduced, "As Is."

Advantage :  Rapid and painless migration for businesses, with a high level of adoption of the target solution. Inconvenience :  We keep everything, even the duplicates or useless dashboards, we also keep the same "pathologies": slowness, errors... It's a "half" modernization.

See also:

Migrate from SAP BO to Power BI, automatically, for a fixed price  !

Option #3: An "As Is" Migration & a Transformation at the end, to reach the optimum over time.

Here, we move quickly in "As Is" mode so as not to disturb the inhabitants (the trades), but once settled in, we reorganize, we improve: "What if we transformed this room into an open space? What if we replaced the old furniture or added storage?". This approach allows for the streamlining and optimization of the target platform progressively: removing duplicates, merging similar dashboards and simplifying the system.

Advantage :  The profession is reflected in the target technology and can participate over time in the rationalization of the target platform. Inconvenience :  The actual transformation of the target platform, if it is to take place, will be gradual.

Option #4:  An "As Is" Migration  & "Self BI", For true modernization!

To continue with the metaphor, "self BI" would be like moving house, keeping only the essential furniture (strategic reports) and letting the residents (the business) take care of the rest themselves. To achieve this, we will implement 3 principles: Migration "As Is" of strategic reports into the target platform,  to constitute a decision-making "framework". Automated migration of the source semantic layer to the target database using star schemas.  Only elements with actual usage will be migrated from the source to the target, resulting in the simplest possible model. Labels and logic from the source will be implemented in the target for a smooth transition.   We will provide the ability to control this new semantic layer,  in order to reach an optimum at high speed.

Advantage :  A fast approach for essential reports, while offering creative freedom to business teams to design the platform of tomorrow from scratch. A thorough modernization.  Inconvenience :  Some answers may be missing initially.

See also:

Migrating SAP BO to Looker with a true semantic layer

CONCLUSION  The choice of a migration approach depends on the company's priorities: speed, radical transformation, or creative freedom, etc. The "As Is" option offers a quick solution and business buy-in, while the "Big Bang" approach involves a complete but risky overhaul. A phased migration with a smooth transformation can be an effective compromise.  Finally, the Self-BI approach offers a more autonomous model. {openAudit}  is a solution offered by Ellipsys that allows "As Is" migrations for certain BI tools, but also "Self BI" migrations. {openAudit}  will also allow you to monitor the platform afterward to ensure it becomes/remains optimal. Choose the migration method that best suits your needs, with {openAudit}  's automation acting as a catalyst!