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

No Magic MagicDraw vs erwin Data Modeler comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Nov 23, 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

erwin Data Modeler
Ranking in Business Process Design
7th
Average Rating
8.4
Reviews Sentiment
5.9
Number of Reviews
48
Ranking in other categories
Enterprise Architecture Management (2nd), Data Governance (9th)
No Magic MagicDraw
Ranking in Business Process Design
14th
Average Rating
8.4
Reviews Sentiment
6.0
Number of Reviews
19
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2026, in the Business Process Design category, the mindshare of erwin Data Modeler is 2.6%, up from 2.3% compared to the previous year. The mindshare of No Magic MagicDraw is 2.6%, down from 3.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Business Process Design Market Share Distribution
ProductMarket Share (%)
erwin Data Modeler2.6%
No Magic MagicDraw2.6%
Other94.8%
Business Process Design
 

Featured Reviews

Sushree Panigrahi - PeerSpot reviewer
Snowflake Data Engineer| Senior PLSQL Developer |Data Modeler|Assitant Vice Pre at Jp Morgan Chase & Co.
Data modeling has transformed regulatory reporting and collaboration across cloud environments
In erwin Data Modeler, areas that have room for improvement include performance improvements. I see that large models sometimes cause it to be slow when opening. Impact analysis can lag as well. Version control is another aspect. If we have developed a current version, it is not integrated with Git where we can easily compare different versions. UI modernization is also something we cannot utilize as it is primarily for development. Additionally, cloud-specific optimizations are needed when it comes to Snowflake or Databricks. When it comes to AI aspects, auto-suggestions for normalization or identifying primary, foreign, or surrogate keys are areas that can be improved.
reviewer2080611 - PeerSpot reviewer
System Engineer at a consultancy with 51-200 employees
Ease of use and real-time collaboration empower effective teamwork and streamlined development
For CAMEO, it's not only the ease of use, it's versatility, its communicability, but Rhapsody is the worst tool I've ever used. It is very difficult, not user-friendly, and very expensive. It works only with its IBM counterparts. SPARX Enterprise Architecture is very easy to use, but it's limited. It gives you an idea of how your model is developing, so this feature helps maintain integrity or correctness of system models. It's really a good feature to have. You've got to have the simulation toolkit installed to be able to do that, and that works really well. The MagicDraw or CAMEO system is good on its own, but it should be integrated and should come out of the box with the simulation toolkit because there are some things you can't do without it, making it very difficult to have to look for another license to be able to do that. I would prefer that it come with the simulation toolkit.

Quotes from Members

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

Pros

"What has been useful, I have been able to reverse engineer our existing data models to document explicitly referential integrity relationships, primary/foreign keys in the model, and create ERDs that are subject area-based which our clients can use when working with our databases. The reality is that our databases are not explicitly documented in the DDL with primary/foreign key relationships. You can't look at the DDL and explicitly understand the primary/foreign key relationships that exist between our tables, so the referential integrity is not easily understood. erwin has allowed me to explicitly document that and create ERDs. This has made it easier for our clients to consume our databases for their own purposes."
"We use the macros with naming standards patterns, domains, datatypes, and some common attributes. As far as other automations, a feature of the Bulk Editor is mass updates. When it sees something is nonstandard or inaccurate, it will export the better data out. Then, I can easily see which entities and attributes are not inline or standard. I can easily make changes to what was uploaded to the Bulk Editor. When taking on a new project, it can save you about a half a day on a big project across an entire team."
"The solution's ability to compare and synchronize data sources with data models is fantastic. We use it for that on a regular basis to make sure that changes haven't been made to the database outside of the modeling process. I can take existing databases and reverse engineer them and understand their structure within 15 minutes. If I didn't have Data Modeler it would take hours. It increases our productivity and helps in understanding our legacy application."
"The most valuable features are the ability to reverse engineer and do model comparison. With the reverse engineering, I can understand the databases from third-party products. With the model comparison, I can track the differences between two versions of the same database."
"When you're getting down to the database level, where you're building a design and you're creating DDL out of it, or you're going in the other direction where you're reaching into system catalogs and bringing things back, that starts to really require specialization. Visio isn't going to reverse-engineer that for you. Those features in erwin are valuable."
"One of the best aspects of the tool is its reverse engineering capability."
"The most valuable features are being able to visualize the data in the diagrams and transform those diagrams into physical database deployments. These features help, specifically, to integrate the data. When the source data is accumulated and modeled, the target model is in erwin and it helps resolve the data integration patterns that are required to map the data to accommodate a model."
"We find that its ability to generate database code from a model for a wide array of data sources cuts development time. The ability to create one model in your design phase and then have it generate DDL code for Oracle or Teradata, or whichever environment you need is really nice. It's not only nice but it also saves man-hours of time. You would have to take your design and just type in manually. It has to take days off out of the work."
"I would rate MagicDraw a nine out of ten because of the price. Enterprise Architect has a lot of bugs and MagicDraw is a lot more accurate and flexible. It's a level better."
"I like the traceability feature. Whoever is working with the product would be sure of the things that could be affected if they decided to affect one of the other companies. For example, let's say that an engineer starts a new project optimization problem by adjusting the thickness of metal sheets. However, the engineers only see a reduced number of affections, but when we use the requirement traceability, they can see the whole picture. That's the main aspect that we were promoting with this tool."
"The initial setup was not straightforward."
"The technical support is very good."
"It is very user-friendly, and the customer service is really good."
"The most valuable feature of No Magic MagicDraw is the simulation capabilities and interface."
"When you look at it, No Magic is an all-encompassing tool. You can use it for business architecture design. You can use it for deploying an ERP system across your enterprise. However, it was initially designed and developed for model-based systems engineering. That's the systems engineering required to either produce an IP system or product. It takes away the mounds of paper and puts it into a model. It enables you to generate significant savings by modeling that new product or that system before you ever start developing a prototype."
"The most valuable feature is the ability to quickly build multiple layers within the organizational and business process environments, as well as in the SysML product environments, and converting to files that can be accessed by clients who do not have a system and a teamwork server access."
 

