Migrating from METL to Maia - what is your experience so far?

Maia
,
1

We are long-time METL users and generally enjoy the experience. It has a responsive uncluttered user interface with fairly intuitive components.
Moving over to Maia and just noticing the interface gets cluttered very quickly, it seems slower responsively in the design surface than METL.
We are committed to the migration so does it get better? Do I need to give it time?
Just curious about other users experience with Maia and in particular with the experience pre- and post- METL migration.

Cheers!

2

Hi,

We are currently doing migration from METL to MAIA. There are some features that is available on METL that is missing on MAIA, features that help us on day to day.

  1. RUN_HISTORY_ID is not available on MAIA it is replaced by EXECUTION_ID which is from numeric to alpha numeric.
  2. Data Sampling is missing on Query Result to Grid/Scalar. Not their priority as per our PS Team.
  3. Pipeline designer is sometimes slow.
  4. There are few bugs on the components that we raised and tag as known issue.
  5. Few Components that we have on METL is missing on MAIA, ensure to engage on your PS Team as it will take months as in months of waiting for them to release it. For example Zuora and Eloqua Connector exists on METL requested since Nov last year, initially they promise on February 2026 but didnt delivery latest promise is on June or July 2026 stable release.
3

Those are some good insights, thanks for sharing!

I have some suggestions for improvement that I may start entering as support tickets.

For example, in the Shared Jobs in METL I can set the job variables on the design surface for testing then again when I actually create the shared job - they are not the same.
In Maia - it uses the values and descriptions from my design surface when I create the shared pipeline, too bad if they are test values you must set them up to be the exact values and description you want everyone to see when you share the pipeline, since you can’t change them from the shared pipeline screen.

On your point 1 above I did have to dig a bit but finally discovered the documentation on “system shared variables” which is a similar concept to the automatic variables in METL.