Where should we start?+
With a conversation about your estate, your reporting goals, and the decisions you are trying to make. That is usually enough to scope a first step — an assessment, a reporting improvement, or a look at a specific migration direction. You do not need to have chosen a platform strategy first.
Can we improve reporting without migrating anything?+
Yes, and for many teams that is the whole engagement. Reporting Studio works in platform-native workspaces for Power BI, Tableau, Looker, and Omni: meet a new requirement, repair a model that has drifted, or reconcile calculations. Your team reviews the proposed changes and decides what is released.
Which migration directions are actually supported?+
Nine directions, listed with their accepted input variants and the artifact you receive. Migration is directional — CoDash does not convert arbitrary source and target combinations — and scope is confirmed against your source versions and asset types during assessment rather than promised in advance.
Can CoDash run in our own cloud?+
Dedicated hosted SaaS and deployment into your own Azure, AWS, or GCP environment are both offered. Connectivity, identity, key management, and operational responsibilities are scoped with your platform team during deployment planning, and the responsibilities on each side are published on the deployment page.
What is available today, and what is preview?+
Analyze, Rationalize, Reporting Studio, and the workspace operations in Manage are available for the platforms listed on each page. Migration is available for supported directions only. In Automate, workflow definition, validation, and on-demand runs are available, while persistent schedules and historical run diagnostics are preview surfaces we will demonstrate rather than claim. Broader BI asset management and agent-coordinated reporting are roadmap items.