Welcome to BIChart

Business Model Transparency and Trust

BIChart is an enterprise software-as-a-service platform designed to help organizations migrate analytics content from Tableau to Microsoft Fabric efficiently and securely. BIChart operates exclusively on customer-authorized metadata to translate dashboards, reports, and semantic structures into Power BI–compatible outputs.

BIChart does not co-mingle, distribute, resell, or reuse customer data or metadata, and it does not access or move underlying record-level data. All access to source environments is explicitly granted and fully controlled by the customer. BIChart’s platform is built to reduce migration friction, accelerate modernization timelines, and maintain enterprise-grade security throughout the process.

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

Currently, BIChart supports Tableau 2023 and greater.

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 .PBIP projects using the latest GA version of Power BI Desktop.
• Preview versions are not supported.
• Opening .PBIP files in an older version of Power BI Desktop may result in compatibility errors.
• Users who download .PBIP files 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.

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

Authentication Method

BIChart connects to Tableau Cloud using Personal Access Tokens (PATs).

Purpose of 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.

Required Information

• Personal Access Token Name
• Personal Access Token Secret
• Tableau Cloud Site ID

Permissions Needed

BIChart requires access to read workbook details.

Your Tableau user must have appropriate permissions (typically Creator or Site Administrator roles).

Data Security

BIChart does not retrieve, move, or store your underlying datasets — only metadata needed for migration.

Connecting to Microsoft Power BI (Fabric)

Authentication Method

BIChart connects to Power BI using a Service Principal authenticated through Azure Active Directory.

Purpose of Service Principals

A Service Principal is a secure application identity in Azure that allows BIChart to programmatically access Power BI without requiring user credentials.

Required Information

• Azure Active Directory Application (Client ID)
• Directory (Tenant ID)
• Client Secret

Permissions Needed

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.)

Tenant Settings

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

No Password Storage

BIChart never requests, stores, or transmits user passwords.

Minimal Scope Principle

Connections are scoped to only the access necessary to extract workbook/report metadata.

User-Controlled Credentials

Tokens and secrets are managed by your organization and can be revoked at any time.

Use of Artificial Intelligence

BIChart may use artificial intelligence (AI) in its internal development, operational workflows, and product research to support efficiency, quality, and continuous improvement. AI capabilities may be introduced, expanded, or modified within the BIChart platform over time as the product evolves.

AI Feature Control

We recognize that some organizations prefer not to enable AI-assisted functionality.

If your organization does not wish to use AI-enabled features within BIChart, you may opt out by contacting support@bichart.ai. Upon request, AI-assisted features will be disabled for your account, and BIChart will operate using deterministic, non-AI logic only.

Data Protection Commitment

While BIChart may leverage third-party AI capabilities, we do not use customer data, metadata, or migrated content to train or fine-tune any AI models, and we do not share descriptive customer information for model improvement or external use.

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**.

Use of Customer Data with AI/LLM Systems:

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:

Microsoft Single Sign-On (SSO)

BIChart authenticates users using Microsoft Single Sign-On (SSO). User access is managed through the customer’s Microsoft identity provider, enabling centralized identity management, access control, and alignment with existing corporate security policies.

Token-Based Authentication

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.

No Dataset Access or Storage

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.

Customer-Controlled Access

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.

Secure Infrastructure

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.

Security Certifications & Compliance

What Security Certifications and Compliance Does BIChart Have?

BIChart has achieved:

• SOC 2 Type I
• SOC 2 Type II

These certifications validate that BIChart maintains effective controls across security, availability, confidentiality, and processing integrity, and that those controls operate effectively over time.

User Usage & Behavior Tracking

BIChart uses PostHog for product analytics and usage monitoring.

What We Track

PostHog is used to understand how users interact with the BIChart application so we can improve usability, reliability, and performance. Tracked data may include:

• Feature usage events (e.g., import actions, migration steps)
• Navigation patterns within the application
• Error events and system performance signals
• Session metadata (e.g., timestamps, anonymized identifiers)

What We Do Not Track

• We do not capture underlying business data, datasets, or records
• We do not record database credentials, tokens, secrets, or passwords
• We do not inspect or analyze customer report contents or visual values
• We do not use usage data for advertising or resale

All analytics data is limited to application-level behavior and is used solely to operate and improve BIChart.

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 pair 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 convert them to .PBIP and or publish them to Fabric.

Do I have to connect to Tableau and Fabric?

No, you are allowed to upload and download content from your local machine.

Is My Tableau or Power BI Metadata Shared with Third Parties?

No.

BIChart does not disclose, sell, share, or reuse any customer metadata retrieved from Tableau or Microsoft Fabric.

Metadata is used solely to perform the requested migration tasks within the BIChart platform.

Does BIChart Access My Metadata When I’m Not Using the App?

No.

BIChart only accesses metadata during active, user-initiated actions (such as imports, migrations, or exports). There is no background polling or continuous access.

How Can I Close My BIChart Account and Delete All Metadata?

To close your BIChart account and request deletion of all associated metadata:

• Email support@bichart.ai from the same email address used to register for BIChart

Our support team will validate the request and confirm deletion through our customer support and compliance process.

When Access Is Revoked, Does BIChart Auto-Purge My Data?

Yes. When access to a connected system (e.g., Tableau Cloud or Microsoft Fabric) is revoked, BIChart no longer has the ability to access that environment.

Any retained metadata is handled in accordance with BIChart’s SOC 2–aligned data retention and deletion policies and is not refreshed or accessed after revocation.

How Long Does BIChart Keep My Data?

BIChart retains customer metadata only for as long as necessary to provide the service or meet contractual and compliance obligations.

Retention periods follow SOC 2 best practices and are governed by:

• Active customer status
• Contractual requirements
• Customer-initiated deletion requests

No customer data is retained indefinitely.

Does BIChart Save or Push Data Back to Tableau or Fabric?

BIChart does not write back to Tableau.

For Microsoft Fabric / Power BI:

• BIChart can generate Power BI artifacts (.PBIP)
• You may optionally publish semantic models or reports to your Fabric environment
• Alternatively, publishing can also be done directly by the user through Power BI Desktop

BIChart does not automatically push content into customer environments without explicit user action.