Try our new research platform with insights from 80,000+ expert users

Matillion Data Productivity Cloud vs Skyvia comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 31, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Matillion Data Productivity...
Ranking in Cloud Data Integration
9th
Average Rating
8.4
Reviews Sentiment
7.4
Number of Reviews
27
Ranking in other categories
No ranking in other categories
Skyvia
Ranking in Cloud Data Integration
33rd
Average Rating
9.0
Reviews Sentiment
7.8
Number of Reviews
1
Ranking in other categories
Data Integration (54th)
 

Mindshare comparison

As of May 2025, in the Cloud Data Integration category, the mindshare of Matillion Data Productivity Cloud is 3.4%, down from 4.7% compared to the previous year. The mindshare of Skyvia is 0.2%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Data Integration
 

Featured Reviews

Tomáš Hronek - PeerSpot reviewer
Used for wrangling or transforming data from sources like S3 and Databricks
I use Matillion ETL for wrangling or transforming data from sources like S3 and Databricks The most valuable feature of Matillion ETL is the UI experience in which you can drag and drop most of the transformation. Sometimes, we have issues with the solution's stability and need to restart it for…
RH
The product works, is simple to use, and is reliable.
Error handling. This has caused me many problems in the past. When an error occurs, the event on the connection that is called does not seem to behave as documented. If I attempt a retry or opt not to display an error dialog, it does it anyway. In all fairness, I have never reported this. I think it is more important that a unique error code is passed to the error event that identifies a uniform type of error that occurred, such as ecDisconnect, eoInvalidField. It is very hard to find what any of the error codes currently passed actually mean. A list would be great for each database engine. Trying to catch an exception without displaying the UniDAC error message is impossible, no matter how you modify the parameters in the OnError of the TUniConnection object. I have already implemented the following things myself. They are suggestions rather than specific requests. Copy Datasets: This contains an abundance of redundant options. I think that a facility to copy one dataset to another in a single call would be handy. Redundancy: I am currently working on this. I have extended the TUniConnection to have an additional property called FallbackConnection. If the TUniConnection goes offline, the connection attempts to connect the FallbackConnection. If successful, it then sets the Connection properties of all live UniDatasets in the app to the FallbackConnection and re-opens them if necessary. The extended TUniConnection holds a list of datasets that were created. Each dataset is responsible for registering itself with the connection. This is a highly specific feature. It supports an offline mode that is found in mission critical/point of sale solutions. I have never seen it implement before in any DACs, but I think it is a really unique feature with a big impact. Dataset to JSON/XML: A ToSql function on a dataset that creates a full SQL Text statement with all parameters converted to text (excluding blobs) and included in the returned string. Extended TUniScript:- TMyUniScript allows me to add lines of text to a script using the normal dataset functions, Script.Append, Script.FieldByName(‘xxx’).AsString := ‘yyy’, Script.AddToScript and finally Script.Post, then Script.Commit. The AddToScript builds the SQL text statement and appends it to the script using #e above. Record Size Calculation. It would be great if UniDac could estimate the size of a particular record from a query or table. This could be used to automatically set the packet fetch/request count based on the size of the Ethernet packets on the local area network. This I believe would increase performance and reduce network traffic for returning larger datasets. I am aware that this would also be a unique feature to UniDac but would gain a massive performance enhancement. I would suggest setting the packet size on the TUniConnection which would effect all linked datasets.
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
852,780 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
15%
Manufacturing Company
9%
Healthcare Company
5%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Matillion ETL?
The new version with the Productivity Cloud is very simple. It's easy to use, navigate, and understand.
What is your experience regarding pricing and costs for Matillion ETL?
While pricing can be an issue compared to other solutions, Matillion Data Productivity Cloud offers discounts and special deals, especially when dealing with high-volume clients or fewer existing c...
What needs improvement with Matillion ETL?
There are problems with GCP connectivity. Specifically, connections to BigQuery for extracting information are complex, and the optimization of the extraction process requires improvements. I raise...
Ask a question
Earn 20 points
 

Also Known As

Matillion ETL for Redshift, Matillion ETL for Snowflake, Matillion ETL for BigQuery
Skyvia, Skyvia Data Integration
 

Overview

 

Sample Customers

Thrive Market, MarketBot, PWC, Axtria, Field Nation, GE, Superdry, Quantcast, Lightbox, EDF Energy, Finn Air, IPRO, Twist, Penn National Gaming Inc
Boeing, Sony, Honda, Oracle, BMW, Samsung
Find out what your peers are saying about Amazon Web Services (AWS), Informatica, Salesforce and others in Cloud Data Integration. Updated: May 2025.
852,780 professionals have used our research since 2012.