How to Migrate from OBIEE to Tableau: Step-by-Step Guide

Why Move from OBIEE to Tableau?

Moving from Oracle Business Intelligence Edition (OBIEE) to Tableau is a shift towards standardized reporting to self-service analytics. The primary reasons why organizations make the move are 

• Advanced visualization: Tableau provides a vast library of interactive charts, maps, and animations. Its intuitive, interactive design makes data insights more accessible.
• Improved user experience: Tableau’s interactive and visual interface provides a dynamic user experience. Compared to OBIEE’s traditional reporting approach, Tableau enables quicker dashboard creation and easier data discovery.
• Enhanced self-service: Tableau reduces IT bottlenecks common in OBIEE’s rigid structure. They provide business users with a reduction in development backlogs and faster decision-making.
• Cost and Time Efficiency: Tableau poses deeper integrations with modern cloud stacks and AI tools. It yields long-term ROI through faster decisions. 
• Performance and Scalability: With optimized query execution and efficient caching, Tableau delivers faster performance for large datasets. It also scales well across cloud and hybrid environments.

✕

Book a Free Consultation

Share your details and our experts will reach out to discuss your goals.

Challenges faced during the OBIEE to Tableau Migration and ways to overcome

Migrating from OBIEE to Tableau is often met with unexpected technical roadblocks. Understanding these challenges will make the migration smoother and more successful.

• Data model recreation: OBIEE’s data modelling is built around a unique repository (RPD) semantic layer that handles data federation, calculations, and security, whereas Tableau uses simpler data extracts. To overcome this, use a phase approach to build Tableau Published Data Sources.  Extract metadata via BI connector to reuse OBIEE logic natively in Tableau. 
• Report and Dashboard conversion: OBIEE is a highly structured, pixel-perfect enterprise report meant for standard operational reporting. Tableau is not meant for pixel-perfect reports, which are more prevalent in OBIEE. To overcome this, redesign reports for interactivity or integrate Tableau with complementary reporting tools.
• Performance tuning: Tableau-OBIEE connectors must handle live/extract modes and version compatibility. They might show a decrease in performance if replicated directly in Tableau. To mitigate this, redesign dashboards using Tableau best practices, optimize data models, and use extracts where appropriate.
• Security and Access controls: Replicating OBIEE’s role-based and row-level security in Tableau can be complex. To overcome this, implement Tableau user filters, groups, and row-level security. Do a UAT to ensure compliance.
• User Adoption: End users might not adopt Tableau’s self-service analytics; they might stick with OBIEE’s predefined reports. To overcome this, provide targeted training sessions for different user groups.

Best Practices for an OBIEE to Tableau Migration

1. Start by creating a roadmap with milestones, resource assignments, and a change management communication plan.
2. Start with pilot projects to demonstrate value and gradually transition to full implementation.
3. Document reports, dashboards, RPD objects, and usage statistics to define migration scope and priorities.
4. Capture joins, calculations, hierarchies, and KPIs to ensure accurate replication in Tableau.
5. Rebuild dashboards again in Tableau by avoiding lift and shift. It will enhance visualization and logic.
6. Implement security and governance controls using Tableau user groups, row-level security, and project-based permissions.
7. Replicate security Tableau row-level security and groups, testing mappings rigorously to match OBIEE roles.
8. Validate the data by running both MicroStrategy and Tableau in parallel.
9. Plan for phased decommissioning of OBIEE. 

6 Step OBIEE to Tableau  Migration  Process

Migrating from OBIEE to Tableau is a shift from top-down reporting to modern self-service analytics. A structured phase-based approach is critical for success.

1. Assessing OBIEE environment:

Start by analyzing the OBIEE environment, including dashboards, reports, and KPIs, and security models. Track OBIEE usage logs to identify which reports are actually being used. Categorize reports into simple, medium, and complex based on their logic and number of joins. Select a phased migration or a parallel-run strategy to deliver value early and reduce risk.

2. Configure Tableau environment:

Set up your Tableau Server/Cloud site, including users, permissions, and content structure. Extract metadata from OBIEE RPD using tools like BI Connector for direct Tableau access. 

3. Data Source mapping and Validation:

Map OBIEE data sources to Tableau-supported connectors. Validate data availability, refresh frequency, and performance to ensure consistency between source systems and Tableau. Reconnect Tableau to the underlying data sources, ensuring proper configurations.

4. Migration and Report recreation:

Design Tableau data sources by implementing joins, relationships, and calculated fields that reflect OBIEE business logic. Manually recreate OBIEE Analyses and Dashboards utilizing drag and drop for visualization. Recreate prompts, variables, and agents using Tableau parameters and actions. Follow best practices for layout, filters, parameters, and user experience.

5. Security and Governance:

Map OBIEE roles to Tableau row-level security and user filters. Implement security at the data source level using User Filters so that only authorized users are able to access. Mention the governance policies that specify who can publish data and who can only view.

6. Validation and Testing:

Perform data reconciliation between OBIEE and Tableau reports. Validate the metrics, calculations, and filters to ensure accuracy and stakeholder confidence. Do a user acceptance testing (UAT) to test the interactivity and accuracy of the new dashboards. Deploy the migration in phases, monitoring with Tableau Server/cloud.

What to Do After You Migrate from OBIEE to Tableau

A successful OBIEE to Tableau migration is not about how many workbooks were created; it is measured by how many people actually use them.

• Validate functionality: Do a parallel run and compare the reports of both OBIEE and Tableau. Confirm their accuracy in calculations, filters, prompts, and aggregations. Do User Acceptance Testing (UAT) focusing on high-traffic subject areas, validating security mappings, and performance under load.
• User training: Provide hands-on training on helping users navigate Tableau, create dashboards, and use self-service analytics features effectively.
• Monitor and Optimize: Review the performance bottlenecks and optimize data sources, extracts, and filters. Follow Tableau best practices to ensure fast load times and smooth user interactions.
• Decommissioning OBIEE: Decommission OBIEE only after Tableau stability, user sign-off, and ensure it does not disrupt business operations.

Why Choose Entrans for Your OBIEE to Tableau Migration?

Migrating from OBIEE to Tableau is a strategic shift towards a futuristic analytics platform. Choosing a migration partner like Entrans brings in a deep expertise in OBIEE RPD analysis, Tableau data modeling, performance optimization, and governance. 

We take care of the risks associated with migration through our proven frameworks, through validation and best practices. Our expert guidance ensures data accuracy, smooth transition, and faster return on investment.

Learn about how we make the technology change into a long-term analytic advantage. Book a consultation with us.