Why Your Family Tree Gets Locked In — and How GEDCOM Sets It Free
You did the work. Years of evenings: census pages, parish records, photos from a cousin, names chased through three spellings. Then you try to leave the service where your tree lives — or the price jumps, or the service changes its terms — and you learn an uneasy fact. The tree is yours. Getting it out, whole, is another matter.
This is lock-in. It does not arrive with a villain's speech. It builds up in small, normal ways: features that exist only inside one service, data stored in forms only that service reads, an export button that gives you less than you put in. This guide explains how lock-in forms in family history, what a GEDCOM export does and does not rescue, and how to arrange your work so no platform can hold it hostage. The practical routine lives in how to back up your family tree. The escape hatch itself is the file from what is a GEDCOM file.
What Lock-In Means for a Family Tree
Lock-in means the cost of leaving is high enough that you stay, even when you would rather go. For software, that cost is usually measured in lost data and lost work. For a family tree, the stakes are personal. Your tree is not a playlist you can rebuild in a weekend. It is years of research, some of it from sources — and relatives — that may not be there when you try again.
No service needs to lock a door on purpose for lock-in to happen. It is enough that the service is where your tree is easiest to use, richest in features, and hardest to copy out in full. Each year you add inside it, the gap between "the tree in the service" and "the tree I could take with me" grows. That gap is the lock.
The Five Ways a Tree Gets Locked
1. Your Work Lives Only Inside the Service
The basic form. Your tree exists in the service's store and nowhere else. You have no current copy of your own. If the account lapses, the password is lost, or the service ends, the tree goes with it. This is the easiest lock to break and the most common one to find: most people who lose trees lose them this way, not through any dispute. They simply never took a copy out.
2. The Export Gives Back Less Than You Put In
Most big services do offer a GEDCOM export. Press it and compare with care. The people and the core facts usually come out. Around the edges, things go missing. Record images you attached from the service's own collections may not download with the file — the GEDCOM holds a link, not the image, and the link may point inside the service. Hints you accepted, notes in service-only fields, and member connections do not map to GEDCOM structures at all.
None of this breaks the export's promise in a legal sense. It still means the file you get is thinner than the tree you built. Knowing what thins out is the start of defending against it, and the defense is in the sections below.
3. Features That Exist Only in One Place
Trees grow roots into features. One service offers record hints from its own collections. Another offers story builders, map views, DNA ties, and shared work spaces for family members. Each feature you use is a thread that an export does not cut cleanly. DNA is the clearest case: test results and matches are not GEDCOM data at all. They stay with the testing service no matter what you export.
Features are good. Use them. Just do not let a feature become the only home of a fact. If a record image matters to a claim in your tree, save a copy of that image in your own files, with the citation written in your own notes. Features should be a view of your research, not its vault.
4. Your Media Lives Behind Their Links
A GEDCOM file links to photos and scans; it does not contain them. Services know this, and photo handling is where exports get ragged. You may be able to download media, but one item at a time. Or the export's links may point to service addresses that die when the account closes.
The photo of your great-grandparents is not a detail. For many families it is the point. A tree with perfect dates and no photos is a poorer thing than the tree you built. Treat media as a separate asset from the start: keep your own folder of originals, and let every service hold copies.
5. The Price and Terms Move After You Commit
Services change prices, fold features into higher tiers, and revise terms. That is their right. Your protection is not a promise from them; it is the ease of your exit. A researcher with a current GEDCOM copy and a media folder can weigh a price rise calmly and leave if it is wrong. A researcher with neither pays the rise, because the alternative is starting over. Lock-in is not the price rise itself. It is having no choice about it.
What a GEDCOM Export Actually Rescues
Be precise about the tool, because it is a good one. A GEDCOM export from a major service carries the structure of your tree: people, families, and the links between them. It carries names, dates, and places for the main events. It carries sources and citations to the extent the service stored them in standard fields. It carries your notes as text.
| Part of your work | Travels in a GEDCOM export? |
|---|---|
| People and family links | Yes — this is the core of the format |
| Names, dates, places | Yes, for standard events and facts |
| Sources and citations | Mostly — depth varies by service |
| Notes and stories you typed | Yes, as text (service-only fields may not) |
| Photos and record images | No — links only; download the files too |
| DNA results and matches | No — not part of GEDCOM at all |
| Hints and saved records lists | No — these belong to the service |
| Tree layout and chart styles | No — the file holds facts, not looks |
That rescue is real. With a current export, you can rebuild your tree in desktop software like Gramps or RootsMagic, or in another service, and lose none of the core research. The conversion guide shows one use of the rescued data: how to convert a GEDCOM file to Excel.
Before you trust an export, check it. Files can carry faults the service never showed you: broken links, encoding slips, loose dates. Run the export through validation and read the report. The GedConvert tool gives that report free, with the individual and family tables, so you can prove the export holds the people you expect before you change anything. The fault guide is why GEDCOM exports fail validation, and the plan list is on the pricing page.
The Habits That Keep You Free
Freedom here is not a stance. It is a set of small habits, none of which takes more than minutes.
Export on a schedule, not in a panic. Every few months, and after any big research push, export the tree and store the file with its date in the name. A panic export on the day a service announces a change is a bad day's work waiting to happen.
Keep your own master somewhere. Many researchers keep the master tree in desktop software they control, and use services for hints and records, copying facts home. Others keep the master in a service but export often. Either works. What fails is having the master exist in exactly one account with no copy out.
Own your media folder. Every photo and scan in your tree also lives in a folder on your own drive, named so you can find it without the tree. Services get copies. You keep originals.
Write citations like a stranger will read them. A citation that says "per Ancestry hint" tells the future nothing. A citation that names the record set, the place, the year, and the page lets anyone — in any tool, in twenty years — find the source again. Sources written this way survive every move.
Test the exit once. Import your export into a second program and look at the result. Counts match? Names clean? Photos planned for? One rehearsal teaches you more about your lock-in than a year of worry. If the test hurts, you have found the gaps while fixing them is still calm work.
If You Are Locked In Right Now
Start where you stand. Log in and find the export or download path for your tree — on the big services it sits in the tree settings. Export the whole tree, not a branch. Download your media as fully as the service allows, starting with the items you could never replace: family photos first, record images second. Save the export and the media together, with today's date.
Then validate the export and import it into a program you control, even a free one. That single afternoon moves you from "my tree lives in their account" to "my tree lives in my files, and their service holds a copy." Every plan you make after that is made from strength.
One more step seals the change. Tell one person where your copies live: a partner, a child, a fellow researcher. Lock-in thrives on a single point of failure, and a single account holder is one. When a second person knows where the master files sit and how to open them, your tree stops resting on one memory, one password, and one person's health. That is not a morbid thought. It is the same care that made you record the family in the first place, extended one step further so the record itself is not lost.
Frequently Asked Questions
Do services have to let me export my tree? In practice, the major services all offer GEDCOM export. The terms and the exact path vary, and services can change them. That is the point of this guide: while the door is open and easy, walk a copy through it on a schedule.
Is exporting against any service's rules? Exporting your own tree through the service's own export tool is a normal, offered feature. What terms may limit is scraping or bulk downloading of the service's record collections — a different act from taking your tree home.
My export looks smaller than my tree. Did I lose data? The file is text, so it is small next to a tree full of images. Check the people count in a validation report against the count in the service. If the counts match, the core is whole. Then handle media as its own download job.
Can I move my tree from one service to another without loss? The core facts move well. Expect small losses at the edges: service-only fields, some media links, and hints do not travel. A pre-move audit — export, validate, test import — tells you your exact losses before you commit.
What about the family members who work on my tree with me? Shared access is a service feature, and it ends if you leave. Warn your collaborators, export while you all still have access, and agree on where the shared master will live next. More trees are lost to account access tangles than to any file fault.
Is a GEDCOM file enough, or do I need the service's own backup too? Take both when both are offered. The service backup restores best into that service. The GEDCOM restores anywhere. They protect against different futures.
References
- https://gedcom.io/ — The home of the GEDCOM standard, the open format that makes export between services possible.
- https://www.archives.gov/research/genealogy — The U.S. National Archives guide to genealogy research and records.
- https://www.loc.gov/ — The Library of Congress, a major source of census, local history, and family history material.