Matillion Review
Updated July 09, 2021

Matillion Review

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Matillion

I have been using Matillion since March and it has been a nice experience. It's helping a lot during our ETL process from RDS to Redshift, both on AWS. I really appreciate the software features and their support team is always able to clarify doubts and lead us to the best solution for our business.
  • It's easy to understand
  • Support team
  • Good performance
  • The step of transformation is not 100% clear.
  • The price could be better.
  • Their forum is not that good.

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

  • Became possible to build our DW
  • We do not need to worry about the ETL software maintenance.
  • It's easy to keep it updated.
It's easy to understand how the flow works and all the features provided by the tool. You also can find some information on their website or Youtube channel.
I started reading about Matillion and after one week and talking to their support team I started my project and it was up and running after 2 weeks of developing.
It looks like we will not have any problem with scalability.
Amazon Redshift, Amazon Relational Database Service (RDS), Microsoft SQL Server
Matillion is nice if you don't want to spend time developing a home-built application to perform the ETL step and of course if you have a budget to spend on it. I don't suggest Matilion if you want to customize a lot or if you have a really specific environment to handle data.

Matillion Feature Ratings

Connect to traditional data sources
10
Connecto to Big Data and NoSQL
9
Simple transformations
10
Complex transformations
8
Business rules and workflow
8
Collaboration
10
Testing and debugging
9

Evaluating Matillion's Business Outcomes

Yes, after I started using Matillion our ETL process became much faster and we are running the instance on AWS only 1 or 2 hours per day which means we are not spending too much money but we are having many benefits once the process is much faster now and our visualization team can find the data more reliable.
Before Matillion we used to use software created by our own company which was already old to date and it was really hard for our new employees to get in of it. Using Matillion we are saving money on training for new partners and now we have a much more organized ETL environment.
Yes. We don't have a lot of data sources but all of them we were able to connect smoothly and import our data easily.
As an example of our data sources I can mention, Relational Databases on AWS running SQL SERVER, we have some input from S3 (text files) and of course, some excel files.
Matillion's implementation was really really easy and smooth, most of my questions I could find solve questions using their forum or sending them an e-mail which was replied to within 1 or 2 days. Their documentation about all the components I consider complete and with good examples of how to implement what you need.

Matillion Support

They have the answers and looks like they have a really technical team ready to reply to you but unfortunately, they are not so fast (I don't know why) which can put you in troubles if you are running against the time and if the whole project depends on this answer to keep going.
ProsCons
Good followup
Problems get solved
Kept well informed
No escalation required
Need to explain problems multiple times
Slow Initial Response
Yes
I would pay for premium support only if it were excellent support, I would not pay for the current support that they have right now. The tool is pretty good and already has some documentation, but if you need more details or something outside that, it's not a good experience for the user.
Yes - It was resolved but it took a couple of days what was not good from our perspective once that we had to stop the developing process to wait for their solution/explanation. Sometimes theses replies were not good enough and we had many times to ask again in order to have a better explanation
I had some troubles with one specific conversion between data types from SQL Server to RedShift and their documentation didn't mention how to perform that so, I contacted them in order to get instructions, it was not exceptional support but once they replied to me they could give me a satisfactory instruction about how should I proceed.