Item: Matillion
Rating: 10
Author: Vinod Kumar C

Use Cases and Deployment Scope

We have data residing in multiple systems across various applications using disparate database applications.
We were looking for a robust tool that would be able to bring in the data from these into our Datawarehouse.
And that is where Matillion ETL tool came into picture.
So we are using Matillion to integrate the data, transform the data by applying Business logic and finally making it available for the Business users to make informed decisions w.r.t Sales, Campaigns and Promotions and also to understand and address the pain areas of our Customers.

Pros and Cons

Connectors for multiple systems/applications spread across Databases, APIs, Files, etc.
The concept of Shared jobs for reusability
Seamless integration with Multiple Cloud providers

UI Feature to track job changes
Option to put the comments while importing/exporting the jobs
Option to search for component names inside the opened job in canvas

Key Insights

Do you think Matillion delivers good value for the price?

Yes

Are you happy with Matillion's feature set?

Yes

Did Matillion live up to sales and marketing promises?

Yes

Did implementation of Matillion go as expected?

Yes

Would you buy Matillion again?

Yes

Return on Investment

Quick turnaround time for Data integrations
No code approach - drag and drop components to do the task
Reusability of the Orchestration flow using Shared jobs

Usability

The quick turn around time to build new Integrations with minimum to no-code usage is very much helpful in delivering our deliverables.
The ability to re-use an existing Orchestration flow by using the Shared jobs is another good feature to build the Integrations very quickly and easily.

Time to Value

We were up and running within 2 weeks of procuring the Matillion ETL.
The very first integrations we started were that of Salesforce and that was both inbound from Salesforce and outbound to Salesforce. We were able to build 5 to 6 such Outbound integrations within a month.
And then there were around 20 Inbound integrations from Salesforce which we were able to achieve in another month.

Scalability

We are using Matillion to integrate data from various data sources like MySQL server that is residing on Amazon AWS, from Oracle on-prem database, from Sharepoint, from Teradata cloud, etc.

Alternatives Considered

The out of the box connectors for various data sources especially for Salesforce is the main reason we chose Matillion in terms of source connectivity.
Aside connectors, Matillion provides some unique features like Shared jobs, Grid variables, etc that are very helpful in quick development.

Other Software Used

Snowflake, Alteryx

Likelihood to Recommend

I prefer Matillion for:

Salesforce integrations. Not just extracting the data from Salesforce, but it has capability to even push the data to Salesforce.
API integrations: Nowadays, all the applications are exposing their data using APIs instead of direct connectivity for security and other reasons, and Matillion has the ability to extract from all kinds of API sources.
The ability to run the same job in other environment by setting up different environments within the same project.

Scheduling is very basic and does not have advanced capabilities. So this needs to be improved.

Matillion - Robust ETL tool

Overall Satisfaction with Matillion