Workspace plugin model
Each BI platform is organized around local config, domain services, workspace tools, and optional routes so teams can add and operate targets without broad runtime rewiring.
Agent workspace platform
CoDash
Analyze, rationalize, develop, migrate, manage, validate, publish, and automate Business Intelligence assets from one agent workspace platform.
6Operating modes9BI platforms9Migration paths
Platform network
Operate one BI platform or many from the same lifecycle workspace.
CoDash connects source systems, databases, BI tools, users, and operating workflows so teams can migrate, develop, operate, and manage mixed BI estates without splitting the work across disconnected tools.
Connect existing BI platforms, source systems, databases, and teams
Run single-platform workspaces or multi-platform modernization programs
Carry migrated and from-scratch work into validation, publish, and management
CoDashAgent workspaceAnalyze, build, migrate, publish, manage
Users and teamsBI owners, analysts, admins, and delivery leads
Source systemsERP, CRM, SaaS apps, files, APIs, and business domains
Databases and lakehousesSQL, warehouses, lakehouses, extracts, and semantic layers
BI platform meshSingle or multi-platform operations
Power BI
Tableau
Looker
Cognos
MicroStrategy
SAP BusinessObjects
Salesforce
Omni
Qlik
Power BITableauLookerCognosMicroStrategySAP BusinessObjectsSalesforceOmniQlikMigrateRoute-specific conversion and validation
DevelopBuild or repair platform-native assets
OperatePublish, monitor, refresh, and validate
ManageVersions, lineage, access, logs, and changes
Lifecycle
One product flow across the full BI modernization cycle.
The shipping app is organized around practical operating modes: analyze the estate, rationalize the portfolio, develop in workspaces, migrate between platforms, manage published BI, and automate repeatable operations.
01
Analyze
Inventory and readiness
Upload or connect BI assets and assess structure, dependencies, complexity, and migration readiness across the estate.
02Rationalize
Portfolio decisions
Find duplicate reports, score assets, compare clusters, and decide what should be kept, merged, archived, or reviewed.
03Develop
Agent workspaces
Create and modify semantic models, LookML, Tableau workbooks, calculations, joins, parameters, worksheets, and dashboards in governed workspaces.
04Migrate
Conversion execution
Run licensed source-to-target paths such as Tableau, Cognos, MicroStrategy, Looker, SAP BO, and Salesforce to Power BI.
05Manage
Round-trip operations
Maintain published BI assets with workspace state, validation results, change history, BI server connections, and publication metadata.
06Automate
Repeatable operations
Create workflow templates and scheduled jobs for validation, publishing, monitoring, and repeat migration tasks.
Agent workspaces
Develop and manage BI assets, not only migrate them.
The workspace architecture supports migrated and from-scratch work. Each platform workspace carries its own tools, domain services, document state, validation, and publish path.
Scoped agent surface
The active agent sees the allowed tools for the selected workspace plus shared integrations, keeping Power BI, Looker, and Tableau actions separated.
Platform-native document state
Workspace changes persist as platform-native assets: semantic models, LookML objects, Tableau data sources, joins, calculations, parameters, worksheets, and dashboards.
Consistent action paths
Frontend saves and chat-driven agent updates can call the same backend implementation, so validation, errors, and audit history stay consistent.
Publish and connection management
Workspaces can resolve BI server connections, validate changes before publish, and retain deployment metadata for ongoing operations.
From-scratch or migrated work
Teams can create a new workbook or model from data connections, continue a migrated asset, or maintain a published workbook in the same governed surface.
Power BI
- Semantic models
- DAX and M-query
- PBIP and publish flows
Looker
- LookML measures
- Dimensions and explores
- Shared save handlers
Tableau
- Data sources and joins
- Calculated fields and parameters
- Worksheets, dashboards, and publish
Workspace capabilities
Move from assessment to live operations without changing products.
The same workspace supports estate inventory, rationalization, platform-native development, migration execution, validation, publishing, change history, and ongoing management across one or many BI platforms.
Analyze workbooks, reports, models, packages, universes, LookML, and semantic assets
Score complexity and migration readiness before teams commit to a path
Find duplicates and consolidation candidates across the BI estate
Build and maintain BI assets in Power BI, Looker, and Tableau workspaces
Use scoped agent tools to edit models, measures, dimensions, calculations, joins, parameters, worksheets, and dashboards
Run source-to-target migrations with configurable data model and database options
Validate and fix DAX, M-query, LookML, Tableau calculations, relationships, and model health
Track jobs, workspaces, status, versions, changes, and audit-friendly activity
BI Estate Analyzer
Platform analyzers cover Tableau, Cognos, MicroStrategy, Looker, SAP BusinessObjects, and Power BI readiness views.
Matches the product's analyzer routes and license-gated platform model.Rationalization Engine
The product surfaces estate summaries, platform breakdowns, duplicate clusters, scoring, strategy templates, and run history.
Grounded in the rationalization workspace and job flow.Agent Development Workspaces
Power BI, Looker, and Tableau workspaces let teams create, inspect, maintain, validate, and publish BI assets with agent support.
Grounded in the workspace-plugin architecture from the active product PRDs.Migration Factory
Source-to-target paths remain first-class, with workspaces carrying converted models and workbooks into review, repair, validation, and publish.
Keeps migration as a product lane without making it the whole product.Managed Operations Layer
Shared handlers, workspace-scoped tools, job history, server connections, and publish workflows support ongoing BI management.
Aligned with PRD-26 shared-handler and scoped-tool patterns.Migration paths
Migration is a product lane, not the whole platform.
Paths are license-gated in the application, so the site names them as available product directions. Converted assets continue into workspaces for review, repair, validation, publishing, and management.
Tableau to Power BICognos to Power BIMicroStrategy to Power BILooker to Power BISAP BO to Power BIPower BI to TableauTableau to OmniTableau to LookerSalesforce to Power BI
Deployment paths
Choose SaaS speed or deploy CoDash inside your own cloud.
Some customers want a dedicated hosted tenant. Others need the platform to run inside their own Azure, AWS, or GCP network. Both paths support the same lifecycle workspaces across analysis, development, migration, operations, and management.
CoDash hosted SaaS
SaaS tenant
A dedicated CoDash tenant for the client, operated as SaaS with tenant-level isolation, managed updates, and faster onboarding.
Dedicated tenantManaged hostingTenant-scoped access
Compare deployment pathDeploy inside your networkClient cloud deployment
Run CoDash inside the client's own cloud and network boundary, with deployment options for Azure, AWS, or GCP.
AzureAWSGCPPrivate network
Compare deployment pathTeams
Built for teams that build, migrate, and operate BI assets.
The page language now follows the product team actually shipping: BI migration teams, analytics engineers, platform owners, and program leaders.
BI Migration Teams
- Assess source estates
- Plan migration waves
- Validate converted assets
Analytics Engineering
- Develop semantic models
- Repair DAX, M-query, LookML, and Tableau calculations
- Manage workspace changes
BI Platform Owners
- Maintain published workbooks
- Manage BI server connections
- Govern publish workflows
Program Leadership
- Track portfolio readiness
- Prioritize rationalization
- Monitor jobs and outcomes
Launch options
Start with one platform, one path, or one program lane.
Keep the first engagement concrete: scan a source estate, pilot a migration path, stand up a workspace development lane, or operate the full lifecycle model.
Estate Scan
DiscoveryStart with one source platform and produce an inventory, complexity view, and readiness summary.
- Platform upload or connection
- Readiness review
- Migration scope notes
Migration Pilot
Focused pathRun a controlled source-to-target path with validation and workspace review before scaling.
- One licensed migration path
- Workspace validation
- Issue and fix queue
Workspace Buildout
Development laneStand up a governed agent workspace for Power BI, Looker, or Tableau development and maintenance.
- Workspace configuration
- Agent tool surface
- Publish and management flow
Lifecycle Program
EnterpriseOperationalize analysis, rationalization, migration, development workspaces, management, and automation together.
- Multi-platform roadmap
- Governed workflows
- Implementation support
Request for demo
Choose the information you need and request a focused demo.
Use the guided flow below to select the lifecycle areas, BI platforms, deployment path, and operating questions you want us to prepare for. This is the single contact path for CoDash demo enrollment.