Welcome to BIChart
Learn more about how BIChart works here.
BIChart is an AI-powered migration tool for moving dashboards and reports off of Tableau onto Microsoft Fabric. Built with a familiar UI to those who work in analytics, BIChart will have you completing BI migrations in minutes, not months.
What BIChart Does — and Does Not Do
This page provides a high-level overview of what BIChart delivers and what is outside the scope of BIChart, to ensure clear expectations for your migration projects.
What BIChart Does
- Visual Migrations
BIChart automatically converts your Tableau visualizations into Power BI equivalents, preserving charts, dashboards, and layouts wherever possible.
- Workbook and Report Connection Details
BIChart extracts and transfers connection metadata — such as server names, database names, and table references — into the Fabric environment to help reestablish connectivity frameworks.
- Metadata Extraction and Transformation
BIChart reads and maps your Tableau workbook metadata (fields, measures, calculated fields, relationships) into corresponding Power BI structures, helping speed up reconfiguration. BIChart translates Tableau calculations into Power BI DAX formulas where feasible.
- Support for Tableau to Power BI Migration
BIChart currently supports one-way migration from Tableau to Power BI. Migration from Power BI back to Tableau is not available.
- Optimized for Microsoft Fabric
BIChart's migration outputs are aligned specifically with Microsoft Fabric environments to ensure compatibility with the latest Power BI capabilities.
What BIChart Does Not Do
- Data Migration
BIChart does not move your underlying data sources (rows of data) from source systems. It focuses solely on migrating your workbook structures and visual models.
- Credential or Password Management
BIChart does not retrieve or store your database usernames, passwords, OAuth tokens, or other authentication secrets.
You will need to manually reauthenticate your data sources after migration.
- Validation of Migrated Content
BIChart does not perform automated testing, reconciliation, or quality assurance of the migrated dashboards or visual outputs.
Enterprises are responsible for validating the accuracy and completeness of the migrated reports.
- Cross Platform Migrations Beyond Tableau and Power BI
BIChart only supports migrations from Tableau to Power BI. It does not support migrations involving other BI tools (e.g., Looker, Qlik, or Domo), nor does it currently support Power BI-to-Tableau migrations.
Supported Tableau Versions
BIChart supports Tableau workbook (.twb) files based on the structure used by supported Tableau Server versions.
How Tableau Version Compatibility Works
Tableau Desktop can only publish workbooks to Tableau Server if the Server version is the same as or newer than the Desktop version. This means organizations typically standardize on a Tableau Server version and ensure Desktop installations do not exceed it.
To maintain compatibility with enterprise environments, BIChart models its workbook parsing after the most recent maintenance release of each supported Tableau Server version.
For example:
- If Tableau Server 2024.2 is supported, and the latest patch version is 2024.2.10, then BIChart models the workbook schema and behavior on 2024.2.10.
BIChart Version Support Policy
- BIChart only supports Tableau Server versions with active maintenance and technical support.
- Older workbook versions should be opened and saved in a newer version of Tableau Desktop that matches a supported Tableau Server version.
Please refer to Tableau's Release and Support Page for the latest support timelines.
Power BI Version Policy
BIChart generates reports using the latest General Availability, found here, version of Power BI Desktop and outputs them in .PBIP format. This ensures compatibility with the Power BI Service (Microsoft Fabric).
Compatibility Notes
- BIChart always compiles
.PBIPprojects using the latest GA version of Power BI Desktop. - Preview versions are not supported.
- Customers are not required to install Power BI Desktop but may do so to inspect or edit downloaded files.
- Opening
.PBIPfiles in an older version of Power BI Desktop may result in compatibility errors. - Users who download
.PBIPfiles should ensure they are using the latest GA version of Power BI Desktop. - BIChart does not guarantee compatibility with older versions of Power BI Desktop.
- All files are structured for direct deployment to Fabric or local review using an up-to-date Power BI Desktop.
How BIChart Connects to Tableau and Power BI
BIChart uses secure, industry-standard methods to connect to your Tableau Cloud and Microsoft Fabric environments during migration.
This ensures a controlled, authenticated, and compliant integration experience without the need for sensitive user passwords or direct database access.
Below is a high-level overview of how BIChart establishes connections:
Connecting to Tableau Cloud
BIChart connects to Tableau Cloud using Personal Access Tokens (PATs).
A PAT allows BIChart to authenticate securely to your Tableau Cloud environment without requiring user passwords.
The token is created by you and scoped to your Tableau site and user role.
- Personal Access Token Name
- Personal Access Token Secret
- Tableau Cloud Site ID
BIChart requires access to read workbook metadata, connection information, and visualization definitions.
Your Tableau user must have appropriate permissions (typically Creator or Site Administrator roles).
BIChart does not retrieve, move, or store your underlying datasets — only metadata needed for migration.
Connecting to Microsoft Power BI (Fabric)
BIChart connects to Power BI using a Service Principal authenticated through Azure Active Directory.
A Service Principal is a secure application identity in Azure that allows BIChart to programmatically access Power BI without requiring user credentials.
- Azure Active Directory Application (Client ID)
- Directory (Tenant ID)
- Client Secret
The Service Principal must be granted Power BI API permissions, and must have access to the target workspaces where the migrated reports will be published.
(Typically requires Contributor or Admin rights on the destination workspace.)
The Power BI tenant must have Service Principal access enabled via Admin Portal settings.
Access can be scoped to specific security groups for additional control.
Security and Compliance Commitments
BIChart never requests, stores, or transmits user passwords.
Connections are scoped to only the access necessary to extract workbook/report metadata.
Tokens and secrets are managed by your organization and can be revoked at any time.
Why BIChart is Considered an AI Company
At its core, BIChart uses artificial intelligence (AI) to streamline and automate complex migration workflows that would otherwise require extensive manual effort.
While BIChart leverages OpenAI's capabilities, we never share descriptive customer data with third parties. Our platform continually improves its internal libraries and algorithms based on industry patterns and validated improvements, enhancing accuracy over time.
Privacy & Security
At BIChart, we are committed to protecting customer information and maintaining strong security practices.
This section outlines how we safeguard privacy and secure your data during migration activities.
Privacy
Your privacy is important to us.
To learn more about how we collect, use, and protect your information, please review our Privacy Policy.
BIChart does not use customer data, metadata, or migrated content to train, fine-tune, or improve any AI, whether internally or through third-party providers.
Customer information is never used for model training, or dataset enrichment
Security
We implement industry-standard security controls to protect customer data and maintain trust throughout the migration process.
Our security practices include:
BIChart connects to Tableau Cloud and Power BI using secure, token-based authentication (Personal Access Tokens and Service Principals). User credentials and passwords are never collected or stored.
BIChart operates exclusively on metadata (visualizations, workbook structures, and connection details).
Underlying data — including tables, records, and sensitive content — is never accessed, moved, or stored.
All authentication credentials (tokens, client secrets) are managed by the customer, with the ability to revoke access at any time through Tableau or Azure settings.
All communications are encrypted in transit using TLS 1.2 or higher. Our infrastructure follows cloud security best practices, including role-based access controls, environment isolation, and monitoring. Currently, BIChart is in the process of obtaining SOC 2 Type 1 and 2 compliance.
How to Get Started
Getting started with BIChart is simple.
You can either:
- Email Us
Reach out to our team directly at hello@bichart.ai to begin your migration project or request more information.
- Request Access
Click the Request Access button on our home page to submit your information, and a member of our team will follow up with the next steps.
FAQ
How is pricing determined?
Our pricing is based on an assessment of your existing environment. We work with you to determine what dashboards and reports need to be migrated, then recommend the right plan for your specific needs.
What if I have specific security requirements or need custom contracts?
For advanced security needs (e.g., SSO, enterprise governance, single tenancy) or special contract terms, please contact sales. We're happy to discuss custom solutions that fit your organization's policies.
Why use a migration tool if analysts need to learn Power BI anyway?
While learning Power BI is valuable, manual migrations are time-consuming and prone to errors. BIChart accelerates your transition timeline from months to weeks, reducing human error and inconsistencies and giving you more time to focus on what matters, mastering Power BI.
How are Tableau elements mapped to Power BI?
BIChart maintains a comprehensive library of mappings that pairs each Tableau element with its closest Power BI equivalent. This includes filters, parameters, visuals, and DAX calculations, ensuring the most appropriate conversion for each component.
How do I import content from Tableau?
Log into the source tool (e.g., Tableau) via a personal access token, pick which workbooks/datasources to import, and BIChart will place them in your chosen project.
Do I have to connect to Tableau and Fabric?
Nope! You are allowed to upload and download content from your local machine.