Free erwin converter
Convert an erwin model for Snowflake, Databricks or BigQuery
Upload an erwin Data Modeler XML export. In seconds you get a health report an architect would write and your model converted for a modern platform, with keys, relationships, subject areas and definitions intact.
erwin model Retail Orders · erwin XML r9 read 8 tables · 40 columns · 6 relationships health 52 / 100 · grade D high personal data with no classification × 5 high columns that look like FKs, no relation × 2 medium customer_id: bigint vs varchar(20) × 1 medium ORDER is a reserved word → orders convert snowflake NUMBER(12,2) → NUMBER(12,2) VARCHAR2(30) → VARCHAR(30) MONEY → NUMBER(19,4) supplier ↔ product → supplier_product (bridge)
Analyse an erwin model
In erwin Data Modeler: File → Save As → XML. Upload the XML here. It is read in memory and never stored.
Years of design work sit in erwin models: entities, keys, relationships, definitions. Moving that work to a cloud warehouse usually means re-keying it by hand or forward-engineering Oracle-flavoured DDL and fixing it table by table.
This converter reads erwin's XML export directly. It keeps the model's structure and documentation, converts every physical type for the platform you choose, resolves logical many-to-many relationships, renames reserved words, and reviews the model the way a principal data architect would, so you know what to fix before it reaches production.
What the converter does
Reads erwin XML, both dialects
erwin r7 and later, and ERwin 4 XML. Entities, attributes, physical types, null options, PK and AK key groups, relationships, subject areas, domains and definitions.
Converts types, keeps sizes
Oracle, SQL Server, DB2 and Teradata types become their Snowflake, Databricks, BigQuery, Postgres, Redshift, Synapse or Fabric equivalents, with lengths and precision kept.
Architect review, free
Missing keys, undeclared joins, type drift between tables, unclassified personal data, undocumented tables and reserved words, ranked by severity with a score.
Fixes what would break
Logical many-to-many relationships become bridge tables, reserved words are renamed, and foreign keys are ordered so the DDL runs first time.
Private by design
The file is parsed in memory with hardened XML handling and discarded. No AI model sees it, and nothing is stored unless you import it.
Then modernise it
Import into OffDataAI for full DDL, dbt, docs, governance and an ontology, or have AI remodel it as a star schema or Data Vault.
Frequently asked questions
How do I export a model from erwin Data Modeler?
Which erwin versions are supported?
Is my model stored or used to train AI?
What does the health report check?
How are data types converted?
What happens to many-to-many relationships and reserved words?
What do I get if I import the model into OffDataAI?
Explore OffDataAI
- Looking for an erwin alternative?How OffDataAI compares with erwin Data Modeler.
- Ontology builderTurn a data model into a published business ontology.
- MCP server for AI agentsGive Claude and other agents your tables, joins and metrics.
- Model BuilderDrag-and-drop data modeling on a full-screen canvas.
- Database ModelerReverse-engineer a live database into an editable model.
- AI data modeling toolDesign a data model from a plain-English description.
Your data warehouse is one conversation away.
Describe your domain, or open one of 170+ production-grade templates. ERDs, DDL, and a complete dbt project — generated in under a minute.
erwin is a trademark of Quest Software Inc. OffDataAI is not affiliated with or endorsed by Quest Software.
