Have you received a new Mitotree haplogroup? Or maybe you didn’t? Are you wondering why you might not have received a new haplogroup? How do the new haplogroups work anyway? And how do you work with them?
Great questions!
Approximately 75% of full sequence testers received a new haplogroup with the Mitotree Beta release, which means that about 25% did not. Keep in mind that new sequences are being added to the database, so the tree will be sprouting new haplogroups with each subsequent release.
Check For Your New Haplogroup
Sign in to your account at FamilyTreeDNA and look at the Badges in the bottom right corner of your page.
Your Beta haplogroup is your new Mitotree haplogroup, and your Legacy haplogroup is your old one – prior to Mitotree. They may be the same. My haplogroup, shown above, did not change.
This is a good place to note that the tree is not “done,” yet, nor will it ever be. New samples are added daily as more people test and as academic samples from published papers are added to the database as well. Additionally, FamilyTreeDNA is tweaking the algorithm, so the tree branching structure may change from time to time.
When your haplogroup changes, you’ll receive a notification email.
Some people’s haplogroup will remain the same. There can be several reasons why you might not have received a new haplogroup.
Before we discuss that, I’d like to stress that your haplogroup remaining the same isn’t exactly a bad thing because there is SO MUCH new content for everyone. It’s like receiving a whole new book about your mother’s direct matrilineal line.
mtDNA Discover Offers 13 New Reports for Everyone
MtDNA Discover was released with the new Mitotree, and it includes a dozen new reports for EVERY haplogroup.
Discover is available publicly, and also through your FamilyTreeDNA dashboard which provides a customized experience for mtFull testers with additional information that is not available in the free version.
Think of these Discover reports as chapters in your personal book – all about you and your matrilineal ancestors.
The Discover reports are provided in addition to the tools in the mtDNA Results and Tools section of your dashboard on FamilyTreeDNA.
There’s something for everyone, even if you don’t have a new haplogroup. There’s certainly new information that will help with your genealogy and with understanding the history and ancestral journey of your mother’s direct line maternal ancestors.
Three Reasons Why You Might Not Receive a New Haplogroup
Ok, so why might you not have received a new haplogroup?
The first reason that you might not have received a new haplogroup assignment is the simplest. The new tree is only updated periodically.
After your results are returned, and before the next Mitotree version is available, your Mitotree haplogroup Badge will show as “Analyzing.”
If one of your matches is waiting for a new haplogroup, their Mitotree Haplogroup will show as “Pending Analysis.”
There is no published tree-update schedule, but you’ll receive your new haplogroup soon.
However, you can probably determine your new haplogroup quite easily. If you have any exact matches on your mtDNA Match page, their haplogroup will be your haplogroup as well, so check your full sequence mtDNA Matches on your dashboard for a hint.
For, example, here’s one of my exact matches with their haplogroup.
The second reason you might not have a new haplogroup assignment is that you may not have taken the full sequence mitochondrial DNA test – mtFull.
Only testers with full sequence test results can receive an updated haplogroup, because the full mitochondria needs to be tested. The older HVR1/HVR2 Plus tests only tested a fraction of the full sequence – around 1000 locations of the 16,569 locations tested in the full sequence test.
If you have only taken the HVR1 or HVR1/HVR2 level test, you will only have one badge, and it will say “Predicted.”
The haplogroup for the Plus test is predicted at a high level based on those 1000 locations, while the full sequence test tests the entire mitochondria and uses all locations to confirm your most granular and detailed haplogroup possible.
On your dashboard, if both the Plus and Full icons are pink, you have taken the mtFull test. If the “Full” is grey, you have not. You can click on that grey button to upgrade.
You can also navigating to on Add Ons and Upgrades in the top bar to upgrade to the full sequence test.
The third reason why someone might not have received a new haplogroup assignment is if they didn’t match with anyone else who has the same mutations, or variants, for a particular haplogroup.
In other words, if my mitochondrial DNA has had a mutation or two since my assigned haplogroup was formed and no one else has tested that has those exact same mutations, there’s no one else to form a new haplogroup with, but there might be in the future as additional people test and the tree continues to grow.
Think of those additional mutations, called Private Variants, as foundation blocks, or haplogroup seeds since they are still private to you, and not yet used for a haplogroup.
It’s easy to see if you have any Private Variants by clicking on Discover on your mitochondrial dashboard.
Scientific Details – Private Variants, Building Blocks, Haplogroup Seeds
If you have taken the full sequence test, click through to mtDNA Discover from your dashboard. If you aren’t signed in and click through from your dashboard, you won’t be able to see your variants or other information customized for you.
Navigate to Scientific Details, then click on the Variants tab.
Be sure that “Show private variants” is toggled to “on,” which is blue with a checkmark.
At the very top, you’ll see two things:
- Your haplogroup, which is indicated by the solid pink square.
- An F number followed by your private variants, if any, and if so, which ones.
I have no private variants or haplogroup seeds available to form a new haplogroup, so I have no ability to receive a more refined haplogroup.
Haplotype Clusters
However, I’m NOT out of luck, because I have something else – a Haplotype Cluster, indicated by having an F#. My Haplotype Cluster is F1752176 and is indicated by the pink outlined box.
I wrote about haplotype clusters in the article, Mitochondrial DNA: What is a Haplotype Cluster and How Do I Find and Use Mine?.
In a nutshell, haplogroups are only formed around reliable, relatively stable mutations, meaning those that are reliable and don’t tend to randomly mutate back and forth.
You may match exactly with a group of other people who share the same haplogroup, PLUS the same unstable mutations that don’t qualify to become haplogroup-defining.
Those groups of two or more people who match exactly on all mutations are members of the same Haplotype Cluster – and Haplotype Clusters can be INCREDIBLY genealogically useful. In fact, let me go out on a limb here and say that I think they are even more genealogical useful than haplogroups, although both have their strengths. Let’s look at a good example.
Using Haplogroups and Haplotype Clusters Together
My family member, Jim, had a surprise waiting for him in his mitochondrial DNA. When he received his new haplogroup, I took a look to see what new information might be forthcoming.
His legacy haplogroup was V, and his new Mitotree haplogroup is V216a2 which is significantly more refined.
Before Mitotree and Haplotype Clusters, there wasn’t much to differentiate him from his other matches.
Let’s take a look at JUST his genetic information before adding genealogy.
If I click on the Time Tree for haplogroup V216a2, I see two testers with no cluster, meaning no one matches them exactly, and Jim’s cluster number F9712482.
Keep in mind that Jim might not match everyone in his haplogroup – only people at or beneath the matching threshold.
Jim’s new haplogroup, V216a2 was formed about 1056 CE, or about 975 years ago. Note that as the tree changes and becomes more refined, haplogroup formation dates change too. A haplogroup’s birth date is an approximate year when the mutations occurred that define that haplogroup, based on surrounding mutations and mutation rates.
Many people look at a haplogroup, especially one with a birth date of, say, 1056 CE, which is long before the formation of surnames, shrug their shoulders, and give up.
Don’t. Do. That.
So, let me say this as loudly as possible.
A haplogroup’s most recent common ancestor is NOT the EKA (earliest known ancestor) with any individual match. It’s the approximate date when ALL of the people with this haplogroup share a common ancestor.
When looking at haplogroups, don’t let locations thrown you. Keep in mind that country boundaries are fluid. What was at one time Hungary could be Germany or Romania or something else just a few years earlier or later. So don’t discount that information either. Think regions and take into consideration that people move around – and some people enter incorrect genealogy/location information.
Your common ancestor with the people, individually, who share your haplogroup, is sometime between the haplogroup formation date and today. Everything else is a clue.
Think about it this way. You share a haplogroup with your mother, and while you are both descended from the woman who lived when your haplogroup was formed – your most recent ancestor with that haplogroup is your mother – not the woman 975 years ago. Your most recent common ancestor (MRCA) with your mother and her sister is your grandmother – a lot closer in time than 1056 CE. 1056 CE the most recent common ancestor (MRCA) date for everyone in the haplogroup, not between you and any one person in particular. The MRCA date for you plus another person is sometime between now and 1056 CE.
So, let’s take a look at Jim’s results.
Finding Jim’s Gold Nugget
Jim has 27 coding region matches, of which six share both his new haplogroup, V216a2, AND Haplotype Cluster F9712482. His other matches are split between three related haplogroups, and multiple haplotype clusters.
Most of his family, meaning three of his grandparents, were from eastern Europe, meaning Germany, Hungary or the Austro-Hungarian empire as it was recorded in American records. Many genealogical records no longer exist in that region, or if they do, you have to know exactly where to look.
We were brick-walled with Jim’s matrilineal great-grandmother, Sophia Smith, who was born about 1877 and seemed to appear out of thin air.
Thanks to the new haplogroups, combined with Haplogroup Clusters, I knew to focus on his matches in this order:
- Same haplogroup plus same Haplotype Cluster
- Same haplogroup plus different Haplotype Cluster, because clusters are built around identical but less reliable mutations
- Related haplogroup – this is unlikely to yield direct genealogical results, but can be very useful in terms of origins
Of Jim’s exact matches with the same Haplotype Cluster, three showed an earliest known ancestor (EKA) and three did not. Three provided a tree, and three did not. Of the trees, one was private and the other two provided no useful insight.
Of the people who provided EKA information, one EKA matches their tree information, one conflicts with their tree. After viewing their tree, it appears that they did not understand that the mitochondrial EKA is the most distant ancestor in your mother’s direct maternal line. They listed someone in their grandmother’s paternal line.
I find this easiest to deal with if I organize the research in a chart for each match.
| Match # | Earliest Known Ancestor | EKA Location | Tree | Comment |
| #1 | No | No | No | |
| #2 | No | No | No | |
| #3 | No | No | Yes – Private | |
| #4 | Yes – only one name “Egan” with brith and death dates | Ireland | Yes – Egan is surname of their grandmother | EKA person listed tracks up wrong line in tree |
| #5 | Yes | Hungary | No | Elizabeth Schmidt Hornung b1888 d 1930 |
| #6 | Yes | No | Yes – matches EKA | Ancestor born NC in 1811, no common names or location |
Match #5 provided an EKA, but no tree, showed a country of origin as Hungary, and the identity of her EKA as “Elizabeth Schmidt Hornung b.1888 and d.1930.”
Hmmm…three things of interest here:
- The location of Hungary, even though the oral history in Jim’s family said his great-grandmother was a Smith from the US, maybe New York. Jim’s family, including Sophia’s husband, was Eastern European. Remember, I couldn’t find any early records for Sophia Smith.
- Smith is the anglicized version of Schmidt.
- Hornung may be a married name.
I’m a genealogist, and Jim’s match had provided enough information that I was able to identify her ancestor, Elizabeth Schmidt, and find additional information.
Sure enough, Elizabeth Schmidt immigrated as an adult by herself, married Karl Hornung in Richland County, Ohio, the same location where Jim’s family was living. That information led me to another record, identifying a brother whose marriage license application provided their parents. Elizabeth’s parents were Ignatius Schmidt and Catherine Schlowe, and her sister was Sophia Schmidt, Jim’s great-grandmother. Deeper digging suggests that Ignatius and Catherine were from Timisoara in what is now Romania. I have been unable to confirm with birth, death or marriage records, but that part of Romania was part of the Austro-Hungarian Empire during that timeframe.
Immigration of siblings, alone, at different times after the 1910 census, without their parents, made this particularly difficult, as did cultural and language barriers – but mitochondrial DNA, and Jim’s Haplotype Cluster in particular, provided the key I needed.
Jim’s common ancestor with his Schmidt match is the birth date of Catherine Schlowe, which was probably about 1850 – NOT 1056 CE, which is the haplogroup formation date.
Don’t get discouraged by misinterpreting haplogroup origin information or missing genealogy information. All you need is that one good match. That gold nugget. Don’t forget that you can email your matches and ask for more information.
The Match Time Tree makes all of this easier.
Match Time Tree
The Match Time Tree shows match, haplogroup, location and Haplotype Cluster information all in one place.
It’s easy to use the Match Time Tree to view how all of your matches are grouped, along with their EKA, displayed together in one place.
Here are all of Jim’s matches. They were all originally haplogroup V, but now his matches have been divided into V216, V216a, V216a1, and V216a2 (Jim’s haplogroup).
I’ve obfuscated the names of his matches, but the EKA, when provided, is there. Each person is grouped into their haplotype cluster of exact matches, and the user-provided country of origin for their ancestor is shown by their profile photo.
Jim’s match with the descendant of Elizabeth Schmidt is indicated in the red boxes, and Jim has updated his own EKA and her country of origin.
Who is waiting for you in your match list?
Will extending and building out trees help?
Have you emailed your matches to see what additional information they can provide?
Female ancestors are sometimes the MOST difficult to find, often due to name changes – so be sure to mine every possible avenue and don’t become discouraged if you don’t immediately see something “familiar.”
Every generation in a female lineage will probably carry a different surname and the match you need may not have researched as far back as your ancestor, or vice versa.
Don’t forget that autosomal matching can play an important role in confirming relationships.
But wait – there’s STILL more about Jim’s ancestors…
There’s Even More to Discover
There’s more to discover about Jim’s ancestors.
Jim’s Discover Ancient Connections tells me that 5200 years ago, Jim shared a common mitochondrial DNA ancestor with two Hungarian and a Slovakian Yamnaya cultural burial whose remains date to about 2800 BCE, or about 4800 years ago.
To be clear, the common haplogroup between Jim and all three burials dates to 5200 years ago, when their common haplogroup was formed, but the remains themselves are from about 4800 years ago – so only about 400 years difference between the haplogroup birth date and when those people lived, died and were buried.
How close are the remains to the location of Jim’s ancestor in Timisoara?
Using Google Maps, I placed the three Yamnaya burial locations (blue pins), plus Timisoara.
The two most distant points, Timisoara to Lesne, Slovakia, walking, is 393 km or 245 miles. The closest burial to Timisoara, located in Sárrétudvari, Hungary, is 157 km or 119 miles.
So Jim’s ancestors remained in the same general area for someplace between 4,800 and 5,200 years. And, his great-grandmother was born not far from those burials. That alone is an INCREDIBLE find!
So, what happened to the people of the Yamnaya culture? I think we might have gained some insight into that question.
So, there’s even more to discover using Discover.
You don’t know what you don’t know about your matrilineal ancestors, so test your mitochondrial DNA at FamilyTreeDNA and break through those brick walls. I’ve already solved multiple long-standing mysteries and added generations to my own tree.
Plus, I really, REALLY want to know where every single ancestor “came from,” what culture they were a part of, and when. History is part of genealogy – and a part of our ancestral journey that we can’t reach any other way.
Fortunately, your matches, Scientific Details, Time Tree, Match Time Tree, and Ancient Connections help you visualize all of these various situations and aspects of your ancestor’s history, and evaluate your results.
Both haplogroups and Haplotype Clusters provide very fine degrees of granularity that were not previously available. MtDNA Discover adds a dozen new reports, and Ancient Connections allow you to time travel.
Let me know what you discover!
_____________________________________________________________
Share the Love!
You’re always welcome to forward articles or links to friends and share on social media.
If you haven’t already subscribed (it’s free,) you can receive an e-mail whenever I publish by clicking the “follow” button on the main blog page, here.
You Can Help Keep This Blog Free
I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.
Thank you so much.
DNA Purchases and Free Uploads
- FamilyTreeDNA – Y, mitochondrial and autosomal DNA testing
- MyHeritage DNA – Autosomal DNA test
- MyHeritage FREE DNA file upload – Upload your DNA file from other vendors free
- AncestryDNA – Autosomal DNA test
- AncestryDNA Plus Traits
- 23andMe Ancestry – Autosomal DNA only, no Health
- 23andMe Ancestry Plus Health
Genealogy Products and Services
- MyHeritage Subscription with Free Trial
- Legacy Family Tree Webinars – Genealogy and DNA classes, subscription-based, some free
- Legacy Family Tree Software – Genealogy software for your computer
- OldNews – Old Newspapers with links to save to MyHeritage trees
- MyHeritage Omni comprehensive “everything included” subscription plan
- Newspapers.com – Search newspapers for your ancestors
- NewspaperArchive – Search different newspapers for your ancestors
My Books
- DNA for Native American Genealogy – by Roberta Estes, for those ordering the e-book from anyplace, or paperback within the United States
- DNA for Native American Genealogy – for those ordering the paperback outside the US
- The Complete Guide to FamilyTreeDNA – Y-DNA, Mitochondrial, Autosomal and X-DNA – for those ordering the e-book from anyplace, or paperback within the United States
- The Complete Guide to FamilyTreeDNA – Y-DNA, Mitochondrial, Autosomal and X-DNA for those ordering the paperback from outside the US
Genealogy Books
- Genealogical.com – Lots of wonderful genealogy research books
- American Ancestors – Wonderful selection of genealogy books
Genealogy Research
- Legacy Tree Genealogists – Professional genealogy research





























































































































































































