Data Governance Systems Specialist at a energy/utilities company with 1,001-5,000 employees
Real User
Top 5
Jan 21, 2026
In terms of handling diverse data sources, Qlik Replicate does exhibit certain shortcomings.Other areas of Qlik Replicate that could be improved include its ability to serve as a single point tool, similar to Databricks and Azure Data Lake, depending on the kind of capabilities required. I believe that having updated documentation is crucial as we encountered a scenario while going through documentation that had not been updated since 2024, which introduced risks since we rely on accurate documentation for task imports and endpoint re-credentialing considerations before reaching out to customer support. Additionally, functionalities for running standardized data quality rules and validation logic, along with exception monitoring similar to what is available in Databricks, would be beneficial for users. While Qlik Replicate is scalable, I find there are limitations. When deploying a tool, it can be centralized, decentralized, or federated, depending on the organization's control and responsibility preferences. We successfully scaled several of our Oracle RDBMS systems simultaneously, including PeopleSoft HR and our network access request systems. However, addressing the shortcomings we discussed would enhance its competitiveness in the market.
Qlik Replicate could be improved in the next release by incorporating more monitoring options to monitor the logs. Currently, log monitoring is not easily accessible, so there should be improvements in this area. Regarding additional improvements, since it is not open source, there is dependency on Qlik support. The system could be scaled to include more sources and functions. Currently, there are limited transformations available in Qlik Replicate which could be expanded. Additionally, support response times could be improved as there are sometimes delays in receiving replies to support cases.
There is complexity involved in the licensing part of this system. It is a core-based licensing, which, especially in the banking industry, results in the system capacity being utilized up to a maximum of 60%. The remaining 40% acts as a buffer for safety purposes.
Some features on the graphical user interface are clunky. Accessing certain functions like replicating from a table after a specific date requires obscure key combinations, which could be made more intuitive and visible.
The disadvantage is, I think, people are not going for this license because it is not marketed properly. Qlik was not promoting it because Talend was acquired at the same time. So Talend has become their primary product. Compose was not being sold much. The other reason is there is a tool called Qlik Cloud Version, which is a combination of Compose and Qlik Replicate. So, Compose was not promoted much by Qlik. So, I started to concentrate on Talend more. This was an affair of around two or three months.
I wish Qlik Replicate had better built-in scheduling for initial table copies (ITCs) and full loads. Some features can also be overly dependent on each other. So, there is room for improvement. For example, one driver will not support the other source driver. So, it would be helpful if Qlik was clearer about driver versions, such as which ones work or don't work with specific sources. Another area of improvement is that full loads could be a bit faster. A tool like Informatica has both good replication and scheduling features.
Senior Vice President at Polestar Solutions & Services India Pvt Ltd
Reseller
Sep 29, 2023
Qlik Replicate's pricing could be improved. The solution's flexibility to work with APIs should also be improved since it is very weak in working with APIs.
In various scenarios, an important consideration is when we encounter issues and Qlik Replicate suggests reloading a specific table. If we face any problems or encounter errors with that table, it becomes necessary to make a change in Qlik Replicate. Performing a full reload every time is not feasible or practical. Instead, we should identify the specific issues and address them without repeating the entire reloading process. Based on this approach, we can investigate and resolve the problem by performing targeted loads from the source itself. This change aligns with my perspective and is something I would like to implement.
An issue we have is that it's not possible to replicate the QVC files in data analytics. It would be helpful if they could solve that. When it comes to metadata, the business name of the fields could be improved to have a catalog very close to the user to link the technical names to the business name.
Business Intelligence Architect at a manufacturing company with 10,001+ employees
Real User
Aug 30, 2022
They can do a better job in the performance. They don't do much compression on the data migration. That's the one thing they need to fix. We'd like better connectivity. Initial migrations are taking up too much time. They can improve on replicating to multiple targets.
Director of Enterprise Services at a computer software company with 10,001+ employees
MSP
Feb 9, 2022
As Qlik Sense is filling all the use cases that we need it to do, the only area for improvement I could think of for this product is for them to provide better support. We'd also like to see more automations and more integrations with third-party solutions and tools in the next version of this product.
Managing Partner at a tech services company with 51-200 employees
Real User
Jan 5, 2022
This product could be improved by providing more insight regarding errors. One of our customers that uses Qlik Replicate has had an issue. We tried to debug it, but we could not trace the error message. The infrastructure site should give us more insight about errors. Qlik Replicate is not a business solution, it's an IT solution. The reporting tools and bug site should be improved.
Software Engineer at a tech vendor with 1,001-5,000 employees
Real User
Nov 17, 2021
When you remote into it the Qlik Replicate UI a lot of times it just freezes. We set up the EC2, to allow them to go to the server and click on the Replicate icon, it just opens up and just sits there. At that point, we have to go into the EC2 and then reboot the server. This should be fixed, it is frustrating. When we do receive errors when the solution suddenly fails it will give a message of "Error." You have to go and figure out which setting you have to tweak to get the actual error. This could be improved by being more descriptive or more intuitive. They have eight different options of things the error would say, such as enhance logging, but you don't really know what that means. The wording doesn't tell you if it fails. It makes it difficult when trying to find the actual problem. In a feature release, they could improve the solution by making it easier to use two different destinations. If we want to do have on-premise and in the cloud, it seemed difficult when I was attempting the process. It would be useful to just have one source and then two different destinations, using the same transformations and other configurations.
We have technical people who work with it. I do not have a lot of feedback to provide at this stage. We want to implement a data lake but that's at the second stage to be integrated with the other tools that we use, which are Qlik. Since we use Qlik, we intend to leverage Attunity's capabilities because Attunity is now part of the portfolio.
Qlik Replicate offers log-based change data capture, supporting real-time data updates without affecting source databases. It manages schema changes automatically and ensures seamless data distribution. The platform is user-friendly, enables late-stage transformation, and supports incremental replication and real-time analytics.Qlik Replicate is known for efficiently capturing data changes with minimal impact on source databases. Its log-based change data capture capabilities ensure quick...
In terms of handling diverse data sources, Qlik Replicate does exhibit certain shortcomings.Other areas of Qlik Replicate that could be improved include its ability to serve as a single point tool, similar to Databricks and Azure Data Lake, depending on the kind of capabilities required. I believe that having updated documentation is crucial as we encountered a scenario while going through documentation that had not been updated since 2024, which introduced risks since we rely on accurate documentation for task imports and endpoint re-credentialing considerations before reaching out to customer support. Additionally, functionalities for running standardized data quality rules and validation logic, along with exception monitoring similar to what is available in Databricks, would be beneficial for users. While Qlik Replicate is scalable, I find there are limitations. When deploying a tool, it can be centralized, decentralized, or federated, depending on the organization's control and responsibility preferences. We successfully scaled several of our Oracle RDBMS systems simultaneously, including PeopleSoft HR and our network access request systems. However, addressing the shortcomings we discussed would enhance its competitiveness in the market.
Qlik Replicate could be improved in the next release by incorporating more monitoring options to monitor the logs. Currently, log monitoring is not easily accessible, so there should be improvements in this area. Regarding additional improvements, since it is not open source, there is dependency on Qlik support. The system could be scaled to include more sources and functions. Currently, there are limited transformations available in Qlik Replicate which could be expanded. Additionally, support response times could be improved as there are sometimes delays in receiving replies to support cases.
There is complexity involved in the licensing part of this system. It is a core-based licensing, which, especially in the banking industry, results in the system capacity being utilized up to a maximum of 60%. The remaining 40% acts as a buffer for safety purposes.
Some features on the graphical user interface are clunky. Accessing certain functions like replicating from a table after a specific date requires obscure key combinations, which could be made more intuitive and visible.
The disadvantage is, I think, people are not going for this license because it is not marketed properly. Qlik was not promoting it because Talend was acquired at the same time. So Talend has become their primary product. Compose was not being sold much. The other reason is there is a tool called Qlik Cloud Version, which is a combination of Compose and Qlik Replicate. So, Compose was not promoted much by Qlik. So, I started to concentrate on Talend more. This was an affair of around two or three months.
The product should improve its licensing limitation.
I wish Qlik Replicate had better built-in scheduling for initial table copies (ITCs) and full loads. Some features can also be overly dependent on each other. So, there is room for improvement. For example, one driver will not support the other source driver. So, it would be helpful if Qlik was clearer about driver versions, such as which ones work or don't work with specific sources. Another area of improvement is that full loads could be a bit faster. A tool like Informatica has both good replication and scheduling features.
Qlik Replicate is a little fuzzy sometimes as to how it's priced. It would be better if the solution’s pricing were more obvious.
Qlik Replicate's pricing could be improved. The solution's flexibility to work with APIs should also be improved since it is very weak in working with APIs.
In various scenarios, an important consideration is when we encounter issues and Qlik Replicate suggests reloading a specific table. If we face any problems or encounter errors with that table, it becomes necessary to make a change in Qlik Replicate. Performing a full reload every time is not feasible or practical. Instead, we should identify the specific issues and address them without repeating the entire reloading process. Based on this approach, we can investigate and resolve the problem by performing targeted loads from the source itself. This change aligns with my perspective and is something I would like to implement.
There is room for improvement in the UI. The UI and data version control can be improved.
An issue we have is that it's not possible to replicate the QVC files in data analytics. It would be helpful if they could solve that. When it comes to metadata, the business name of the fields could be improved to have a catalog very close to the user to link the technical names to the business name.
We would like to see more details in messages about errors with the system.
They can do a better job in the performance. They don't do much compression on the data migration. That's the one thing they need to fix. We'd like better connectivity. Initial migrations are taking up too much time. They can improve on replicating to multiple targets.
As Qlik Sense is filling all the use cases that we need it to do, the only area for improvement I could think of for this product is for them to provide better support. We'd also like to see more automations and more integrations with third-party solutions and tools in the next version of this product.
This product could be improved by providing more insight regarding errors. One of our customers that uses Qlik Replicate has had an issue. We tried to debug it, but we could not trace the error message. The infrastructure site should give us more insight about errors. Qlik Replicate is not a business solution, it's an IT solution. The reporting tools and bug site should be improved.
When you remote into it the Qlik Replicate UI a lot of times it just freezes. We set up the EC2, to allow them to go to the server and click on the Replicate icon, it just opens up and just sits there. At that point, we have to go into the EC2 and then reboot the server. This should be fixed, it is frustrating. When we do receive errors when the solution suddenly fails it will give a message of "Error." You have to go and figure out which setting you have to tweak to get the actual error. This could be improved by being more descriptive or more intuitive. They have eight different options of things the error would say, such as enhance logging, but you don't really know what that means. The wording doesn't tell you if it fails. It makes it difficult when trying to find the actual problem. In a feature release, they could improve the solution by making it easier to use two different destinations. If we want to do have on-premise and in the cloud, it seemed difficult when I was attempting the process. It would be useful to just have one source and then two different destinations, using the same transformations and other configurations.
We have technical people who work with it. I do not have a lot of feedback to provide at this stage. We want to implement a data lake but that's at the second stage to be integrated with the other tools that we use, which are Qlik. Since we use Qlik, we intend to leverage Attunity's capabilities because Attunity is now part of the portfolio.
Qlik can be made more user-friendly. Support-wise, this solution is in need of improvement.