CoDash
Start with your platform
Back to your Power BI workflow

BI migration

Salesforce to Power BI migration.

Explore Salesforce to Power BI conversion, with platform-specific inputs and a workspace for reviewing the result.

Supported direction

Your migration scope

Inputs: Salesforce reports, dashboards, objects, and formulas to Power BI

You receive: Power BI model and visual plan in a review workspace

Supported direction. Confirmed in your enterprise agreement. Scope is confirmed per source version and asset type during assessment.

  • sObject, report, dashboard, and formula inventory
  • Formula translation and relationship mapping
  • Power BI model and visual plan
  • Parity validation before release
Choose another migration direction
Start with your platform Explore the workflow
01

Define a migration scope you can defend.

Identify the source platform, target platform, asset types, owners, and reporting deadlines. CoDash’s analysis and rationalization workflows help turn an estate into a selected backlog. Separate required reports from overlapping or obsolete assets, and record the assumptions behind each migration decision.

Reduce scope through rationalization
02

Choose a supported direction.

Migration capability depends on both source and target. Tableau to Power BI produces model and report structures with calculation translation and PBIP/PBIT output. Cognos to Power BI includes report, package, data module, and cube variants. Each direction has its own accepted input variants, target artifact, and entitlement; coverage of a platform does not imply it can convert to every other platform. Scope is confirmed against your source versions and asset types during assessment.

Compare platforms and migration paths
03

Use a representative migration first.

Choose an asset that exercises important calculations, parameters, filters, and data relationships. For Tableau, inspect LOD expressions and table calculations before deciding the target model. For Cognos, review prompts, queries, determinants, and package dependencies. Record conversion gaps and expected manual work before expanding the migration wave.

Read the Tableau to Power BI guide
04

Continue in a native target workspace.

Converted assets need review. In the Power BI workspace, teams can inspect the semantic model, edit DAX and Power Query, review report structures, and prepare PBIP or PBIT packages. Keeping conversion and development together makes it possible to resolve gaps before handing assets to the people responsible for deployment.

Explore the Power BI workspace
05

Agree on acceptance before cutover.

Define reference data and expected results, then test totals, filters, time logic, data access, and refresh behavior. Assign owners to exceptions and keep source reporting available until the target has been accepted. Publishing an artifact is one milestone; an agreed support and rollback plan completes the release decision.

Get the migration acceptance checklist

Directional migration paths

Match the workflow to your platforms.

Scope and availability vary by path. Confirm source versions and asset types during assessment.

Supported directionTableau to Power BI

Single workbook · Single workbook with Tableau Server connection

  • Parsed Tableau workbook inventory
  • Converted semantic model and report structures
  • Translated calculations with validation
  • PBIP/PBIT output in a workspace for review before release
Read the migration guide
Supported directionPower BI to Tableau

Power BI semantic model to Tableau workbook

  • Power BI model extraction
  • Tableau data-source and workbook mapping
  • Calculation and field translation plan
  • Tableau workspace review loop
Supported directionTableau to Looker

Template-based LookML generation · Agent-backed Tableau to LookerSQL conversion

  • LookML views, models, explores, and dashboard objects
  • LookerSQL translated calculation bodies
  • Looker workspace populated for review
  • LookML download and deploy flow
Supported directionTableau to Omni

Tableau workbook to Omni documents import payload

  • Omni topics, views, dashboards, and tiles
  • Documents-import payload
  • Workspace review and validation
  • Publish to Omni action
Supported directionLooker to Power BI

LookML project to Power BI workspace

  • LookML model, view, explore, measure, and dimension extraction
  • Target semantic model mapping
  • DAX and SQL translation review
  • Power BI workspace validation
Supported direction, multiple input variantsCognos to Power BI

Report migration · Data module migration · Package migration · Multiple report IDs · Multiple report files · Cube migration · Offline cube migration

  • Cognos report/package/module inventory
  • Prompt, query, determinant, layout, and dependency analysis
  • Power BI model and report mapping
  • Readiness notes and a validation queue
Read the migration guide
Supported direction, multiple input variantsMicroStrategy to Power BI

Single report · Single report with prompts · Multiple reports · Single dossier · Multiple dossiers · Single cube · Schema objects · Hybrid migration

  • Project, report, dossier, cube, metric, and attribute inventory
  • Prompt, filter, schema object, and dataset analysis
  • Power BI semantic model mapping
  • Validation, exception queue, and conversion history

UNV universe migration · UNX universe migration · Web Intelligence report migration

  • Universe, report, prompt, LOV, context, and variable inventory
  • Business Layer and Data Foundation analysis
  • Power BI semantic model mapping
  • Readiness and validation outputs
Supported directionSalesforce to Power BI

Salesforce reports, dashboards, objects, and formulas to Power BI

  • sObject, report, dashboard, and formula inventory
  • Formula translation and relationship mapping
  • Power BI model and visual plan
  • Parity validation before release

Frequently asked questions

Your questions, answered.

Can CoDash migrate Tableau to Power BI?

Yes. The documented Tableau to Power BI path supports a single workbook, including a variant with a Tableau Server connection. Deliverables include parsed inventory, converted semantic model and report structures, translated calculations with validation, and PBIP/PBIT output. Source-specific gaps still require review.

Is BI migration fully automatic?

CoDash assists analysis, conversion, and validation, but platform semantics and reporting requirements differ. Teams review target models, resolve exceptions, reconcile business results, and approve publishing. The amount of manual work depends on the source assets and migration path.

How should we estimate migration effort?

Start with inventory and rationalization, then migrate a representative sample. Use the observed calculation complexity, dependency gaps, validation work, and business acceptance requirements to estimate subsequent waves.

Keep exploring

BI modernization

Your BI journey: understand, prioritize, deliver, operate, improve.

The enterprise BI modernization journey, stage by stage: understand the estate, prioritize investment, deliver the change, operate what you released, and keep improving. Owners and outputs for each stage.

Explore BI rationalization

A smaller backlog. A clearer BI estate.

Rationalize your BI portfolio with CoDash. Review duplicate reports and shared logic, select canonical assets, and decide what to keep, merge, retire or migrate.

Explore Guides & checklists

A practical starting point for your team.

Read the readiness guide, migration checklist, and platform migration walkthroughs.

Browse BI resources

A clear next step

Make a plan for your BI estate.

Choose the platform you use and explore how CoDash supports your next step.

Start with your platform