Cons

"The Bulk Editor needs improvement. If you had something that was a local model to your local machine, you could connect to the API, then it would write directly into the repository. However, when you have something that is on the centralized server, that functionality did not work. Then, you had to export out to a CSV and upload up to the repository. It would have been nice to be able to do the direct API without having that whole download and upload thing. Maybe I didn't figure it out, but I'm pretty sure that didn't work when it was a model that sat on a centralized repository."
"Complete Compare is set up only to compare properties that are of interest to us, but some of the differences cannot be brought over from one version of the model to another. This is despite the fact that we are clicking to bring objects from one place to another. Therefore, it's hard to tell at times if Complete Compare is working as intended without having to manually go into the details and check everything. If it could be redesigned to a degree where it is easier to use when we bring things over from one site to another and be sure that it's been done correctly, that would be nice to have. We would probably use the tool more often if the Complete Compare were easier to use."
"I still use Visio for conceptual modeling, and that's mainly because it is easier to change things, and you can relax some of the rules. DM's eventual target is a database, which means you actually have to dot all the Is and cross all the Ts, but in a conceptual model, you don't often know what you're working with. So, that's probably a constraint with erwin. They have made it a lot easier, and they've done a lot, but there is probably still room for improvement in terms of the ease of presentation back to the business. I'm comparing it with something like Visio where you can change colors on a box, change the text color and that sort of stuff, and change the lines. Such things are a whole lot easier in Visio, but once you get a theme organized in erwin, you can apply that theme to all of the objects. So, it becomes easier, but you do have to set up that theme."
"erwin is not as robust as a data warehousing project I've been on in the past."
"The navigation is a little bit of a challenge. It's painful. For example, if you've got a view open and you want to try to move from side to side, the standard today is being able to drag and drop left and right. You can't really do that in the model. Moving around the model is painful because it doesn't follow the Windows model today."
"The only real complaint I have is the time it takes to do a database comparison on a large model. If they could speed that up, that would be the only thing I can think of that needs improvement."
"erwin generally fails to successfully reverse engineer our Oracle Databases into erwin data models. The way that they are engineered on our side, the syntax is correct from an Oracle perspective, but it seems to be very difficult for erwin to interpret. What I end up doing is using Oracle Data Modeler to reverse engineer into the Oracle data model, then forward engineer the DDL into an Oracle syntax, and importing that DDL into erwin in order to successfully bring in most of the information from our physical data models. That is a bit of a challenge."
"While I do not have knowledge about pricing for erwin Data Modeler, I think it could improve by having a feature that allows the publishing of models, similar to how Power BI allows for dashboard publishing for different users within an organization, not just data modelers."
"They don't really support code engineering, and that's why we have to move to Enterprise Architect. MagicDraw is stuck at C++03 standards, whereas most C++ programs today want to use the latest definition of the C++ standards. We were at C++11, and we wanted to do code engineering with C++11 or 17, but they didn't support it. That pushed us into a different tool, which is Sparx Enterprise Architect."
"For the next releases, I would like to have them import requirements from other sources. They could make it very easy to do that because there are a lot requirements management tools like DOORS, D-O-O-R-S, Dynamic Object Oriented Management. A lot of folks use DOORS to create a requirement. For those requirements you allocate them to a component in the architecture and a verification method for that requirement. It would be good if we could import those into MagicDraw as components so you don't have to manually do these things."
"The cost of upgrading the product should be lower."
"The technical support is not very good."
"There could be a trial version for students."
"There are some technical features that you have to study and do research on to be able to understand."
"I would like to see the ability to deploy live business process models and capture real-time data (without the need for another product tool) so you don't have to be dependent on other products for this functionality."
"The price of the solution could be reduced."
 

