Hi Vineeth,

Yes, migrating the Alteryx data-processing logic into Mendix is a valid approach, especially if your goal is to bring data processing, datasets, and dashboards together into a single application.

A possible architecture would look like:

SAP / Snowflake → Mendix → Data processing & business logic → Datasets → Dashboards

Mendix can connect directly to external sources like SAP (via OData services, RFC/BAPI, or SAP Cloud connectivity, depending on your SAP landscape) and Snowflake (via JDBC/database connectors or REST APIs), so the integration piece is achievable.

That said, before migrating everything, I'd recommend first reviewing your existing Alteryx workflows and splitting them into two categories:

• Simple data transformations/business rules (filtering, joins, calculated fields, conditional logic) — these can be moved into Mendix microflows/nanoflows fairly well.
• Heavy data-processing workloads (large-scale aggregations, complex statistical transforms, high-volume batch processing) — these are often better left in the source platform (SAP/Snowflake) or handled through a dedicated data-processing/ETL layer, since Mendix's runtime isn't optimized for that kind of bulk compute the way Alteryx is.

Once the data is available in Mendix (either synced into the domain model or queried live), you can build dashboards using native widgets like Charts, Data Grids, and Pivot tables, or integrate with tools like Power BI for more advanced reporting needs.

So in short — yes, it's definitely possible, but I'd suggest evaluating your current Alteryx workflows and data volumes first to decide what should be migrated into Mendix versus what should stay in the data platform layer, so Mendix ends up serving as the app/logic/dashboard layer rather than a full ETL replacement.

Hope this helps!

Kindly mark this as the accepted answer if it helps.