BI analysis, migration, and reporting

CoDash

Modernise your BI estate.

CoDash · Illustrative workflow · sample data

Who buys it: Heads of BI, analytics modernisation, and data platform teams
The job it addresses: Understand what exists across the BI estate, decide what matters, migrate selected assets, and build and validate reporting.
What you end up with: An inventory you can act on, migrated assets with their exceptions named, and validated native reporting.
Where it stops: Migration is directional and asset-scoped. CoDash does not convert any BI platform to any other; each supported path states its source, target, asset types, and unsupported constructs.

Next step

CoDash helps teams understand their BI estate, modernise selected assets, and build and validate reporting in platform-specific workspaces. Coverage varies by platform and migration path.

Discuss a BI assessment Go to the CoDash site

Plans and pricing live on the product site, where they stay current.

The workflow, end to end

Input, action, artifact, human review, outcome — and an honest account of how far the evidence currently goes.

One migration path, from inventory to a validated artifact

CoDash application — inventory, analyzer, migration, workspace, and validation surfaces · inspected 2026-09-26

Source-backed

1
Input
An inventory of the source estate and one explicitly chosen migration path.
2
Action
A selected report is converted along that path.
3
Artifact
The converted asset, plus the exceptions the conversion could not resolve.
4
Human review
A reviewer repairs the exceptions and runs a comparison against the source.
5
Outcome
A validated artifact, with its unsupported constructs recorded.

What this supports

Inventory, analysis, conversion, workspace authoring, and validation exist as implemented surfaces.
Exceptions and human repair are part of the intended workflow, not a failure of it.

What this does not support

Conversion fidelity for any path that has not been run and recorded.
That every object type in a listed platform converts.

Recording still owed

One recorded path over permitted sample assets: inventory → selected report → conversion → an identified exception → its repair → comparison results → reviewed export. Source and target versions and the supported object scope recorded alongside.

What it does today

Status is per operation and per platform, because that is the level at which it actually varies. A route existing in the product is not the same as a product owner releasing it.

CoDash capabilities by operation, platform scope, status and limitations
Operation	Platform scope	Status	Limitations
Inventory a BI estate and score complexity and dependencies	Source platforms admitted by the configured connectors	Source-backedreviewed 2026-09-26	Completeness is per source platform and must be validated for each environment. An inventory is an assessment input, not a migration decision.
Convert selected assets along a stated migration path	Directional paths published on the product site, including Tableau → Power BI, Power BI → Tableau, Tableau → Looker or Omni, and several legacy sources → Power BI	Source-backedreviewed 2026-09-26	Paths are directional and asset-scoped. Any-platform-to-any-platform conversion is not offered. Source and target versions, supported object scope, and unsupported constructs are stated per engagement; a path being listed does not mean every object type converts. Exceptions requiring human repair are expected and are part of the workflow.
Author, review, validate, and publish reporting in a platform workspace	Power BI, Tableau, Looker, and the other workspaces in product navigation	Source-backedreviewed 2026-09-26	One full author → review → validate → publish sequence is still to be recorded; until then this is not described as production-ready. Workspace availability differs by platform.
Run validation suites and compare source and target outputs	Validation suites exposed by the CoDash application	Source-backedreviewed 2026-09-26	Typed frontend clients and workflow documentation exist. An API client existing does not prove a successful backend validation run. Parity results are per artifact; no portfolio-wide accuracy figure is claimed.
Deploy as a dedicated hosted tenant or into a customer cloud	Hosted tenant; customer-operated Azure, AWS, or GCP	Plannedreviewed 2026-09-26	These options are offered on the product site. A reference configuration is confirmed per cloud before it is committed to; equivalent operational support across clouds is not inferred. Who operates backups, upgrades, monitoring, and incidents is agreed per deployment.
Manage the whole estate as a governed asset portfolio	Cross-platform estate	Plannedreviewed 2026-09-26	Estate-wide asset management and expanded agentic reporting sit on the roadmap. They are distinct from current workspace history and current report authoring.

How to read the status labels

Source-backed: The implementation exists in the inspected product source. It has not been demonstrated end to end here.
Demonstrated: A dated end-to-end run supports this capability, with environment, inputs and outputs recorded.
Available: A product owner has approved this capability for a stated customer scope and operating model.
Interactive preview — simulated execution: An illustrative interface or synthetic simulation. No live backend behaviour is implied.
Planned: Roadmap work. A component, route or partial API may already exist; the capability does not.

The other two products

Bahulam

Connected intelligence for real work.

Bring conversations, coding, tools, and domain workspaces around the task a team needs to complete.

Bahulam in detail

OneAdmin

Administration with clear authority.

Inspect enterprise administration context and route agent proposals to the administrator who is accountable for the decision.

OneAdmin in detail