Pricing and Cost Advice

"Pricing is very high compared to any other product."
"There are two license options and the pricing is reasonable."
"erwin is expensive compared to other solutions. We are paying almost $6,000 per seat a month."
"There are no costs in addition to the standard licensing fees."
"I don't specifically know what we're paying now. About three years ago, in another organization, I have this memory of 6,000 AUD a seat or something like that, but I am not sure. In the mid-2000s, it was something like 1,200 AUD a seat. I get the impression that there was a price jump when it was spun off from CA as a separate company, which is understandable, but it could sometimes be a barrier in some organizations picking it up. I haven't talked to erwin people yet, but I'm going to suggest to them that they could perhaps think of having an entry-level product that is priced a bit lower, and then, you can buy the extra suite."
"The solution is expensive."
"erwin has this option where you pay a one-time fee and you have the license for six years, which makes sense because I don't upgrade my database engine every other year. I have an application that depends on it. This is something weird about PowerDesigner. There are no additional costs beyond the standard licensing fee."
"The price of erwin Data Modeler is very expensive, in particular for this part of the world."
"The price of No Magic MagicDraw could improve. The price of the solution is too expensive for smaller-sized companies. There should be a better pricing model."
"I would say licensing would be anywhere from $3,500 to $6,500 per person or per seat (it's a per seat style license)."
"I rate the pricing a ten out of ten. It is an expensive product compared to software for model-based system engineering."
"In addition to the initial cost, you have to pay annually for support in order to get the upgrades."
"The licensing is on a yearly basis, and it's expensive."
report
Use our free recommendation engine to learn which Business Process Design solutions are best for your needs.
882,207 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Manufacturing Company
8%
Government
8%
Performing Arts
5%
Manufacturing Company
24%
Government
11%
Aerospace/Defense Firm
10%
Financial Services Firm
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business16
Midsize Enterprise3
Large Enterprise35
By reviewers
Company SizeCount
Small Business14
Midsize Enterprise1
Large Enterprise7
 

Questions from the Community

What is your experience regarding pricing and costs for erwin Data Modeler by Quest?
Regarding pricing, it depends on the company. For a cloud or SaaS standard edition, it typically runs around two hundred to two hundred ninety-nine US dollars per month. For a workgroup edition, it...
What needs improvement with erwin Data Modeler by Quest?
In erwin Data Modeler, areas that have room for improvement include performance improvements. I see that large models sometimes cause it to be slow when opening. Impact analysis can lag as well. Ve...
What is your primary use case for erwin Data Modeler by Quest?
My use case is mostly architectural design for our end-to-end deployment.
What is your experience regarding pricing and costs for No Magic MagicDraw?
Maybe the price is a little bit high for a small company to acquire this tool. However, they offer trial versions and trial licenses for members of INCOSE.
What needs improvement with No Magic MagicDraw?
For CAMEO, it's not only the ease of use, it's versatility, its communicability, but Rhapsody is the worst tool I've ever used. It is very difficult, not user-friendly, and very expensive. It works...
What is your primary use case for No Magic MagicDraw?
I deal with DOD lifecycle acquisition sorts of things as some of the main use cases currently, and I expect to continue using it for more than 25 years.
 

Also Known As

erwin DM
MagicDraw
 

Overview

 

Sample Customers

 Premera, America Honda Motors, Aetna, Kaiser Permanente, Dental Dental Cali, Cigna, Staples
Northrop Grumman, Labcorp, Deposco, ClearView Training, IT Services Promotion Agency, Intelligent Chaos, Metalithic Systems Inc., Sodifrance
Find out what your peers are saying about No Magic MagicDraw vs. erwin Data Modeler and other solutions. Updated: February 2026.
882,207 professionals have used our research since 2012.