thank you for raising this very good question.
First of all, I would like to mention that we will shortly introduce a feature to easily migrate already existing analyses from Process Analytics to the Studio -stay tuned But why would you wanna do that? And why start building new analyses in the Studio instead of Process Analytics?
The benefits of moving analyses to the Studio and building analyses in Studio are
a) you have Version Control at the Package level, there is no version control in Process Analytics
b) you can have analyses linked to different data models in the same package
c) as you mentioned, you have the possibility to combine Analyses and Views (with new visualization and actionable components) in one package and use it in parallel to leverage the benefits of both. Also extending the capabilities of analysis with view components is way easier if the analyses are already in the Studio
d) you have one place where you can maintain and build both, Analyses and Apps. Even if the analysis does not require new Studio capabilities, the use and edit experience is better if it is always in the same place.
e) Process Automation already fully migrated into Studio. The Studio will be THE place to create new content of any kind. That also means long-term, the Studio will be the sole place where you build analyses, and Process Analytics will be replaced by it at some point. With the feature we will release soon, we want to give customers and partners already a chance to explore the Studio and move the first analyses.
And as you said, the question to either build a View or an Analysis depends on what you want to achieve right now. With Views you can build persona-specific views, optimized for daily work, integrating the Task execution or defining priorities.
Currently, to provide ad-hoc analyses and drill-downs Analyses are a bit more flexible and you can achieve fast results. Long-term, as we further and further developing the Views and analytical components for Views (like the Sankey or Treemap diagram), as well as the build experience of Views and Knowledge Models, they will become more powerful and also be the first choice for analytical use cases.
If you have further questions please do not hesitate to reach out to us!
All the best
Sabeth and the Celonis Studio Team