We use the solution for Salesforce data integration, multi-cloud approaches and processing bottlenecks. We deploy the solution in a hybrid format.
Data Integration Architect at InfoCepts
Great solution for Salesforce data integration, multi-cloud approaches and processing bottlenecks
Pros and Cons
- "The serverless capability and the packaging application of the solution are valuable."
- "It could be improved by including a buffer that saves data when there is a connectivity issue."
What is our primary use case?
What is most valuable?
The serverless capability and the packaging application of the solution are valuable, as all tools come with the solution and do not require additional license purchases.
What needs improvement?
Although the solution seems complete currently, it could be improved by including a buffer that saves data when there is a connectivity issue.
For how long have I used the solution?
We have been using the solution for a year and a half and are currently using the latest version.
Buyer's Guide
Informatica Intelligent Data Management Cloud (IDMC)
October 2026
Learn what your peers think about Informatica Intelligent Data Management Cloud (IDMC). Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
922,349 professionals have used our research since 2012.
What do I think about the stability of the solution?
The solution is very stable.
What do I think about the scalability of the solution?
The solution is scalable.
How was the initial setup?
The initial setup is straightforward. It takes a couple of days, but for migration, if you have to move over the code from one tool to another, it takes a lot of time.
What other advice do I have?
I rate the solution an eight out of ten. The solution is good but can be improved by a buffer that saves data when there is a connectivity issue. I recommend the solution because it has existed for a long time, and a lot of people already understand the tool. Additionally, the learning curve is effortless compared to the other tools.
Disclosure: My company has a business relationship with this vendor other than being a customer. Integrator
Technology Lead at a computer software company with 5,001-10,000 employees
Excellent scalability, in a class of their own, with time tested features
Pros and Cons
- "The most valuable features are data quality, data integrate transformations, match-merge, and a few MDM solutions we build into data quality transformation."
- "One area that could use improvement is the speed of the web interfaces. At present, they are very slow. I think it is essential that we are original and robust on-premises."
- "I have a lot of issues with their customer support and not getting the required technical information, which we actually need unless you can do a call with their senior technicians."
What is most valuable?
The most valuable features are data quality, data integrate transformations, match-merge, and a few MDM solutions we build into data quality transformation.
What needs improvement?
One area that could use improvement is the speed of the web interfaces. At present, they are very slow. I think it is essential that we are original and robust on-premises.
For how long have I used the solution?
I have worked with Informatica Data Quality for the past four and a half years.
What do I think about the stability of the solution?
You have excellent stability in the market in comparison to other data solutions.
What do I think about the scalability of the solution?
We find that scalability is not an issue and have installed it on fourteen servers.
How are customer service and support?
I have a lot of issues with their customer support and not getting the required technical information, which we actually need unless you can do a call with their senior technicians. Most of the cases that you raise are assigned to a junior technician.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is simple for a person who knows the company. If you already have one of their products you will find yourself comfortable doing the deployment. If you do not have experience with the company it is medium in relationship to complexity.
What other advice do I have?
I would continue to encourage the upgrades that are taking place every other one in order to release the new and relevant features. I would rate Informatica Data Quality an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Informatica Intelligent Data Management Cloud (IDMC)
October 2026
Learn what your peers think about Informatica Intelligent Data Management Cloud (IDMC). Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
922,349 professionals have used our research since 2012.
Senior Architect at Unilever Inc.
The solution offers good data governance and they provide helpful documentation and training
Pros and Cons
- "The solution offers good data governance."
- "Some functionalities can be a challenge in the cloud."
- "I've found that whatever functionalities are available on-prem, can become a bit of a challenge sometimes in the cloud."
What is our primary use case?
I'm a senior architect and we are partners with Informatica.
What is most valuable?
The solution offers good data governance.
What needs improvement?
I've found that whatever functionalities are available on-prem, can become a bit of a challenge sometimes in the cloud. There are no simple rules for customization so they need to be applied which is a challenge on the cloud side.
For how long have I used the solution?
I've been using this solution for four years.
What do I think about the stability of the solution?
Informatica stability is great. Even now, Purview has evolved a lot, but we haven't used it to the same extent.
What do I think about the scalability of the solution?
The solution is scalable.
How are customer service and support?
We are partnered with Informatica, so we don't have an issue with technical support.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Our preference is Purview when we're asked for a cloud solution because it's a cloud native and the same applies when taking cost into account. Deployment is easier with Purview. If an organization is going for a hybrid solution and there's a lot of governance and complex rules involved, my first choice is Informatica. If that's not the case then I go for Purview.
How was the initial setup?
Without experience, it may be somewhat difficult but I don't find it particularly complex because there's a lot of training and documentation available. We've already had a lot of experience so it's a piece of cake for us.
What's my experience with pricing, setup cost, and licensing?
Licensing costs are not fixed and I know that Informatica offers discounted prices to certain customers. Microsoft is cheaper.
What other advice do I have?
The solution is suitable for enterprise or mid-size organizations. But if there are customer-related or different domain issues and it has some kind of regulatory impact and a lot of external agencies come into the picture, then it's always good to go with the Informatica Axon.
I rate this solution eight out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Product Manager at a manufacturing company with 10,001+ employees
Mapping is easy and requires no coding; easier validation and transformation compared to other solutions
Pros and Cons
- "The feature I found most valuable in Informatica Intelligent Cloud Services is the mapping. You just drag, and it maps the data. Mapping is very easy, and it's no code. When you migrate data or when the data interaction happens at the source and destination, the challenge is that you'll get different formats. The validation has to be done in the middleware, and the transformation should happen. In Informatica Intelligent Cloud Services, it's very easy to do data validation and transformation compared to any other tool."
- "The feature I found most valuable in Informatica Intelligent Cloud Services is the mapping; you just drag and it maps the data, so mapping is very easy and it's no code."
- "Synchronicity is an area for improvement in Informatica Intelligent Cloud Services. For example, when you want real-time or immediate response from the solution when multiple technologies are involved, the integration with Informatica Intelligent Cloud isn't seamless, whether it's the MQ, JMS, or BES service, so the connectivity should be improved a bit. The data governance is good, but what's lacking is a demo. For example, if there's a new feature in Informatica Intelligent Cloud Services, the documentation for that new feature is limited, so if Informatica could give a more complete documentation and more demos, that would be better for the users. Right now, there isn't any issue with any of the features of the solution. It's the new feature awareness or user training, and improved connectivity that I'd like to see in the next version of Informatica Intelligent Cloud Services."
- "If you have to build an entire architecture, or when you compare from end-to-end, and multiple systems will be involved, then the performance of Informatica Intelligent Cloud Services needs improvement because connectivity issues in a complex system affect the performance."
What is our primary use case?
The company I work for has a huge supplier database with a billion records, so Informatica Intelligent Cloud Services is a data integration tool used for migrating the legacy data to Informatica MDM (master data management), then moving to the cloud. It's GCP and PCF (Pivotal Cloud Foundry).
I've also used Informatica Intelligent Cloud Services for moving data to SAP Ariba and SAP S/4HANA.
Informatica Intelligent Cloud Services is used for multiple technology in legacy mainframes, Oracle, some PeopleSoft, some Java-based applications, some in-house, QAD to MDM, or to SAP S/4HANA, or SAP Ariba, so it has various use cases, from legacy to cloud, legacy to MDM, and MDM to S/4HANA, etc.
What is most valuable?
The feature I found most valuable in Informatica Intelligent Cloud Services is the mapping. You just drag, and it maps the data. Mapping is very easy, and it's no code.
When you migrate data or when the data interaction happens at the source and destination, the challenge is that you'll get different formats. The validation has to be done in the middleware, and the transformation should happen. In Informatica Intelligent Cloud Services, it's very easy to do data validation and transformation compared to any other tool.
What needs improvement?
Synchronicity is an area for improvement in Informatica Intelligent Cloud Services. For example, when you want real-time or immediate response from the solution when multiple technologies are involved, the integration with Informatica Intelligent Cloud isn't seamless, whether it's the MQ, JMS, or BES service, so the connectivity should be improved a bit.
The data governance is good, but what's lacking is a demo. For example, if there's a new feature in Informatica Intelligent Cloud Services, the documentation for that new feature is limited, so if Informatica could give a more complete documentation and more demos, that would be better for the users.
Right now, there isn't any issue with any of the features of the solution. It's the new feature awareness or user training, and improved connectivity that I'd like to see in the next version of Informatica Intelligent Cloud Services.
For how long have I used the solution?
I've been using Informatica Intelligent Cloud Services for four years.
What do I think about the stability of the solution?
Informatica Intelligent Cloud Services has good stability.
What do I think about the scalability of the solution?
Informatica Intelligent Cloud Services is easy to scale.
How are customer service and support?
We contacted the Informatica Intelligent Cloud Services technical support team for some configurations which we needed that weren't available in the product, so we had to create a ticket. We talked to the product team biweekly and asked if they can get it done.
When the incident is high-priority because of the impact, the support has an SLA of twenty-four hours, especially if it's about configurations that aren't available in Informatica Intelligent Cloud Services. Otherwise, if the issue is about a feature already in production that we are already using and we need technical support, there's a four-hour SLA. That's the agreement we have with Informatica.
I would rate the Informatica Intelligent Cloud Services technical support team as four out of five.
Which solution did I use previously and why did I switch?
We've used the CIG (Cloud Integration Gateway), and we switched to Informatica Intelligent Cloud Services because CIG only works in an SAP environment. Informatica Intelligent Cloud Services, on the other hand, integrates with various environments, even non-SAP environments.
Compared to other solutions, Informatica Intelligent Cloud Services is also good with data governance, scalability, and it's no code.
How was the initial setup?
The initial setup for Informatica Intelligent Cloud Services was straightforward. The first time the solution was set up, the deployment took three weeks. My company had a center for excellence team that worked with the Informatica product team. The team from Informatica served as a guide throughout the deployment process.
The next deployments only took one to two hours of work. Once you get the approval for the SOWs and the contract, you'll have access to Informatica Intelligent Cloud Services then you can use it. It's usually a one-hour job.
On a scale of one to five, I'm rating my experience with setting up Informatica Intelligent Cloud Services as four.
What about the implementation team?
The first time we implemented Informatica Intelligent Cloud Services, we did it with the guidance of the Informatica product team, but during the next deployments, for example, when adding a new service, we did it ourselves.
What's my experience with pricing, setup cost, and licensing?
In terms of the licensing for Informatica Intelligent Cloud Services, we had the option of paying based on the number of users and paying based on the volume of data, and we went with the data volume licensing option.
Informatica Intelligent Cloud Services isn't as expensive as CIG. The pricing for it is okay, so I'm rating it a four out of five in terms of pricing.
We did use the email verification and address validation services which weren't part of the contract, so we had to pay additional fees for those services.
What other advice do I have?
I'm using data integration and app integration tools from Informatica, in particular, Informatica Intelligent Cloud Services and Informatica Data Quality.
I'm working with the latest update of Informatica Intelligent Cloud Services.
The solution doesn't require any maintenance after it's deployed.
In my company, across all departments, between five hundred to six hundred people use Informatica Intelligent Cloud Services.
On a scale of one to five, in terms of performance, I'd give Informatica Intelligent Cloud Services a four when it's used in a complex environment. If it's just at the source and destination without multiple technologies, then it's fine. If you have to build an entire architecture, or when you compare from end-to-end, and multiple systems will be involved, then the performance of Informatica Intelligent Cloud Services needs improvement because connectivity issues in a complex system affect the performance.
The advice I would give to anyone looking into implementing Informatica Intelligent Cloud Services is to get a POC done for the complex use cases for your organization. If the data hasn't been used for years and you have to move that to another source, be it the cloud or any other new technologies, take the data and do a POC for profiling, cleansing, and transformation for the different sets of data. For example, chunk the data, get the categories, then see how it is. Once that's done, look further and check if it's real-time, or it's a batch. If it's real-time, check how much time it's taking, and if it's aligned with your use case.
If you're using Informatica Intelligent Cloud Services for so many applications, do an end-to-end as a POC and check the time to see if it gives the time performance index, how the performance is, and how is it landing at the destination.
My rating for Informatica Intelligent Cloud Services is eight out of ten.
My company is a customer of Informatica.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Informatica Developer at a government with 1,001-5,000 employees
One of the leading ETLs with good in-built functionalities and helpful support
Pros and Cons
- "The solution is stable."
- "It's probably one of the leading lights in ETL."
- "Managing the licenses with the on-premises version was difficult."
- "The company that I moved out of was going to be switching off Informatica at some point due to licensing, et cetera, and they just chose to go to StreamSets with Snowflake for storage."
What is our primary use case?
We don't use profiling as much, however, we do use it, in certain cases, for profiling. We use the Analyst tool to do out-of-box, high-level profiling of data to see high-level quality of completeness, and uniqueness, et cetera. Mainly, we use the Developer tool to connect to the sources and to write data quality rules.
How has it helped my organization?
It has improved our organization.
We started from just pretty much having flat files, and then doing some basic transformations, then writing back to Excel or QFD files.
We gradually moved to more analytical tasks. You don't just do statistical data quality you also do analytical. You do lots of joins with other sources and do the consistency checks, and to do more complex logic, and build metrics.
We use Tableau on the back of it to present the data and data quality, and then monitor it. We use it more like a batch process to build pipelines, and then, using Tableau, monitor the results of it and those metrics. Now, we work more with live updates and do that more than the batch.
What is most valuable?
It's probably one of the leading lights in ETL. They have really good built-in functionalities, or algorithms, that you can use to transform or process data and validate and standardize.
The solution is stable.
It's not too had to set up the cloud version.
Support is helpful and responsive.
What needs improvement?
We are in this transition mode, where we haven't yet got IDMC, the cloud version, so we don't actually have hands-on experience and have not actually seen the features. All we rely on, at the moment, is just the available documentation. What I don't like on the IDQ side is just the fact that in the on-premises version, you have all these applications, with separate configurations. In the cloud solution, it is fixed so that you have everything on one platform.
The performance isn't as good on-premises. For example, when you install clients, it's slow compared to the cloud. Still, we need to see. We haven't experienced it ourselves.
The upgrades are a downside. On-premises you manage all the changes in the software. You have to do that yourself, and if there's some problem with compatibility, it makes things that much harder. With the cloud, everything is managed by Informatica on the servers.
Managing the licenses with the on-premises version was difficult. However, with the cloud, it will be much simpler.
For how long have I used the solution?
I've been using the solution for the last six or seven years.
What do I think about the stability of the solution?
Once you set everything up, it is pretty stable. It's reliable. There are no bugs or glitches and it doesn't crash or freeze. It is way more stable than Hadoop and other applications.
What do I think about the scalability of the solution?
In terms of scaling, we used the clusters, and the processing was on Hadoop side. If we needed any extra space or any service, it was just managed there, so it was outside of Informatica.
Originally, we had 20 people using the solution, and then it was reduced to less than ten.
We do use it as much as we can for its purposes. In the past, we used that for the whole ETL process with data loads, and then we moved to Hadoop storage. At the moment, we are only going to be using Cloud Data Quality and others for cleansing, standardization, and deduplication, and then using some other Azure capabilities.
How are customer service and support?
I've dealt with support in the past. There were issues, and we had to deal directly with Informatica for some hotfixes. They were good. They just got straight to the point and were helpful overall.
How would you rate customer service and support?
Positive
How was the initial setup?
It is way more complex to install on-premises than in the cloud.
With the cloud, the installation will be way easier since you only install these secure agents. They have many different connectors, so it is definitely less hustle to install all these machines, and all these applications. On-premises, it was more user-based. Now, it's service-based, and you just pay for what you use and the licenses as well.
We had myself, an architect, and a developer as well as help from Informatica while handling the setup.
We have about two or three people that can deploy and maintain the solution. They also cover other applications, not just Informatica.
What about the implementation team?
We had Informatica support, and we had an internal group of people with Informatica knowledge who handled the solution. For some parts, we were involved as well, and we handled them ourselves.
What was our ROI?
We're still in the early stages of moving toward the cloud. We have not seen an ROI yet.
What's my experience with pricing, setup cost, and licensing?
When you are using the on-premises version, managing the licenses is quite difficult. However, on the cloud, you just pay for what you use, and it's a lot easier. With the cloud, if you want MDM, you pay for it, and if you want PowerCenter, you pay for it; however, if you don't want it or don't use it, you don't pay. We'll just pay for Data Quality, as it has all of the features we need inside it.
I'm not involved in the conversations around licensing and agreements. That said, my understanding is that Informatica is pretty expensive. I'd likely rate it two to two and a half out of five in terms of affordability.
Which other solutions did I evaluate?
We definitely considered others and had StreamSets used for some other purposes. The company that I moved out of was going to be switching off Informatica at some point due to licensing, et cetera, and they just chose to go to StreamSets with Snowflake for storage.
I haven't researched enough about other products in relation to Informatica.
What other advice do I have?
We are moving to the cloud version. On-premises, we were on version 10.4.2, and that moved to 10.5. Soon, we will be on the cloud.
We're using IDMC, which is not just Data Quality. It has governance, Axon, and other applications in it.
We're just a customer.
I'd advise people to research use cases before beginning. Companies need to understand what they are trying to achieve, figure out their requirements, and then appraise the solution.
While Informatica is good in terms of Data Quality and is probably the leading option, you need to be clear about budget, et cetera.
I would rate the solution seven out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Senior Solution Architect at Intraedge
Can be built to handle integration, data modeling, and data governance under one umbrella
Pros and Cons
- "It comes with lot of features and is a one-stop-shop solution for integration, data modeling, and data governance. Everything can be built under one particular umbrella. If any issues come up, then there won't be any blame game saying that it could be an integration issue or an MDM hub issue because it's wholly owned by Informatica. That's the biggest advantage of Informatica MDM over that of any other tools that are available on the market."
- "It comes with lot of features and is a one-stop-shop solution for integration, data modeling, and data governance."
- "This is a costly solution. We have several customers who evaluate it but then look for other solutions because of the cost. At present, Informatica MDM comes as an on-premises or cloud-based solution. I would like to see them offer a SaaS-based MDM model. I think they are working on it."
- "This is a costly solution."
What is most valuable?
It comes with lot of features and is a one-stop-shop solution for integration, data modeling, and data governance. Everything can be built under one particular umbrella. If any issues come up, then there won't be any blame game saying that it could be an integration issue or an MDM hub issue because it's wholly owned by Informatica. That's the biggest advantage of Informatica MDM over that of any other tools that are available on the market.
It has given us a lot of flexibility in terms of solutions.
What needs improvement?
This is a costly solution. We have several customers who evaluate it but then look for other solutions because of the cost.
At present, Informatica MDM comes as an on-premises or cloud-based solution. I would like to see them offer a SaaS-based MDM model. I think they are working on it.
For how long have I used the solution?
I've worked with Informatica MDM for close to a year.
What do I think about the stability of the solution?
We have not had any performance issues.
What do I think about the scalability of the solution?
It is a scalable solution.
How are customer service and support?
The technical support is good depending on the SLA. Sometimes, they do have a busy schedule. When I contacted them for issues, someone joined the call if he/she was ready. Otherwise, we have had to wait for a day or two.
What's my experience with pricing, setup cost, and licensing?
Informatica MDM is a costly solution because it comes as a bundle. They are also globally positioning themselves and are definitely working on very upgraded technologies. If someone wanted to do it on the cloud, they have a lot of flexibility because they upgrade themselves according to the current needs. It definitely comes with a lot of features and that's the reason why it's costly.
The licensing cost should be approximately one million dollars. It's about four to five times that of other vendors.
What other advice do I have?
Take a look at your budget first and then proceed with this solution.
On a scale from one to ten, I give Informatica MDM a nine.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Principal Applications System Analyst at a university with 10,001+ employees
Quick on profiling and scales very well, but needs better UI and more reporting capabilities
Pros and Cons
- "There are a couple of valuable features. One is that it is very quick on the profiling. So, you get a very fast snapshot of the type of data that you're looking at from the profiling perspective. It can highlight anomalies in the data."
- "Their UI needs improvement. Their scorecards and reporting also need improvement. Their data quality reporting, especially their dashboards and scorecards, is lackluster at best. Its reporting capabilities are limited. If you want to do anything beyond its limited reporting capabilities, then you're going to have to use an external reporting tool such as Power BI or something like that."
- "Their data quality reporting, especially their dashboards and scorecards, is lackluster at best."
What is our primary use case?
A lot of times, we use it for basic profiling. That's its most common use case. Currently, we are also in the process of establishing a set of ongoing processes around Data Quality that would feed into and augment our current metadata. So, from that standpoint, our usage is primarily around some of the basic dimensions of data quality, such as completeness, conformity, consistency, timeliness, accuracy, etc. We measure each of those or at least create quality rules that measure each of those aspects. We're in the process of doing this for all of the data that's currently feeding into our analytics engine. These are some use cases that we're currently doing on a daily basis.
What is most valuable?
There are a couple of valuable features. One is that it is very quick on the profiling. So, you get a very fast snapshot of the type of data that you're looking at from the profiling perspective. It can highlight anomalies in the data.
The other valuable feature of the Data Quality tool is the flexibility of using their Analyst tool to create a mapping specification, which allows you to join multiple sources of information. You can then create rules within that data set. You can apply aggregations and all other types of functions, and then you can feed that into the profiling tool. From the profiling tool, you can then create your scorecards. It can be two-step where you're using that mapping engine to integrate multiple sources. If you don't have a need for that, you can do a lot more sophisticated mappings inside their Developer tool, and then maybe do an analyst type of mapping engine. So, you can do straightforward data quality within the Analyst tool, or you can do more sophisticated data quality within the Developer tool, at least as far as the rules are concerned.
What needs improvement?
Their UI needs improvement. Their scorecards and reporting also need improvement. Their data quality reporting, especially their dashboards and scorecards, is lackluster at best. Its reporting capabilities are limited. If you want to do anything beyond its limited reporting capabilities, then you're going to have to use an external reporting tool such as Power BI or something like that.
It has a few glitches that they haven't fixed. For example, while creating a new scorecard, when you get up to a point, you have to stop and save what you've done. You have to exit and then go back into the tool to finish up your work. From the development aspect, using their scorecard tool has a couple of glitches in it. This might be a tool that they're going to eventually phase out. So, they're just not doing a lot of work on it. I've been living with it for a few years now. I've learned that I got to save my work, and then I got to get back into it to finish up what I was doing.
For how long have I used the solution?
I have been using this solution for at least five years.
What do I think about the stability of the solution?
It is pretty stable.
What do I think about the scalability of the solution?
As far as I know, it scales pretty well. The part of the problem that we have is with the way it saves the results. When it saves the result, it creates a physical copy of some of the data results and stores it. So, when we're processing, for example, 500 million rows of data, depending on the type of rules that we have and how we're doing it, it can quickly use up a lot of space. We've had some issues with some of the space and storage. It scales, but you still have to be careful how you configure it so that you don't use up all your resources. We've added a lot of disk space, and we still occasionally have problems.
Currently, we have maybe half a dozen heavy users, but we're probably going to scale that up to 20 to 25.
How was the initial setup?
It is straightforward.
What other advice do I have?
I would rate it a six out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Lead Software Engineer at a tech vendor with 10,001+ employees
Provides good deduplication capabilities but the UI is outdated and not user-friendly
Pros and Cons
- "The product provides all the typical MDM capabilities like deduplication, machine survivorship, and other things."
- "The downside of this solution is that the UI is terrible and not user-friendly."
What is our primary use case?
We use this solution for MDM in the commercial sector. I'm a lead software engineer for EPAM Systems.
What is most valuable?
The product provides all the typical MDM capabilities like deduplication, machine survivorship, and other things.
What needs improvement?
The downside of this solution is that the UI is terrible and not user-friendly. The solution was developed a long time ago and it no longer provides a lot of value. Our organization is considering decommissioning the solution or reducing usage. The problems seem to be more about the design and not the tool. The UI and general user experience need to be improved. Making changes on Informatica takes a lot of time compared to making changes on other MDM tools.
For how long have I used the solution?
I've been using this solution for seven months.
What do I think about the stability of the solution?
I haven't heard any complaints about stability.
What do I think about the scalability of the solution?
Which solution did I use previously and why did I switch?
Before my time, the company used a legacy MDM solution for dealing with customers. It was created for reporting purposes, to create some compliance reporting, but its functionality didn't allow the addition of more MDM features, so they decided to build a new solution based on Informatica MDM, and from there they basically merged two solutions, the legacy one and this one into Informatica MDM.
How was the initial setup?
The initial setup was carried out prior to my joining the company.
What's my experience with pricing, setup cost, and licensing?
A lot of the solutions on the market are expensive and Informatica is at the top end in terms of licensing costs. They use a bundle model so you choose what you want to include in your bundle and that's what you pay for.
What other advice do I have?
Informatica MDM is a typical MDM tool. I've worked with others and they are all more or less the same. It requires more work than some other tools in terms of development and adding additional features. It has lots of features and is rated highly by Gartner.
I rate this solution seven out of 10.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Principal Applications System Analyst at a university with 10,001+ employees
An enterprise-scale solution with a pretty robust set of tools for scanning a variety of information sources
Pros and Cons
- "The capability of the tool to scan and capture the metadata from a variety of sources is one of the capabilities that I find most useful. The central repository into which it is going to put that captured metadata is the best."
- "From my standpoint, Informatica offers a pretty robust set of scanning tools that can scan a variety of sources of information."
- "The model is somewhat flexible. There are certain aspects of the model that are not as flexible as we would like. It doesn't do certain things to a great level of depth. So, in situations where we want to drill in to do something specific, we have to essentially copy that data into our own structures in order to add that additional layer of flexibility."
- "I can't say the user interface is useless, but people don't use it because they find it cumbersome."
What is our primary use case?
We are using it to understand the assets that we have from their technical metadata perspective, but we're also using it to align our business glossaries with the actual physical data location where the data is stored. Using their Claire or AI engine helps facilitate that. We've been doing that for a while.
The other thing we're trying to do is extend that metadata capability to include extended lineage and provenance attributes. We're trying to incorporate those into the existing EDC environment, and hopefully, when we get Axon, we'll try to figure out how we would expose that to the customer. We will figure out whether we're going to expose that directly or whether we're going to have to augment Axon with an additional UI layer.
How has it helped my organization?
From my standpoint, Informatica offers a pretty robust set of scanning tools that can scan a variety of sources of information. It offers a central repository that you can go to for interrogating and finding data. You can find the data that you're looking for based on enhanced metadata.
The other thing that we're working on is extending the existing Informatica data quality capabilities within the EDC so that we have a more robust understanding of not only what the data is and where it is located but also the quality of that data. We are doing this so that when people are looking for data, they see not only where they can find the data, but they also feel confident that the data is going to meet their needs.
What is most valuable?
The capability of the tool to scan and capture the metadata from a variety of sources is one of the capabilities that I find most useful. The central repository into which it is going to put that captured metadata is the best.
What needs improvement?
The model is somewhat flexible. There are certain aspects of the model that are not as flexible as we would like. It doesn't do certain things to a great level of depth. So, in situations where we want to drill in to do something specific, we have to essentially copy that data into our own structures in order to add that additional layer of flexibility.
Robust process management or workflow management, like Bonita, should be incorporated into the Informatica tool stack because it offers very simplistic workflow capabilities. If we had more dynamic and robust workflow capabilities, we could make use of that a lot more. Currently, we have to do a lot of pre-work outside of the Informatica tools before we can get the data loaded and start using it because they're UIs. I haven't dealt with Axon. So, I don't know exactly how that's going to change things, but with the EDC tool, I can't say the user interface is useless, but people don't use it because they find it cumbersome.
Its UI, without considering Axon, is probably their least desirable part. It has some interesting capabilities, but it is not what I would call cutting edge or super. It is not as intuitive as I would've expected. Its UI is probably prior to Axon. It is a little dated, and even Axon has been out there for a while now, but it is a little dated. That's probably why they went out and bought the company that originally made Axon.
For how long have I used the solution?
I have been using this solution for five or six years.
What do I think about the stability of the solution?
It is very stable.
What do I think about the scalability of the solution?
We're using it for our enterprise. We are not the largest enterprise in the world, but we're a pretty good size. We have 20,000 people working here and petabytes of data flowing through various systems. It is less about the people using it directly as opposed to the systems using it. It is really a matter of the system interfaces that are automating. We're trying to automate the metadata as much as possible so that when people are looking at their data, they can also see the associated metadata. Sometimes, we have to pull the metadata out of EDC and feed it into other systems so that as they're using these other systems, they can see the metadata flows with it.
How are customer service and support?
I haven't dealt much with them directly, but I've had colleagues create tickets all the time. Generally, they're pretty good.
How was the initial setup?
I'm more from the end-user perspective. From a system standpoint, there is a different team that sets things up on the server and establishes various types of configurations. I do work with them, but I'm not actually doing that work.
They have three people that are actively managing the system, and they are system administrators. There are also various people who might be testing things at any one point in time, and then there are various analysts who might be creating data to feed into the system, such as definitions of business terms. The same people may review the results once it gets into the engine. When it starts to process that data and makes the associations between the terms and the actual metadata where it is linking the two up, somebody has to go in and validate that, especially the exceptions or the ones that don't have a high enough matching score. So, there are probably three or four system admin folks, and those are more technical folks, and then you have maybe 20 people who might be putting in data, validating the data, and so on. Those are still primarily an IT function. They have subject matter expertise, but they're still reporting up through the IT group, and then, we'll eventually get to the point where we have a more robust set of business users who are reviewing and vetting that information.
What's my experience with pricing, setup cost, and licensing?
I have no idea what the price actually is. It is probably not going to be the cheapest, but it is a pretty stable and robust platform from the backend standpoint.
What other advice do I have?
I would rate it an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Manager, Data Governance at a healthcare company with 5,001-10,000 employees
They listen to their customers, so if something is missing or not working, they will put it on their roadmap.
Pros and Cons
- "I like EDC's self-service capabilities. You can put the catalog on the intranet inside the organization, so users can search for something. People in the research world have specialized systems, and you might find data from various places that sound similar."
- "It's a great solution, and I was happy with it."
- "Interoperability is one area where EDC has room for improvement. It was challenging when the faculty took over the data world and had specific vendors they wanted to use, and some were not particularly open platforms."
- "Interoperability is one area where EDC has room for improvement."
What is our primary use case?
We were trying to publish a compendium of all our various assets using an Oracle-based data warehouse. We also had vendor-based solutions like Epic for electronic medical records on an SQL Server base. We had many research systems on various platforms because it's a cancer research institution.
We wanted to pull together a comprehensive data catalog to show people all the different assets we had and where they could go to find things. If there were vendor-based definitions of things, we'd pull in the definitions and various attributes. It's a heterogeneous environment data-wise. We get a lot of value from a comprehensive enterprise catalog.
It's available on our intranet through a data governance portal. You could go there for a catalog, quality reports, etc. In a year, there may have been 500 unique visitors. It was my job to publicize it, but I didn't necessarily do a good job. I worked with research groups and clinicians to get their stuff on it, and they would tell other people about it. The nice thing about Informatica is that it was easy to link from our internal web portal to their catalog. I had excellent developers working for me. It didn't require much development, and it took less and less as time went on.
What is most valuable?
I like EDC's self-service capabilities. You can put the catalog on the intranet inside the organization, so users can search for something. People in the research world have specialized systems, and you might find data from various places that sound similar.
The purpose of the Enterprise Data Catalog was to build an internally searchable catalog of stuff. You may not have permission to see this data but at least you could find out where it was and contact the person who owns it.
What needs improvement?
Interoperability is one area where EDC has room for improvement. It was challenging when the faculty took over the data world and had specific vendors they wanted to use, and some were not particularly open platforms.
It was a challenge to promote data visibility while also jumping through hoops to take some of the proprietary things and make them part of the calling, especially when the vendor doesn't necessarily support interoperability. You need to export things from a vendor program and import them again.
For how long have I used the solution?
We used Informatica for a lot of the data governance stuff I worked with when I joined the company, including things like cataloging and profiling data. The organization has really changed a lot in the last year and went with Informatica EDC. They're moving from the on-prem version to the cloud.
What do I think about the stability of the solution?
Informatica is a strong company, and EDC is a solid platform.
What do I think about the scalability of the solution?
The scalability is excellent. Informatica really knows what it's doing. They're smart people and great engineers.
How are customer service and support?
Informatica's customer service and support were decent. They listen to their customers. If something is missing or wasn't working, they will put it on their roadmap. They were listening to customers for roadmap stuff.
We wound up building a staging database to pull stuff out of the EDC, stage it, and then access that. It was open, so we would often have an intermediary layer at Oracle. If we wanted to show, for example, data quality over time, we would have a weekly quality process that would run. We staged that in an Oracle database, and the portal could access that.
Which solution did I use previously and why did I switch?
We had to build Informatica pipelines and do some Azure work to feed data to them. With data warehousing, you typically have static data that is timestamped daily or weekly and sometimes monthly or annually. We were trying to get real-time data, like blood pressure monitoring and stuff like that. That was a lot of work. I didn't do it. The integration team.
When I joined the company, it was an Oracle-based solution. Then Epic took over, which was SQL Server-based. After that, they went to Azure. Now, all the analytics are supposed to be on this platform, and it's not particularly open.
How was the initial setup?
Setting up Informatica EDC is usually pretty straightforward. The challenge is working with vendors like Oracle and Microsoft, which have APIs for integrating things. You can query what they have. They want it to play well with other vendors because they know customers don't only have one brand of product. In some cases, you get vendors in there that are, "No, we're not going to do that because we're so special." It was a challenge. The platform of choice for data initiatives at the cancer research institution is Palantir.
Which other solutions did I evaluate?
We didn't look for an alternative, but Azure has its own catalog.
What other advice do I have?
I rate Informatica Enterprise Data Catalog nine out of 10. It's a great solution, and I was happy with it. It did everything I wanted, and Informatica dramatically increased the integration points over time. When we started, it was like Oracle and SQL Server, but now they're adding NoSQL databases and others.
Informatica has user groups and listens to user input. One of the people that worked for me hosts an annual Informatica user group in Houston. You can try to build your own Oracle-based or SQL-based solution. They listened to the market, and they're working on improving the interoperability. Maybe it works better with Palantir since I left, but they work across all platforms. They're making it Cloud-based. I didn't know anything about them before I got here. I was dropped into a department where Informatica had been for at least five or six years, and it was a good choice.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Download our free Informatica Intelligent Data Management Cloud (IDMC) Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2026
Product Categories
Data Management Platforms (DMP) Cloud Master Data Management (MDM) AI Data Analysis Data Observability Product Information Management (PIM) Test Data Management Services Integration Platform as a Service (iPaaS) Metadata Management Data Masking Data Integration Test Data Management Data Governance Cloud Data Integration API Management Business-to-Business Middleware Business Process Management (BPM) Data QualityPopular Comparisons
Automation Anywhere
IBM webMethods Hybrid Integration
Microsoft Azure API Management
SAP Business Data Cloud
MuleSoft Anypoint Platform
Buyer's Guide
Download our free Informatica Intelligent Data Management Cloud (IDMC) Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Reltio: Question about Master Data Management Capabilities
- Has anyone compared Informaticta to IBM to SAS for an MDM solution?
- Informatica MDM or Hybris PCM? Buy vs. Build?
- Which Informatica product would you choose - PowerCenter or Cloud Data Integration?
- How does Microsoft MDS (vs Informatica MDM) fit with Azure architecture?
- Which is the best choice for cloud integration: AWS Glue or Informatica Intelligent Cloud Services (IICS)?
- Looking for feature comparison: Collibra Governance vs Informatica Axon vs IBM Data Governance vs ASG Enterprise Data Intelligence
- What are the biggest benefits of using Informatica Cloud Data Integration?
- Is the support provided by Informatica Cloud Data Integration helpful?
- What industries does Informatica Cloud Data Integration serve?


















