A GEDCOM file gives you names and dates, not a genogram. Here's the 5-step workflow for converting it, then rebuilding the relational and clinical layer GEDCOM was never built to hold.
A GEDCOM file will hand you three generations of names, dates, and marriages in about ten seconds. It will not hand you a genogram. The conversion itself is the easy part; the real work starts after the import finishes.
GEDCOM (GEnealogical Data COMmunication) is a file format built for genealogists, not clinicians. It was designed in the 1980s to move family tree data between programs like Gramps, Ancestry, and MyHeritage, and it still does that job well. What it was never designed to do is hold the relational and clinical information a genogram depends on.
GEDCOM tracks lineage: who descended from whom, who married whom, and when. It answers "how are these people related" in a purely biological and legal sense. A genogram, by contrast, is a family-systems tool. As we cover in Genogram: The Complete Guide to Mapping Family Systems, a genogram encodes relationship quality, recurring patterns, and system-level dynamics across generations, none of which a genealogy format was built to store.
The structural skeleton of a family tree converts well. Names, sex codes, birth and death dates, and marriage/divorce events are core GEDCOM fields, and any competent converter maps them to genogram nodes and lines without much fuss.
Everything that makes a genogram clinically useful, emotional closeness or conflict, cutoffs, estrangement, substance use, mental health history, caregiving roles, lives outside the GEDCOM schema entirely. If it exists in the file at all, it's buried in a free-text NOTE tag, and a converter has no reliable way to parse a paragraph of prose into a relationship symbol.
| What Converts Cleanly | Transfers to Genogram? | Notes |
|---|---|---|
| Names, sexes, birth/death dates | Yes | Core GEDCOM tags, maps directly to nodes |
| Marriages and divorces | Yes | Standard FAM record events |
| Parent-child links | Yes | Structural, rarely ambiguous |
| Emotional relationship quality | No | Not a GEDCOM concept |
| Medical/mental health history | Rarely | Only if manually typed into NOTE fields |
| Cutoffs, estrangement, conflict | No | Must be added after import |
Before you run a conversion, it helps to know what you're actually looking at. A GEDCOM file is plain text, organized into tagged records that any text editor can open.
Every person in the file is an INDI (individual) record, with a unique ID and child tags for name, sex, birth, and death. Every couple or parent-child unit is a FAM (family) record, linking husband, wife, and children by their INDI IDs. A genogram converter's main job is walking these two record types and rebuilding the family structure they describe.
Dates live under BIRT (birth), DEAT (death), and MARR (marriage) tags, usually in a standardized format. Anything that doesn't fit a structured tag, an illness, a falling-out, a caregiving arrangement, gets dumped into a NOTE tag as unstructured text, if it's recorded at all.
Most genealogists never enter medical or emotional detail because their software doesn't prompt for it. A proper genogram, on the other hand, is built to carry exactly that layer. As we outline in Medical History Tracking: A New Standard in Genetic Counseling, clinical genogram tools track hereditary conditions, causes of death, and health patterns as structured fields, not buried prose. If your GEDCOM has any of this at all, expect to find it scattered across NOTE tags and plan to re-enter it manually.
Here is the sequence that actually works, in order.
Start from the cleanest possible export. Remove duplicate individuals, merge obviously duplicated records, and confirm dates are consistent before exporting from tools like Ancestry, MyHeritage, or Gramps. A messy source file produces a messy import every time; cleanup afterward is far slower than cleanup before.
Run the GEDCOM through your genogram tool's importer. This step should recreate individuals, sexes, birth and death dates, and marriage/parent-child links automatically. Treat this output as a rough draft, not a finished chart.
GEDCOM sex codes and family groupings don't always translate perfectly, especially with blended families, adoptions, or same-sex partnerships that older genealogy software recorded inconsistently. Check every generation line before moving on; a single misplaced FAM record can shift an entire branch out of alignment.
This is where the actual genogram work begins. Emotional closeness, conflict, cutoff, and enmeshment lines all have to be added by hand or through an interview process, because nothing in the GEDCOM file describes them. Our 5-step AI workflow covers a fast, structured way to rebuild this relational layer once the raw import is in place.
Add hereditary conditions, causes of death, mental health history, and substance use notes to the individuals who need them. This is usually the slowest manual step, and it's the one most "converters" skip entirely because it isn't a conversion task at all, it's clinical data entry.
Once the import is done, check it against standard genogram notation before you trust it.
GEDCOM's SEX tag uses M, F, or U (unknown/unspecified). A correct converter maps M to a square, F to a circle, and U to a diamond or other neutral marker, matching the conventions detailed in How to Read a Genogram: Symbols, Lines and Patterns Explained. If every individual in your import came out as a square regardless of the source data, the mapping is broken.
| GEDCOM Sex Code | Standard Genogram Symbol | Common Import Error |
|---|---|---|
| M | Square | Rare, usually correct |
| F | Circle | Rare, usually correct |
| U (unknown) | Diamond or neutral marker | Often defaults incorrectly to square |
| Blank/missing | Should prompt for review | Silently defaults instead of flagging |
MARR and DIV events should produce solid and broken horizontal lines respectively. Cohabitation without a legal marriage record is a common gap: GEDCOM has no clean tag for it, so an importer either drops the relationship or guesses based on shared children.
The most common failure mode is a floating individual with no connecting line to any family. This usually means a FAM record referenced an INDI ID that didn't resolve correctly during import. Scan for disconnected nodes before you build anything on top of the chart.
Even a technically correct import is usually visually unusable on the first pass.
Most importers place individuals in the order they appear in the file, not in a layout optimized for readability. Large families and multiple marriages produce charts with lines crossing in every direction.
A genogram with a dozen overlapping lines is functionally unreadable, no matter how accurate the underlying data is. Line Tunneling: Why Crossing Lines in a Genogram Should Hop explains why simply letting lines cross flat is a design failure, and how a proper hop or tunnel at intersections keeps a dense, freshly imported chart readable instead of a tangle of ink.
When you manually reposition nodes to fix the layout, do it generation by generation, and confirm every connecting line follows its node rather than staying anchored to a now-empty position. This is the step where a rushed cleanup silently detaches relationships that were correct in the underlying data.
Most of the pain in a GEDCOM conversion isn't the import, it's everything after it: fixing the layout, then re-entering relationship and medical data by hand, one node at a time.
GenogramAI is built to take that raw structural skeleton and let you add the relational and clinical layer quickly instead of manually placing every line. Once your family structure is in, adding relationship types, medical notes, and life events takes seconds per node rather than minutes.
The Radial Quick-Add Menu is designed specifically for this: click a node, and add relationship lines, medical annotations, or new family members without leaving the canvas or hunting through nested menus. For a chart with fifty imported individuals, that difference is the gap between an afternoon of cleanup and a fifteen-minute pass.
Once the structure is verified and the layout is legible, the real genogram work is turning a family tree into a family-systems map.
Genograms use a distinct set of line styles, separate from the marriage/divorce lines GEDCOM can supply, to show emotional closeness, conflict, distance, and cutoff between individuals. None of this exists in the source file; it has to be added deliberately, usually based on clinical interview or client report.
Rather than guessing at relationship dynamics, work from a structured set of questions. Genogram Questions to Ask in a Family Interview: 60+ Prompts by Category (2026) is a practical source for the kind of prompts clinicians use to surface exactly the relational detail a GEDCOM file never captured in the first place.
The end goal isn't a prettier family tree, it's a chart you can actually use in a clinical or coaching context: one that shows not just who is related to whom, but how those relationships function. That transformation happens entirely in the steps after import, not during it.
Not every genogram tool treats GEDCOM import the same way, and the differences matter more than most buyers expect.
Before committing to a tool, test it with a real GEDCOM file, ideally one with multiple marriages, an adoption, or an unknown-sex record, and check whether individuals, sexes, and family links come through intact. A vendor's marketing claim of "GEDCOM support" can mean anything from full fidelity to a barebones name-and-date import.
Genealogy platforms like Ancestry, MyHeritage, and Gramps are optimized for lineage research, not clinical use. They generally lack relationship-dynamic lines, medical annotation fields, and the kind of layout tools that keep a dense chart readable in a session.
| Feature | Genealogy Software | Clinical Genogram Software |
|---|---|---|
| GEDCOM import | Native, full fidelity | Varies by vendor |
| Relationship dynamic lines | Not supported | Core feature |
| Medical/clinical annotations | Rare or manual | Built-in fields |
| Layout tools for dense charts | Basic | Purpose-built |
| Designed for session use | No | Yes |
Best Genogram Software in 2025: The Definitive Comparison and Genogram Software for Therapists: The Speed-First Buyer's Guide (2026) both compare tools on exactly these dimensions, import fidelity, how fast you can add the clinical layer, and whether the software was actually built for session-paced work rather than after-hours documentation.
Can I convert a GEDCOM file directly into a genogram? Yes, for the structural layer. A good importer will recreate individuals, sexes, dates, and marriage/parent-child links from a GEDCOM file. It cannot generate the relationship-dynamic or clinical layer, since that data doesn't exist in the format.
What information from my GEDCOM file transfers into a genogram, and what doesn't? Names, sexes, birth and death dates, marriages, and parent-child relationships transfer reliably. Emotional relationship quality, cutoffs, mental health history, and most medical detail do not, since GEDCOM has no structured fields for them.
Why does my imported genogram look tangled or cluttered? Most importers place individuals in file order rather than a readability-optimized layout, which produces heavy line crossing in larger families. Rearranging by generation and using proper line-crossing techniques, as described in Line Tunneling, fixes most of this.
Do I need genealogy software or clinical genogram software to open a GEDCOM? Either can technically open a GEDCOM file, but genealogy software won't give you relationship-dynamic lines or clinical annotation fields. If you're building a genogram for clinical or coaching use, a purpose-built clinical genogram tool is the better starting point.
How do I add medical and emotional relationship data after importing a GEDCOM? Manually, either through direct editing or a structured interview process. Using a set of standardized prompts, rather than free recall, tends to surface more complete and consistent relational data.
Will the converter map GEDCOM sex codes to the correct genogram symbols? A correct importer maps M to a square, F to a circle, and unknown/unspecified to a diamond or similar neutral marker. Check a sample of records after import, since some converters default ambiguous codes to a single symbol instead of flagging them for review.
Converting a GEDCOM file into a genogram is a five-minute technical task. Turning that converted file into a genogram anyone can actually use clinically is the work that comes after, verifying the structure, cleaning the layout, and adding the relational and medical layer the format was never built to hold. Treat the import as step one of a longer process, not the finish line, and the chart you end up with will actually be worth using.
GenogramAI turns a conversation into a clinical-grade family map, with symbols, relationship lines, and medical history built in.
Start mapping freeGenogramAI is designed for educational and personal use. It is not a medical device and should not be used for clinical diagnosis or treatment decisions.